helm: Upgrades fails with: grpc: received message larger than max
After adding more grafana dashboards that are populated via configmap from files:
{{ (.Files.Glob "assets/generated/*.json").AsConfig | indent 2 }}
And running upgrade: helm upgrade --install -f values-staging.yaml dev .
I’m now receiving:
Error: UPGRADE FAILED: grpc: received message larger than max (4290838 vs. 4194304)
After deleting some of the larger dashboard files it works again. This might be related to https://github.com/kubernetes/helm/issues/3322
Client: &version.Version{SemVer:"v2.8.1", GitCommit:"6af75a8fd72e2aa18a2b278cfe5c7a1c5feca7f2", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.8.1", GitCommit:"6af75a8fd72e2aa18a2b278cfe5c7a1c5feca7f2", GitTreeState:"clean"}
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 2
- Comments: 16 (6 by maintainers)
Commits related to this issue
- Bump client side grpc max msg size Set it to match the server side, or the default limit of 4MB will still apply when upgrading charts. Fixes #3512 — committed to joonix/helm by balboah 6 years ago
- Bump client side grpc max msg size Set it to match the server side, or the default limit of 4MB will still apply when upgrading charts. Fixes #3512 — committed to joonix/helm by balboah 6 years ago
- Bump client side grpc max msg size Set it to match the server side, or the default limit of 4MB will still apply when upgrading charts. Fixes #3512 — committed to joonix/helm by balboah 6 years ago
- Bump client side grpc max msg size Set it to match the server side, or the default limit of 4MB will still apply when upgrading charts. Fixes #3512 (cherry picked from commit 98e5006ecfefe7c1b1ab10... — committed to helm/helm by balboah 6 years ago
- Bump client side grpc max msg size Set it to match the server side, or the default limit of 4MB will still apply when upgrading charts. Fixes #3512 — committed to splisson/helm by balboah 6 years ago
- Bump client side grpc max msg size Set it to match the server side, or the default limit of 4MB will still apply when upgrading charts. Fixes #3512 — committed to splisson/helm by balboah 6 years ago
- Bump client side grpc max msg size Set it to match the server side, or the default limit of 4MB will still apply when upgrading charts. Fixes #3512 — committed to jianghang8421/helm by balboah 6 years ago
I’m getting this on v2.8.1 and v2.7.2 and v2.6.2 and v2.5.1. Couldn’t go further back, Tiller v2.4.1 won’t deploy on k8s 1.8.
EDIT: this was caused by having an undesired large file in my chart directory. #3563
Large file in chart directory was also the source for me.
I had a really large (unnecessary log) file in my project. Upon removing, that fixed the issue. To further avoid this problem add unnecessary files in
.helmignore.if you have kept your chart.yaml and templates in the same directory as in source directory, this happens. So better structure is to put all helm related stuff in a separate directory.
e.g. src -> helm-> Chart.yaml and templates -> *.yaml
Check if there’s any artifacts in your chart directory that shouldn’t be there. 475MB seems like an abnormally large chart.
@balboah @bacongobbler @koenfaro90 @mausch I am also experiencing same issue,
helm version Client: &version.Version{SemVer:“v2.9.1”, GitCommit:“20adb27c7c5868466912eebdf6664e7390ebe710”, GitTreeState:“clean”} Server: &version.Version{SemVer:“v2.9.1”, GitCommit:“20adb27c7c5868466912eebdf6664e7390ebe710”, GitTreeState:“clean”}
helm upgrade name charts --set fe_image.tag=test0.0.234 Error: UPGRADE FAILED: grpc: received message larger than max (475664632 vs. 20971520)
Kindly suggest what is the best way to fix this issue.