Estimate the total manifest size of a Helm release stored in cluster secrets.
Every Helm install or upgrade stores a full release record — rendered manifests, hook definitions, and NOTES.txt — as a Secret (or ConfigMap) in the release namespace. Because Helm keeps a configurable number of historical revisions for rollback, the actual in-cluster storage footprint is the per-revision payload multiplied by how many revisions are retained, which is easy to underestimate on charts with large CRD manifests.
totalStorage = (manifests + hooks + notes) × revisions
By default Helm 3 stores each release revision as a base64-encoded, gzip-compressed Secret in the release's namespace (storage backend is configurable to ConfigMaps or SQL).
Helm keeps a history of past revisions to support `helm rollback`. Each retained revision is a separate stored object, so storage grows linearly with `--history-max` until old revisions are pruned.
Lower `--history-max` (default 10), split very large charts into smaller subcharts, and avoid embedding large static assets or verbose CRDs directly in templated manifests.