✨ Upgrade cluster-api to v1.11.0 #880

PavanNeerudu · 2025-08-26T12:40:43Z

✨ Upgrade cluster-api to v1.11.0

What this PR does / why we need it:

This PR upgrades the cluster-api dependencies from v1.10.4 to v1.11.0, which includes several breaking changes that required significant code updates:

Dependency Updates: Upgraded sigs.k8s.io/cluster-api to v1.11.0 and related dependencies
API Version Updates: Updated import paths from v1beta1 to v1beta2 where applicable
Validation Fixes: Fixed condition reason validation by ensuring all condition reasons follow Kubernetes naming conventions (no spaces, alphanumeric with underscores)
Test Updates: Updated all test files to use the new condition helper patterns and fixed compatibility issues
CRD Updates: Regenerated CRDs to match the new cluster-api v1.11.0 specifications

This upgrade ensures compatibility with the latest cluster-api release and maintains all existing functionality while adopting the standardized Kubernetes condition handling patterns.

Testing:

All unit tests pass with the new cluster-api version
Condition validation errors have been resolved
Contract version compatibility verified

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):

Fixes: #854

netlify · 2025-08-26T12:40:49Z

✅ Deploy Preview for kubernetes-sigs-cluster-api-operator ready!

Name	Link
🔨 Latest commit	`880b9c1`
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-cluster-api-operator/deploys/68d2a460f21a7900081a0e89
😎 Deploy Preview	https://deploy-preview-880--kubernetes-sigs-cluster-api-operator.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

k8s-ci-robot · 2025-08-26T12:40:53Z

Hi @PavanNeerudu. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

furkatgofurov7 · 2025-08-26T12:42:53Z

/ok-to-test

PavanNeerudu · 2025-08-27T09:47:39Z

/retest pull-cluster-api-operator-e2e-main

k8s-ci-robot · 2025-08-27T09:47:55Z

@PavanNeerudu: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

/test pull-cluster-api-operator-build-main

/test pull-cluster-api-operator-e2e-main

/test pull-cluster-api-operator-make-main

/test pull-cluster-api-operator-test-main

/test pull-cluster-api-operator-verify-main

The following commands are available to trigger optional jobs:

/test pull-cluster-api-operator-apidiff-main

Use /test all to run all jobs.

In response to this:

/retest pull-cluster-api-operator-e2e-main

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

PavanNeerudu · 2025-08-27T09:48:14Z

/test pull-cluster-api-operator-e2e-main

PavanNeerudu · 2025-08-27T14:21:37Z

Hi @furkatgofurov7 , could you review the PR. I was able to resolve the failures in the last iterations. There is however a pipeline failure(pull-cluster-api-operator-apidiff-main) which is expected because this PR brings in changes from cluster-api conditions to the kubernetes conditions. Since the project is on alpha, do you think we can bypass this failure or suggest what we can do here? Thanks!

PavanNeerudu · 2025-08-29T12:09:29Z

Hey @furkatgofurov7 , checking in for reviews on the PR.

furkatgofurov7 · 2025-08-29T17:51:57Z

@PavanNeerudu thanks for the PR, I'll take a closer look soon, but meanwhile can you please take care of adding kind: Metadata to all metadata manifests? That seems to be a new requirement from CAPI v1.11.0 which providers need to update, xref: kubernetes-sigs/cluster-api#12242.

furkatgofurov7 · 2025-08-29T17:53:44Z

Hi @furkatgofurov7 , could you review the PR. I was able to resolve the failures in the last iterations. There is however a pipeline failure(pull-cluster-api-operator-apidiff-main) which is expected because this PR brings in changes from cluster-api conditions to the kubernetes conditions. Since the project is on alpha, do you think we can bypass this failure or suggest what we can do here? Thanks!

Yes, api-diff failure is quite normal to ignore, hence it is not a required job if you have noticed.

cmd/plugin/cmd/init.go

internal/controller/configmap_changes_test.go

internal/controller/coreprovider_to_providers_test.go

internal/controller/genericprovider_controller.go

PavanNeerudu · 2025-09-01T15:15:44Z

@PavanNeerudu thanks for the PR, I'll take a closer look soon, but meanwhile can you please take care of adding kind: Metadata to all metadata manifests? That seems to be a new requirement from CAPI v1.11.0 which providers need to update, xref: kubernetes-sigs/cluster-api#12242.

Done. Updated in the latest commits.

internal/controller/phases.go

kodal · 2025-09-12T14:31:10Z

@PavanNeerudu Any news? It's blocking update to clusterctl 1.11

internal/controller/genericprovider_controller_test.go

furkatgofurov7 · 2025-09-17T11:18:21Z

@PavanNeerudu hey, can you please address the outstanding minor comments and squash the commits? I'll defer the labelling until then, thank you!

alexander-demicev · 2025-09-17T13:30:07Z

/approve

k8s-ci-robot · 2025-09-17T13:30:16Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alexander-demicev

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:

~~OWNERS~~ [alexander-demicev]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

PavanNeerudu · 2025-09-23T09:03:19Z

@PavanNeerudu hey, can you please address the outstanding minor comments and squash the commits? I'll defer the labelling until then, thank you!

