-
Notifications
You must be signed in to change notification settings - Fork 239
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 to v3.28.0 #3216
update canal to v3.28.0 #3216
Conversation
Hi @samuelfischer. Thanks for your PR. I'm waiting for a kubermatic member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
@samuelfischer hey and thanks for the PR.
What CVE are you referring to? |
Ah sorry, I missed adding the CVEs on Friday - added them to the Description now. Re-checking the image again today I also saw two golang stdlib CVEs in the go version of flanneld - both will also be fixed by the update (CVE-2023-24538, CVE-2023-24540). |
Signed-off-by: Samuel Fischer <samuel.fischer@scandio.de>
5dba97c
to
f7275e5
Compare
rebased to fix conflicts after Merge of #3214 |
/test all |
/approve |
LGTM label has been added. Git tree hash: 1df257d94d80021a99c95064c8ab39d16ac33504
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kron4eg 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 |
What this PR does / why we need it:
Continues #3214 to update canal-cni.
Additionally fixes Critical CVEs in the older flannel image ( CVE-2023-38545, CVE-2023-26463, CVE-2023-41913 ).
Which issue(s) this PR fixes:
Fixes #3206 (the first Task, the others should be fixed by the preceding PR)
What type of PR is this?
/kind feature
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation:
Do we need a hint to https://docs.tigera.io/calico/latest/release-notes/#important-upgrade-notes and that restarts of calico controllers might be necessary after the update?
Not sure how to handle that.