kubernetes-sigs/cluster-api

How to surfacing runtime hook blocking cluster deletion in condition

Ouverte

#6 807 ouverte le 2 juil. 2022

 (10 commentaires) (0 réaction) (0 personne assignée)Go (1 532 forks)auto 404
area/runtime-sdkhelp wantedkind/cleanuppriority/important-longtermtriage/accepted

Métriques du dépôt

Stars
 (4 267 étoiles)
Métriques de merge PR
 (Métriques PR en attente)

Description

Details:

This issue is to discuss how to surface that a cluster deletion is blocked when the BeforeClusterDelete hook blocks the deletion of a process with a blocking response.

We have 2 options:

  1. Use TopologyReconciled condition - Since only managed clusters are affected by BeforeClusterDelete hook we can use the TopologyReconciled condition to surface if a cluster deletion is blocked. Reason will be LifecycleHookBlocking. This will be consistent with how the other lifecycle hook blocking cases are surfaced.

  2. Use a separate condition - Since TopologyReconciled condition reflects if the underlying objects reflect the topology spec of the cluster using it for delete might be deviating from it purpose.

Some additional concerns:

  • How should the condition be updated after deletion is unblocked and the cluster is in the process of deleting the objects?
  • Which controller owns this condition?

/area runtime-sdk

Guide contributeur