Helm --atomic --timeout cancellation and rollback boundaries
A deployment policy is needed for Helm upgrades that combines --timeout with --atomic to provide a bounded wait for readiness and an automatic rollback on failure. The documented behavior indicates --timeout limits client wait time and --atomic triggers a rollback on timeout or failure, while a SIGINT stops the client immediately. It is unclear how these mec
helm
kubernetes