You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Acceptance Criteria
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
The text was updated successfully, but these errors were encountered: