Unlocking independent API version updates

[sedefsavas]

Up until now, CAPA was using the same API version with core Cluster API.
I want to open up the discussion to change that and update CAPA API versions as needed.

Some of the providers are already using their own versioning like Openstack and MicroVM and not matching with CAPI versioning. There is no blocker in the core cluster API to block this change. Plus, this makes our innovation/breaking change pace independent of another repo.

The main reason why we need this now is ClusterClass support for CAPA-managed clusters, which requires a breaking change.

Another reason why we need a new API version is ClusterClass support for EKS-managed clusters.
Following the managed Kubernetes proposal kubernetes-sigs/cluster-api#6988, we will need to make some CRD changes, possibly breaking.

Please comment if there are any concerns regarding this. I will also bring this up during Aug 8th community meeting.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[Ankitasw]

We have changed the API version to beta2, is this issue still needed?
cc @richardcase @Skarlso

[Skarlso]

Good point. I think this is "done" now.

[richardcase]

I agree @Ankitasw & @Skarlso, this is done:

/close

[k8s-ci-robot]

@richardcase: Closing this issue.

In response to this:

I agree @Ankitasw & @Skarlso, this is done:

/close

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/test-infra repository.