-
Notifications
You must be signed in to change notification settings - Fork 20
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
Comments
salasberryfin
moved this to CAPI Backlog
in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE)
Apr 10, 2024
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
changed the title
[ADR] v1.Cluster to v3.Cluster Migration
[ADR] Apr 10, 2024
v1.Cluster
to v3.Cluster
Migration
salasberryfin
moved this from CAPI Backlog
to In Progress (8 max)
in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE)
Apr 15, 2024
salasberryfin
moved this from In Progress (8 max)
to CAPI Backlog
in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE)
Apr 15, 2024
ADR in the May milestone |
salasberryfin
moved this from CAPI Backlog
to In Progress (8 max)
in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE)
Jun 10, 2024
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
moved this from PR to be reviewed
to Done
in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE)
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
Description
Until now, Turtles releases have used
provisioning.cattle.io
as resource for representing CAPI clusters in Rancher. This means that the controller createsclusters.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:
provisioning.cattle.io
tomanagement.cattle.io
.Terms
v1.Cluster
is equivalent toclusters.provisioning.cattle.io
, which is the actual resource that is used to represent clusters.v3.Cluster
is equivalent toclusters.management.cattle.io
, which is the actual resource that is used to represent clusters.The text was updated successfully, but these errors were encountered: