Helm v3 release history retention without configurable revision cap or pruning permissions
Helm v3 persists each release revision as a separate object in the configured storage backend, typically a Kubernetes Secret in the release namespace, and retains that history indefinitely by default with no built-in maximum revision enforcement. The helm uninstall command preserves revision history unless --no-keep-history is specified, yet the client does
helm
kubernetes