-
Notifications
You must be signed in to change notification settings - Fork 443
Upgrade to calico 3.29 and use windows support #5523
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
base: main
Are you sure you want to change the base?
Upgrade to calico 3.29 and use windows support #5523
Conversation
[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 #5523 +/- ##
==========================================
- Coverage 53.26% 53.26% -0.01%
==========================================
Files 272 272
Lines 29529 29529
==========================================
- Hits 15730 15728 -2
- Misses 12984 12986 +2
Partials 815 815 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
leaving my self some notes after investigating the failures:
|
not sure what to do about this one as the chart doesn't let me override dnsConfig settings |
5fbed9d
to
78297a9
Compare
with the latest changes the cluster is coming online:
|
Opened projectcalico/calico#10117 |
The workload upgrade test is failing with cloud manager crashing:
Is this a known issue? I don't see anything that makes it look like this is related to changes here. |
This is now mostly passing, It requires:
|
Super strange that it is flaky with a panic.. |
All the major challenges have been addresses. Just waiting on a Calico release that contains the updated helm chart |
4285b61
to
1f6f8b4
Compare
We probably need a rebase here ? |
Still waiting on a helm chart release. I saw they released the next calico version but don't see the updates in the helm chart so I will ping them to find out if that will be released too |
It wasn't scheduled till Calico 3.31 but I requested some backports so should have it in the next patch release! projectcalico/calico#10117 (comment) |
1f6f8b4
to
06b1720
Compare
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
47b9852
to
87199fa
Compare
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.
Looks mostly ready to me! Just some minor comments and questions from my end
@@ -8,5 +8,5 @@ spec: | |||
spec: | |||
containers: | |||
# Change the value of image field below to your controller image URL | |||
- image: gcr.io/k8s-staging-cluster-api-azure/cluster-api-azure-controller:main | |||
- image: jjsacrpub.azurecr.io/cluster-api-azure/cluster-api-azure-controller-amd64:dev |
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.
Was this meant to be committed?
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.
no, I think is result of running tools locally. Not sure why its not a part of the .gitignore? will remove
@@ -8,4 +8,4 @@ spec: | |||
spec: | |||
containers: | |||
- name: manager | |||
imagePullPolicy: Always | |||
imagePullPolicy: IfNotPresent |
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.
Same as above. I think these get changed when you run make tilt-up
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.
yes, I think so... I'll remove it and squash commits too
@@ -1,5 +1,1088 @@ | |||
apiVersion: apiextensions.k8s.io/v1 | |||
kind: CustomResourceDefinition | |||
metadata: |
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.
Are these diffs just generated templates from the new Calico source? And same with all the deletions in the other folders of addons
?
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.
Yes, this is automated via the make file command where it grabs the latest release then extracts it.
plural: "" | ||
conditions: [] | ||
storedVersions: [] | ||
--- |
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.
nit: eof line
api server name properly\n# https://github.com/projectcalico/calico/issues/9536\ndnsConfig: | ||
\n nameservers:\n - 127.0.0.53\n options:\n - name: edns0\n - name: | ||
trust-ad\nkubernetesServiceEndpoint:\n host: \"{{ .Cluster.spec.controlPlaneEndpoint.host | ||
}}\"\n port: \"{{ .Cluster.spec.controlPlaneEndpoint.port }}\"" |
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.
Can this be formatted like the previous diff so it's a bit more readable rather than using newline characters?
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.
I can take a look, I think this is an automatically generated file?
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Upgrades Calico to 3.29 and updates windows to use the upstream Calico HPC support .
I tried to remove as much of the calico manifests but the Private Cluster test still uses those so they are still needed. We still need a bunch of the CSRs for windows since the calico still needs some additional support to fully remove it (tigera/operator#3113).
I did chat briefly with @Jont828 about expanding the helmProxy to take an additional field that would be Pre/Post yaml to deploy so we could potentially remove some of the extra yaml. But that is low priority and could be a follow up.
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 #5498
Special notes for your reviewer:
TODOs:
Release note: