Bump helm.sh/helm/v3 from v3.9.4 to v3.10.2 #1006
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We are facing timeouts on clusters that have a huge amount of CRDs. It seems this release of helm contains a couple of fixes like caching.
Compare v3.9.4 vs v3.10.2
When bumping to this release of helm it also bumps the
k8s.io/…
dependencies from0.24.2
to0.25.2
as soon you rungo mod download
, so those have to be in the same batch.Hopefully bumping the helm version resolves those issues. The issue can easily be reproduced by installing the Crossplane Upbound AWS provider in a cluster. Then try to use this provider to deploy some other helm charts. They will simply timeout due to client side throttling.
Acceptance tests
N.A.
I have tested locally using
make build
.Release Note
Release note for CHANGELOG:
References
Community Note