Skip to content
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

Open
Tracked by #3853
ncdc opened this issue Oct 3, 2019 · 15 comments
Open
Tracked by #3853

Migrate away from using sigs.k8s.io in AWS tags #1166

ncdc opened this issue Oct 3, 2019 · 15 comments
Labels
kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone

Comments

@ncdc
Copy link
Contributor

ncdc commented Oct 3, 2019

/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:

NameAWSProviderPrefix = "sigs.k8s.io/cluster-api-provider-aws/"
.

Environment:

  • Cluster-api-provider-aws version: v0.4.1

/priority important-longterm

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Oct 3, 2019
@vincepri
Copy link
Member

vincepri commented Oct 3, 2019

Next version or current v0.4.x?

@ncdc
Copy link
Contributor Author

ncdc commented Oct 3, 2019

Not 0.4

@vincepri vincepri added this to the Next milestone Oct 3, 2019
@detiber
Copy link
Member

detiber commented Oct 3, 2019

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)

@vincepri
Copy link
Member

vincepri commented Oct 3, 2019

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

@detiber
Copy link
Member

detiber commented Oct 4, 2019

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.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 2, 2020
@detiber
Copy link
Member

detiber commented Jan 2, 2020

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 2, 2020
@randomvariable randomvariable modified the milestones: Next, v0.7.0 Mar 11, 2021
@randomvariable randomvariable modified the milestones: v0.7.0, v0.7.x Jun 28, 2021
@randomvariable randomvariable added the kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API label Nov 8, 2021
@randomvariable randomvariable modified the milestones: v0.7.x, v1.x Nov 8, 2021
@sedefsavas sedefsavas modified the milestones: v1.x, v2.x Dec 6, 2021
@richardcase
Copy link
Member

/remove-lifecycle frozen

@k8s-ci-robot k8s-ci-robot removed the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jul 8, 2022
@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 6, 2022
@richardcase
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 10, 2022
@Ankitasw
Copy link
Member

Ankitasw commented Dec 2, 2022

Looks like a breaking change.
@richardcase shall we add this item to v1beta3 APIs issue?

@richardcase
Copy link
Member

@Ankitasw - yes good idea 👍

@Ankitasw Ankitasw mentioned this issue Dec 5, 2022
2 tasks
@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 2, 2023
@k8s-triage-robot
Copy link

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:

  • 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 rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 1, 2023
@Ankitasw
Copy link
Member

Ankitasw commented Apr 4, 2023

/remove-lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
Development

No branches or pull requests

10 participants