mirror of https://github.com/helm/helm
During `helm uninstall --wait --cascade foreground`, the kstatus watcher can intermittently miss deletion events for resources, leaving them stuck in Terminating status until the timeout expires. This is a race between the Kubernetes garbage collector removing the foregroundDeletion finalizer and the informer delivering the corresponding watch event. Add a fallback verification step in waitForDelete: after the watcher times out, before reporting a resource as still existing, issue a live GET to the API server. If the resource returns 404 (NotFound), treat it as successfully deleted. The fallback GET uses a bounded 10-second timeout to avoid blocking on unresponsive API servers. This only affects the error path; the happy path (watcher observes deletions normally) is unchanged. Signed-off-by: Jathavedhan M <jathavedhan.m@ibm.com>pull/32222/head
parent
f8b5203160
commit
33076b3bd5
Loading…
Reference in new issue