The staged-update docs never mention the deletion stage in prose — it appears only inside pasted status YAML (deletionStageStatus). Nothing states that it exists, that it removes resources from clusters, or that it runs without approval gates (unlike user-defined stages, which support beforeStageTasks/afterStageTasks). Users following the approval docs reasonably conclude every cluster-affecting step is gated; the final, irreversible one isn't. Related: kubefleet-dev/kubefleet#746.
The staged-update docs never mention the deletion stage in prose — it appears only inside pasted status YAML (
deletionStageStatus). Nothing states that it exists, that it removes resources from clusters, or that it runs without approval gates (unlike user-defined stages, which supportbeforeStageTasks/afterStageTasks). Users following the approval docs reasonably conclude every cluster-affecting step is gated; the final, irreversible one isn't. Related: kubefleet-dev/kubefleet#746.