Document Breaking Changes through kubernetes-sigs/karpenter
using SemVer for Packages
#1181
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
kubernetes-sigs/karpenter
using SemVer for Packages
#1181
Description
What problem are you trying to solve?
Historically, AWS moved the
kubernetes-sigs/karpenter
repository from its organization over into thekubernetes-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.
The text was updated successfully, but these errors were encountered: