-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document Breaking Changes through kubernetes-sigs/karpenter
using SemVer for Packages
#1181
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
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: