helm: `helm list`error maximum size exceeded
Problem:
After installing kolla-kubernetes (a collection of helm charts resulting in many releases) and attempting to do a helm list from a remote client I receive the following error:
Error: grpc: received message larger than max (6645791 vs. 4194304)
This problem does not manifest when performing helm list on the server.
Currently the count of releases is 16 although I presume it also has to do with release size. Each release is composed of multiple sub-charts.
Version:
Client: &version.Version{SemVer:"v2.7.2", GitCommit:"8478fb4fc723885b155c924d1c8c410b7a9444e6", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.7.2", GitCommit:"8478fb4fc723885b155c924d1c8c410b7a9444e6", GitTreeState:"clean"}
Solutions:
Should I look into “chunking” the results as to not exceed the maximum or does someone have a better of idea of how to resolve this issue?
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 14
- Comments: 31 (13 by maintainers)
Commits related to this issue
- Fix race in helm list when partitioning Problem: The chunks slice that is passed through the channel is reused for each partition. This means that encoding the release into a message is racing with p... — committed to bmarshall13/helm by bmarshall13 6 years ago
- Fix race condition in `helm list` (#4620) * Fix race in helm list when partitioning Problem: The chunks slice that is passed through the channel is reused for each partition. This means that enc... — committed to helm/helm by bacongobbler 6 years ago
- Fix race condition in `helm list` (#4620) * Fix race in helm list when partitioning Problem: The chunks slice that is passed through the channel is reused for each partition. This means that enc... — committed to helm/helm by bacongobbler 6 years ago
- Fix race condition in `helm list` (#4620) * Fix race in helm list when partitioning Problem: The chunks slice that is passed through the channel is reused for each partition. This means that enc... — committed to splisson/helm by bacongobbler 6 years ago
- Fix race condition in `helm list` (#4620) * Fix race in helm list when partitioning Problem: The chunks slice that is passed through the channel is reused for each partition. This means that enc... — committed to splisson/helm by bacongobbler 6 years ago
- Fix race condition in `helm list` (#4620) * Fix race in helm list when partitioning Problem: The chunks slice that is passed through the channel is reused for each partition. This means that enc... — committed to splisson/helm by bacongobbler 6 years ago
- Fix race condition in `helm list` (#4620) * Fix race in helm list when partitioning Problem: The chunks slice that is passed through the channel is reused for each partition. This means that enc... — committed to splisson/helm by bacongobbler 6 years ago
Can confirm that we’re using helm 2.8.1 and seeing this issue:
You can upgrade helm in-place via
helm init --upgrade --history-max=10 ....Same as @jrthrawny but noticed that I can successfully do:
Adds some
.helmignoreand upgraded releases, and it reducedd a bit that number, but not a lot. I found no easy way to remove old release history without delete the entire release.@pashau see #3514; you can test using the canary clients 😃 otherwise we should be able to cut a v2.8.2 release some time by end of week
I too am experiencing this issue
Client: &version.Version{SemVer:"v2.8.0", GitCommit:"14af25f1de6832228539259b821949d20069a222", GitTreeState:"clean"} Server: &version.Version{SemVer:"v2.8.0", GitCommit:"14af25f1de6832228539259b821949d20069a222", GitTreeState:"clean"}