-
Notifications
You must be signed in to change notification settings - Fork 155
helm secrets triggering increase in history over 1Meg etc limit #161
Comments
I added to my .helmignore the following and it resolved the issue. Would this break anything if we plan to roll back to older helm deployment ? |
@diepes I think this issue that you have is connected with old issue helm/helm#1413 now moved to helm/helm#8281. How big are your configmaps? |
@kaarolch They went over the 1meg limit, currently with the secrets.yaml excluded back down to 700kb.
I logged the issue under helm-secrets, as by default when adding a sops encrypted secrets.yaml to your helm template, it seems |
@diepes Whats your path of secret.yaml? I can't see my encrypted files via |
Error: UPGRADE FAILED: create: failed to create: Secret "sh.helm.release.v1.xxx-dev.v3360" is invalid: data: Too long: must have at most 1048576 characters
I think this is triggered because helm saves all the files in the chart dir to the history.
with helm secrets upgrade, the secrets.yaml and the secrets.yaml.dec end up in the history.
Am i correct that i can solve this by adding secrets.yaml to my .helmignore file ?
The text was updated successfully, but these errors were encountered: