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
Now if we delete a tenant all tenant namespaces are deleted automatically by kubernetes garbage collector. To protect critical tenants from accidental deletion (e.g. wrong commit to ci\cd system) it would be good to have some annotation, like capsule.clastix.io/protected, which will make capsule-controller to ignore tenant deletion and instead add event and message to a log.
@bsctl the tenant won't be deleted. But resources from tenant namespace will be deleted and namespaces would be stuck in Terminating state (I've just verified this in our staging environment by making accidental commit which removed system tenant, where we install all our additional cluster components :) )
Now if we delete a tenant all tenant namespaces are deleted automatically by kubernetes garbage collector. To protect critical tenants from accidental deletion (e.g. wrong commit to ci\cd system) it would be good to have some annotation, like
capsule.clastix.io/protected
, which will makecapsule-controller
to ignore tenant deletion and instead add event and message to a log.@prometherion WDYT?
The text was updated successfully, but these errors were encountered: