-
Notifications
You must be signed in to change notification settings - Fork 812
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 CI to use 1.32 eks and kops clusters #2323
Conversation
Code Coverage DiffThis PR does not change the code coverage |
When running locally run in to |
dc26cee
to
4a9c0f1
Compare
FYI eksctl release v0.201.0 made This means that eks tests are likely failing due to a conflict between our CI scripts attempting to install metrics-server, and eksctl already doing it. We'll either have to edit run.sh to not install metrics-server for eksctl clusters (or, less ideal, override eksctl to not install metrics-server) |
4a9c0f1
to
0a3ca65
Compare
0a3ca65
to
aa4e383
Compare
/retest looks like |
Tested locally and am able to successfully make a 1.32 cluster with make/cluster
Additionally CI is now passing unholding CR |
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.
/lgtm
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.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: torredil 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 type of PR is this?
/kind cleanup
What is this PR about? / Why do we need it?
This PR updates our CI to use k8s 1.32 when creating clusters using kops and eksctl
How was this change tested?
CI and running make cluster/create with change to verify 1.32 cluster is created
Does this PR introduce a user-facing change?
/hold
holding until local testing is done