I have addressed the comments. Could you please take another pass?

furkatgofurov7

small nit:

internal/controller/phases_test.go

furkatgofurov7 · 2025-09-23T09:18:37Z

Please squash commits once you resolve the last comments, otherwise LGTM, thank you.

PavanNeerudu · 2025-09-23T09:26:43Z

Please squash commits once you resolve the last comments, otherwise LGTM, thank you.

Sure, done.

PavanNeerudu · 2025-09-23T10:51:42Z

@furkatgofurov7 can you approve and merge the PR? Thanks!

furkatgofurov7 · 2025-09-23T11:55:57Z

@PavanNeerudu golangci-lint is failing

This commit upgrades the cluster-api-operator to use cluster-api v1.11.0 with the following major changes: - Updated all cluster-api dependencies from v1.10.4 to v1.11.0 - Migrated from cluster-api conditions helpers to k8s.io/apimachinery/pkg/api/meta - Updated condition handling to use conditions.Set instead of meta.SetStatusCondition - Fixed condition status comparisons for v1beta2 compatibility - Updated contract version to v1beta2 with major: 1, minor: 11 across all configurations - Fixed healthcheck controller to properly map deployment status to provider Ready condition - Added DeploymentAvailable reason constant for condition validation - Updated test infrastructure to handle CoreProvider naming constraints - Fixed CRD cleanup in E2E tests to preserve operator CRDs - Updated all test resources and configurations for v1.11.0 compatibility - Resolved linting issues and compilation errors - All unit tests and E2E tests now pass with v1.11.0 Breaking changes: - Requires cluster-api v1.11.0 or later - Uses v1beta2 API contract - Condition Reason field validation is stricter (must be non-empty and match regex pattern) Fixes #[issue-number] if applicable

furkatgofurov7 · 2025-09-23T14:06:01Z

Thank you!

/lgtm

k8s-ci-robot · 2025-09-23T14:06:09Z

LGTM label has been added.

Git tree hash: 13554306f69bfe002522cd10fc25f196561c56bd

k8s-ci-robot · 2025-09-23T14:08:27Z

@PavanNeerudu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cluster-api-operator-apidiff-main	`880b9c1`	link	false	`/test pull-cluster-api-operator-apidiff-main`

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Aug 26, 2025

k8s-ci-robot requested review from Fedosin and furkatgofurov7 August 26, 2025 12:40

k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Aug 26, 2025

k8s-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Aug 26, 2025

k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Aug 26, 2025

LingyanCao reviewed Sep 1, 2025

View reviewed changes

cmd/plugin/cmd/init.go Show resolved Hide resolved

LingyanCao reviewed Sep 1, 2025

View reviewed changes

internal/controller/configmap_changes_test.go Outdated Show resolved Hide resolved

LingyanCao reviewed Sep 1, 2025

View reviewed changes

internal/controller/coreprovider_to_providers_test.go Outdated Show resolved Hide resolved

LingyanCao reviewed Sep 1, 2025

View reviewed changes

internal/controller/genericprovider_controller.go Outdated Show resolved Hide resolved

LingyanCao reviewed Sep 2, 2025

View reviewed changes

internal/controller/phases.go Outdated Show resolved Hide resolved

furkatgofurov7 reviewed Sep 17, 2025

View reviewed changes

internal/controller/genericprovider_controller_test.go Show resolved Hide resolved

furkatgofurov7 mentioned this pull request Sep 17, 2025

CAPI v1.11.0-beta.0 has been released and is ready for testing #854

Closed

furkatgofurov7 requested review from alexander-demicev and LingyanCao September 17, 2025 11:18

furkatgofurov7 mentioned this pull request Sep 17, 2025

🌱 Bump the kubernetes group in /test with 3 updates #890

Closed

furkatgofurov7 reviewed Sep 23, 2025

View reviewed changes

internal/controller/phases_test.go Outdated Show resolved Hide resolved

internal/controller/phases_test.go Outdated Show resolved Hide resolved

PavanNeerudu force-pushed the cluster-api-v1.11.0-upgrade branch from 4ba2a94 to 17125f6 Compare September 23, 2025 09:25

zerospiel mentioned this pull request Sep 23, 2025

feat: upgrade [email protected] k0rdent/kcm#2032

Draft

PavanNeerudu force-pushed the cluster-api-v1.11.0-upgrade branch from 17125f6 to 60acb91 Compare September 23, 2025 10:26

furkatgofurov7 mentioned this pull request Sep 23, 2025

🌱 support Git release URLs as source for plugin ConfigMap #894

Merged

PavanNeerudu force-pushed the cluster-api-v1.11.0-upgrade branch from 60acb91 to 880b9c1 Compare September 23, 2025 13:45

k8s-ci-robot assigned furkatgofurov7 Sep 23, 2025

k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 23, 2025

k8s-ci-robot merged commit 63ce757 into kubernetes-sigs:main Sep 23, 2025
13 of 14 checks passed

✨ Upgrade cluster-api to v1.11.0 #880

✨ Upgrade cluster-api to v1.11.0 #880

Uh oh!

Conversation

PavanNeerudu commented Aug 26, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!