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 from Provisioner to KIM on DEV #207

Open
1 of 8 tasks
Tracked by #112
Disper opened this issue May 10, 2024 · 0 comments
Open
1 of 8 tasks
Tracked by #112

Migrate from Provisioner to KIM on DEV #207

Disper opened this issue May 10, 2024 · 0 comments

Comments

@Disper
Copy link
Member

Disper commented May 10, 2024

Acceptance Criteria

  • Old clusters are now also managed by KIM (we have ran the migration script)
  • Migration should be resilient to possible simultaneous upgrades done by the user (e.g. if user changes machine type).
  • At any given time, it's possible to create new shoots
  • At any given time, it's possible to upgrade new shoots
  • when CR is created for a cluster created by the old Provisioner, KIM should not attempt to create a cluster
    Possibly could be achieved by having additional CR's annotation such as (operator.kyma-project.io/do-not-provision that would need to be respected by KIM
  • Remove https://github.com/kyma-project/control-plane/tree/main/components/schema-migrator
  • Assure that the scenario for a cluster created via provisioner and migrated to KIM works (also from KEB perspective)
  • Provisioner is disabled on DEV
@Disper Disper changed the title Migrate DEV Migrate from Provisioner to KIM on DEV May 10, 2024
@Disper Disper added this to the Provisioning MVP milestone May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant