-
Notifications
You must be signed in to change notification settings - Fork 443
Update Calico to 3.29 #5499
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 Calico to 3.29 #5499
Conversation
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5499 +/- ##
=======================================
Coverage 52.57% 52.57%
=======================================
Files 272 272
Lines 29470 29470
=======================================
Hits 15495 15495
Misses 13167 13167
Partials 808 808 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
/test pull-cluster-api-provider-azure-conformance-dual-stack-with-ci-artifacts |
took a look at the windows nodes and they are not getting correct calico version. Will need to look closer at how that version is specified |
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
f5e2cca
to
8a16726
Compare
/test pull-cluster-api-provider-azure-ci-entrypoint |
1 similar comment
/test pull-cluster-api-provider-azure-ci-entrypoint |
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
be6c284
to
d23c63c
Compare
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
@jsturtevant: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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-sigs/prow repository. I understand the commands that are listed here. |
Getting closer, the pods are deploying. Now I believe we are running into kubernetes-sigs/sig-windows-tools#347 |
/close |
@jsturtevant: Closed this PR. 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-sigs/prow repository. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
fixes #5498
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
TODOs:
Release note: