You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Evans Mungai 5895a7e8f9 fix: default to foreground cascade when --wait is used in uninstall ... When `helm uninstall --wait` is called, the default deletion propagation is now "foreground" instead of "background". This ensures dependent resources (like Pods, ReplicaSets created by controllers) are fully cleaned up before the command returns. Previously, with background deletion, parent resources were deleted immediately while garbage collection handled dependents asynchronously. This caused subsequent namespace deletions to hang for 2+ minutes waiting for those dependent resources to be cleaned up. With foreground deletion, Kubernetes waits for all dependents to be deleted before removing the parent resource, ensuring `--wait` truly waits for all cleanup to complete. Cascade behavior by command: | Command | Cascade | |----------------------------------------------|------------| | `helm uninstall release` | background | | `helm uninstall release --wait` | foreground | | `helm uninstall release --wait=hookOnly` | background | | `helm uninstall release --wait --cascade=background` | background | Users can still explicitly set `--cascade=background` to restore the previous behavior if needed. Fixes #31651 Signed-off-by: Evans Mungai <mbuevans@gmail.com>		8 months ago
..
capturing_kube_client.go	fix: default to foreground cascade when --wait is used in uninstall	8 months ago
failing_kube_client.go	chore: Cleanup additional/redundant kube client Interfaces	11 months ago
printer.go	chore: Cleanup additional/redundant kube client Interfaces	11 months ago