Update dependencies to Kubernetes 1.30 and adapt to breaking changes #763
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
leaderelection.SwitchMetric
was renamed toleaderelection.LeaderMetric
and this breaks controller-runtime. So we have to pin controller-runtime to an unreleased version that contains kubernetes-sigs/controller-runtime#2693 here and in every Flux controller.PS. The breaking change was addressed in https://github.com/kubernetes-sigs/controller-runtime/releases/tag/v0.18.0
We can't release Flux v2.3 without bumping Kubernetes to 1.30 and be stuck on 1.29 till end of Q3. I think we should go forward with this, when controller-runtime has a stable release that includes client-go 1.30, we'll do a patch release for Flux v2.3.
PS. Using
major.minor
for the Go version in go.mod is no longer possible because Kubernetes switched to full semver.