New idea proposal vetting - split large Helm encoded release data across multiple K8s secrets


Some of our charts create during install/upgrade secrets that are bigger than 1MB. Then Helm install/upgrades fail.
We can take some measures to remove content and cleanup charts but we can only do so much.
Our idea is to have Helm create multiple secrets to hold a Helm release.
The encoded release data would be split across multiple secrets created as needed if the encoded release data is > 1MB.
We have a working implementation of this implemented as an additional storage driver called "chunkedsecrets" which can be enabled by setting the HELM_DRIVER=chunkedsecrets environment variable.
But we feel it is better to integrate chunking into the standard secret/secrets storage driver and add automatic chunking only if the size of the encoded release data becomes too big.

Join to automatically receive all group messages.