Skip to content

Helm releases do not show up if there is a large number of releases #15

Open
@stv-io

Description

I have noticed that on installing v0.2.0 - if the cluster is relatively small (small number of releases) then the helm list shows up fine. For larger clusters - the list seems to be fetched, however the app keeps spinning forever, while the following logs are generated:

2021-09-28T14:56:42.283+0200	ERROR	api/content_manager.go:159	generate content	{"client-id": "133c6cf8-205b-11ec-a01c-acde48001122", "err": "generate content: grpc client content: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (34810808 vs. 16777216)", "content-path": "helm"}
github.com/vmware-tanzu/octant/internal/api.(*ContentManager).runUpdate.func1
	github.com/vmware-tanzu/octant/internal/api/content_manager.go:159
github.com/vmware-tanzu/octant/internal/api.(*InterruptiblePoller).Run.func1
	github.com/vmware-tanzu/octant/internal/api/poller.go:86
github.com/vmware-tanzu/octant/internal/api.(*InterruptiblePoller).Run
	github.com/vmware-tanzu/octant/internal/api/poller.go:95
github.com/vmware-tanzu/octant/internal/api.(*ContentManager).Start
	github.com/vmware-tanzu/octant/internal/api/content_manager.go:133

Unfortunately I can't help much on this myself. I've replicated this, both on a read-only instance running within the cluster itself, as well as using a macos local install.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions