-
Notifications
You must be signed in to change notification settings - Fork 10
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
Set force-deletion flag when creating shoot-cluster [KIM/feature] #103
Comments
Pre-requisite for kyma-project/kyma#18198 |
@tobiscr should that annotation be set for only new clusters or should also existing clusters be migrated at some point? |
Confirmed that we want to set it only for new clusters. |
According to what I've tried - it's not possible to just create a cluster with that annotation set.
For more details, please refer to the relevant Gardener docu. It could be possible to do it differently and when we fail to delete a cluster with one of those listed error messages to apply the annotation then. |
JFYI - @pbochynski : After deeper investigation, we realised that this features collides with #126 :
|
Yes - we can postpone this one. We should also check how Gardener handles the deletion of hibernated clusters. Maybe the force-deletion annotation will help to reduce the time. |
We will for now not work on it, until we discovered how hibernation works. Possible that we can reuse this flag for deleting hibernated clusters faster. |
Description
Gardner supports now the option to force the deletion of a cluster (which avoids longer waiting-periods during the de-provisioning e.g. the K8s cluster couldn't be gracefully stopped caused by hanging finalizers).
We agreed to use this feature flag and the infrastructure manager / provisioner should set this flag properly.
AC:
confirmation.gardener.cloud/force-deletion
is set in the shoot-specs of Gardener clusters.Reasons
Enable/accept non-graceful shutdowns of Gardener clusters to avoid longer waiting periods during the de-provisioning.
Attachments
[Moved from Provisioner to KIM]
The text was updated successfully, but these errors were encountered: