-
Notifications
You must be signed in to change notification settings - Fork 240
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.
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
Update Canal/Calico to v3.23.5 #2538
Conversation
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
/cherrypick release/v1.5 |
@xmudrii: once the present PR merges, I will cherry-pick it on top of release/v1.5 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahmedwaleedmalik 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 |
LGTM label has been added. Git tree hash: 291900f6b41e48a17f8aeb374bdbeeec530f61a5
|
@xmudrii: #2538 failed to apply on top of branch "release/v1.5":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What this PR does / why we need it:
This PR updates Calico as part of the
cni-canal
addon to v3.23.5. This Calico release is supposed to fix an issue where Calico pods are crashing after upgrading from an older Calico version to a newer one (projectcalico/calico#6442).What type of PR is this?
/kind feature
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: