-
Notifications
You must be signed in to change notification settings - Fork 21
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 to Cluster api 1.7 #117
Conversation
this change brings the provider into line with the cluster-api 1.7 release, and also with kubernetes 1.29
it appears that a change in the cluster-api kubeadm bootstrap provider is causing secrets with the same name as a machine to be created in the namespace with the machine object. this is causing the kubeconfig secret created by the capk controller to be overwritten, which cascades into kubemark not being able to start. the fix is to add "kubemark-config" as a suffix to secret.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: elmiko 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 |
/assign |
@@ -5,7 +5,7 @@ jobs: | |||
if: (github.repository == 'kubernetes-sigs/cluster-api-provider-kubemark') | |||
strategy: | |||
matrix: | |||
go-version: [1.22.x] | |||
go-version: [1.21.x] |
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.
Why take the go version backwards?
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 was mostly trying to sync all the versions so that everything was the same, my plan is to update to 1.22 with the cluster-api 1.8 update. so, mostly just trying to get a clean base to build on top of.
/lgtm |
What this PR does / why we need it:
updates the provider to use 1.7 capi and 1.29 k8s.
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged):fixes #106
Special notes for your reviewer:
use
make test-e2e
to replicatei tested this locally on an ubuntu 22.04 server and got the following output:
Release notes: