-
Notifications
You must be signed in to change notification settings - Fork 552
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
Migrate away from using sigs.k8s.io in AWS tags #1166
Comments
Next version or current v0.4.x? |
Not 0.4 |
I'd suggest that we maintain the backwards compat logic for the duration of the 0.5.x (or whatever the next version is) release, and then drop at v0.6.x (or vNext +1) |
Wouldn’t an upgrade tool or document handle covering the breaking change? I wonder if it’s worth maintaining backward logic while we are in alpha phase |
We need to start to make a clear distinction between the alpha version of the types and the support that we provide for the greater project, which IMO is beyond alpha at this point. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/lifecycle frozen |
/remove-lifecycle frozen |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
Looks like a breaking change. |
@Ankitasw - yes good idea 👍 |
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 |
The Kubernetes project currently lacks enough active 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 rotten |
/remove-lifecycle stale |
/kind feature
Describe the solution you'd like
We should migrate away from using sigs.k8s.io in AWS tag names and instead use x-k8s.io. This applies to all tags prefixed with
sigs.k8s.io/cluster-api-provider-aws/
.We must provide a migration path that automatically copies an old tag name to a new one, and we need to define the period of time during which we need to support both naming conventions.
Anything else you would like to add:
The prefix is defined here:
cluster-api-provider-aws/api/v1alpha2/tags.go
Line 96 in c6b8c30
Environment:
/priority important-longterm
The text was updated successfully, but these errors were encountered: