Calculate the rendered manifest size produced by a Helm chart's templates.
The total size of a chart's rendered output is simply the count of distinct Kubernetes resources it produces multiplied by their average YAML size. This total matters because it feeds directly into etcd object storage, `kubectl apply` payload size, and — for Helm specifically — the size of the release record stored per revision, so charts with many CRDs or verbose ConfigMaps can meaningfully inflate it.
totalManifestSize = resourcesCount × avgResourceSize
Run `helm template <chart> | grep -c '^kind:'` or pipe the output through `yq` to split multi-document YAML and count distinct `kind`/`metadata.name` pairs.
Every applied resource becomes an object stored in etcd; very large manifests (e.g. big ConfigMaps holding embedded config files) count against etcd's per-object and total database size limits.
ConfigMaps/Secrets embedding full config files or certificates, CRDs with large schemas, and Deployments with long lists of environment variables or init containers.