Fix breaking changes from k8s 0.34 and controller runtime 0.22 #7692
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.
What this PR does / why we need it:
After updating the KKP dependencies in kubermatic/kubermatic#15087, there have been some breaking changes introduced in dashboard. This PR updates the dashboard API dependencies to align with KKP and it also adds 0.34 client libraries and controller runtime 0.22.0.
It also looks like dashboard 2.29 release contains a KKP RC dependency.
The dependency updates in this PR:
k8c.io/kubermatic/v2updated to latest (so this covers also the stable 2.29)k8c.io/kubermatic/sdk/v2updated to latestk8s.io/apiandk8s.io/apimachineryupdated to v0.34.0sigs.k8s.io/controller-runtimeupdated to v0.22.0k8c.io/machine-controller/sdkupdated to v0.64.0Manual updates:
k8s.io/client-gohas been updated to v0.34.0k8s.io/kube-openapihas also been updatedBreaking changes introduced:
preferencesfield also has theomitzerotag)isUnstructured boolparameter toapiutil.RESTClientForGVK, this was causing issues for our testse. It seems to have been added with this pr: ⚠️ Add native SSA support kubernetes-sigs/controller-runtime#3253What type of PR is this?
/kind cleanup
/kind chore
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: