HIP Support Helm release data stored in multiple K8s Secrets

helm / community

Helm community content

https://helm.sh

417 stars 175 forks source link

HIP Support Helm release data stored in multiple K8s Secrets #256

Open ralfv opened 2 years ago

ralfv commented 2 years ago

Helm release data encoded into the release field in a Kubernetes Secret can cause the Secret as a whole to exceed 1 MiB (as defined by MaxSecretSize in kubernetes/pkg/apis/core/types.go).

When this happens, the Kubernetes Secret cannot be stored in Etcd and the Helm install or upgrade fails.

Splitting the Helm release data across multiple Kubernetes Secrets resolves this problem.

Hammond95 commented 4 months ago

will this ever be implemented? Could you please provide a solution to this problem?