Jack Lindamood

I have a similar problem. I resolved it by running explicitly ``` < go get -u k8s.io/cli-runtime go: downloading k8s.io/cli-runtime v0.23.1 go get: upgraded k8s.io/cli-runtime v0.22.4 => v0.23.1 go get:...

Exactly what i want!

I suppose one option is that the client becomes non blocking and each client sends on multiple open connections. My goal would be to see if there is a use...

My perspective would not be about gaining a performance increase, but measuring the language with the least performance decrease.

That seems reasonable.

Do all servers equally misbehave? I'm curious where that breaking point is.

Another option is to increase the timeout on the client side?

Threads work fine. For our use cases, the NOTES of a helm chart are interesting when a chart is first installed, but not so helpful when a chart is updated....

> Slightly worried it might get very long, especially if the diff covered multiple files To clarify, I'm talking about `helm get values`, not the entire template (`helm get all`)

We follow a best practice of never putting sensitive values in helm charts. They are usually secrets that are created with either https://github.com/godaddy/kubernetes-external-secrets or https://github.com/bitnami-labs/sealed-secrets