Support suspension and unsuspension, appropriately removing or creating Runtime CR.
For plans where provider is still driving the process (but we manage Runtime CRs) fail operation in case either KIM related changes fail or provisioner operation fails.
We have settings telling that given plan is managed by KIM only or is driven by provisioner (but Runtime CR is to be updated as well).
Consider cases for both settings and different states of already provisioned clusters (i.e. KIM only driven plan, but cluster provisioned by provisioner, no Runtime CR present - migration not done yet).
Support suspension and unsuspension, appropriately removing or creating Runtime CR.
For plans where provider is still driving the process (but we manage Runtime CRs) fail operation in case either KIM related changes fail or provisioner operation fails.
We have settings telling that given plan is managed by KIM only or is driven by provisioner (but Runtime CR is to be updated as well). Consider cases for both settings and different states of already provisioned clusters (i.e. KIM only driven plan, but cluster provisioned by provisioner, no Runtime CR present - migration not done yet).