HIP Support Helm release data stored in multiple K8s Secrets

Open ralfv opened this issue 3 years ago • 1 comments

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.

Jun 20 '22 16:06 ralfv

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

May 23 '24 12:05 Hammond95