Document Breaking Changes through `kubernetes-sigs/karpenter` using SemVer for Packages

[jonathan-innis]

Description

What problem are you trying to solve?

Historically, AWS moved the kubernetes-sigs/karpenter repository from its organization over into the kubernetes-sigs organization back in November of 2023. As part of this move we continued to couple the upstream package version to the downstream provider version that actually releases the application with the helm chart. These changes were coupled because it was assumed that we would decide to decouple them at v1, where it would be natural to do so.

Given that we are starting to adopt more and more CloudProviders using Karpenter (currently have Azure, AWS, and Kwok), soon to have CAPI, I'd like to see a proposal for decoupling versions and v1 and to start using SemVer more consistently in the upstream repository to signal breaking changes and updates to downstream providers.

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[liangyuanpeng]

/remove-lifecycle stale