Skip to content

Conversation

@adoi
Copy link
Contributor

@adoi adoi commented Nov 7, 2025

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/v2 updated to latest (so this covers also the stable 2.29)
  • k8c.io/kubermatic/sdk/v2 updated to latest
  • k8s.io/api and k8s.io/apimachinery updated to v0.34.0
  • sigs.k8s.io/controller-runtime updated to v0.22.0
  • k8c.io/machine-controller/sdk updated to v0.64.0

Manual updates:

  • k8s.io/client-go has been updated to v0.34.0
  • k8s.io/kube-openapi has also been updated

Breaking changes introduced:

What 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:

Update to controller-runtime v0.22.0 and client libraries to v0.34.0

Documentation:

NONE

@kubermatic-bot kubermatic-bot added docs/none Denotes a PR that doesn't need documentation (changes). kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. kind/chore Updating grunt tasks etc; no production code changes. sig/api Denotes a PR or issue as being assigned to SIG API. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Nov 7, 2025
@adoi
Copy link
Contributor Author

adoi commented Nov 7, 2025

/assign

@KhizerRehan KhizerRehan changed the title fix breaking changes from k8s 0.34 and controller runtime 0.22 Fix breaking changes from k8s 0.34 and controller runtime 0.22 Nov 7, 2025
@KhizerRehan KhizerRehan requested a review from archups November 7, 2025 08:16
@KhizerRehan
Copy link
Contributor

/lgtm

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Nov 7, 2025
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: c6c717ff793f2202ee9188b0f737c42326e409af

@ahmadhamzh
Copy link
Contributor

/approve

@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahmadhamzh

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubermatic-bot kubermatic-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 10, 2025
@kubermatic-bot kubermatic-bot merged commit ea8bd89 into kubermatic:main Nov 10, 2025
9 checks passed
@kubermatic-bot kubermatic-bot added this to the KKP 2.29 milestone Nov 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. docs/none Denotes a PR that doesn't need documentation (changes). kind/chore Updating grunt tasks etc; no production code changes. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/api Denotes a PR or issue as being assigned to SIG API. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants