Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[release/v1.5] Update Canal/Calico to v3.23.5 #2539

Merged
merged 1 commit into from
Dec 9, 2022
Merged

[release/v1.5] Update Canal/Calico to v3.23.5 #2539

merged 1 commit into from
Dec 9, 2022

Conversation

xmudrii
Copy link
Member

@xmudrii xmudrii commented Dec 9, 2022

What this PR does / why we need it:

This is a manual backport of #2538 to the release/v1.5 branch.

What type of PR is this?

/kind feature

Does this PR introduce a user-facing change? Then add your Release Note here:

Update Canal to v3.23.5. This Canal release is supposed to fix an issue where Calico pods are crashing after upgrading from an older Calico version to a newer one (see the [Known Issues](https://docs.kubermatic.com/kubeone/v1.5/known-issues/) document for more details)

Documentation:

https://github.com/kubermatic/docs/pull/1281

@xmudrii
Update Canal/Calico to v3.23.5
7bf6302 
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
@kubermatic-bot kubermatic-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/feature Categorizes issue or PR as related to a new feature. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Dec 9, 2022
moadqassem
moadqassem reviewed Dec 9, 2022
View reviewed changes
Copy link
Member

@moadqassem moadqassem left a comment •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Dec 9, 2022
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: d13509c2843d90388c50b904718fc3458a18287b

moadqassem
moadqassem approved these changes Dec 9, 2022
View reviewed changes
Copy link
Member

@moadqassem moadqassem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: moadqassem

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubermatic-bot kubermatic-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 9, 2022
@kubermatic-bot kubermatic-bot merged commit 8403987 into release/v1.5 Dec 9, 2022
@kubermatic-bot kubermatic-bot deleted the update-calico-1.5 branch December 9, 2022 16:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@moadqassem moadqassem moadqassem approved these changes

@ahmedwaleedmalik ahmedwaleedmalik Awaiting requested review from ahmedwaleedmalik

Assignees

@moadqassem moadqassem

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@xmudrii @kubermatic-bot @moadqassem