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

[ADR] v1.Cluster to v3.Cluster Migration #475

Closed
Tracked by #473
kkaempf opened this issue Apr 9, 2024 · 2 comments
Closed
Tracked by #473

[ADR] v1.Cluster to v3.Cluster Migration #475

kkaempf opened this issue Apr 9, 2024 · 2 comments
Assignees
Labels
kind/proposal Issues or PRs related to proposals
Milestone

Comments

@kkaempf
Copy link

kkaempf commented Apr 9, 2024

Description

Until now, Turtles releases have used provisioning.cattle.io as resource for representing CAPI clusters in Rancher. This means that the controller creates clusters.provisioning.cattle.io resource when a CAPI cluster (or the namespace where it exists) is configured to be imported into Rancher.

Users that are already using Turtles will have clusters backed by this import mechanism and, when migrating to the new clusters.management.cattle.io resource, we need to make sure that clusters are properly upgraded.

The ADR will need to cover:

  • How to migrate clusters: from provisioning.cattle.io to management.cattle.io.
  • User actions: do users need to perform specific actions to migrate?
  • Migration tools: do we provide script/tooling to simplify migration?
  • Deprecation of current controller: how do we deprecate the existing controller after migration?

Terms

v1.Cluster is equivalent to clusters.provisioning.cattle.io, which is the actual resource that is used to represent clusters.
v3.Cluster is equivalent to clusters.management.cattle.io, which is the actual resource that is used to represent clusters.

@kkaempf kkaempf converted this from a draft issue Apr 9, 2024
@salasberryfin salasberryfin mentioned this issue Apr 10, 2024
4 tasks
@salasberryfin salasberryfin added the kind/proposal Issues or PRs related to proposals label Apr 10, 2024
@salasberryfin salasberryfin added this to the April release milestone Apr 10, 2024
@salasberryfin salasberryfin changed the title [PROPOSAL] v1.Cluster to v3.Cluster Migration [ADR] v1.Cluster to v3.Cluster Migration Apr 10, 2024
This was referenced Apr 10, 2024
@salasberryfin salasberryfin changed the title [ADR] v1.Cluster to v3.Cluster Migration [ADR] v1.Cluster to v3.Cluster Migration Apr 10, 2024
@salasberryfin salasberryfin self-assigned this Apr 15, 2024
@salasberryfin salasberryfin moved this from CAPI Backlog to In Progress (8 max) in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE) Apr 15, 2024
@salasberryfin salasberryfin moved this from In Progress (8 max) to CAPI Backlog in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE) Apr 15, 2024
@salasberryfin salasberryfin removed their assignment Apr 15, 2024
@mbologna
Copy link
Member

ADR in the May milestone

@mbologna mbologna removed this from the May release milestone May 15, 2024
@alexander-demicev alexander-demicev added this to the July release milestone Jun 3, 2024
@kkaempf kkaempf modified the milestones: July release, June release Jun 4, 2024
@salasberryfin salasberryfin moved this from CAPI Backlog to In Progress (8 max) in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE) Jun 10, 2024
@salasberryfin salasberryfin moved this from In Progress (8 max) to PR to be reviewed in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE) Jun 18, 2024
@salasberryfin salasberryfin moved this from PR to be reviewed to Done in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE) Jun 19, 2024
@salasberryfin
Copy link
Contributor

salasberryfin commented Jun 19, 2024

ADR is ready and implementation has started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/proposal Issues or PRs related to proposals
Development

No branches or pull requests

4 participants