You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Hidde Beydals 68f7b1f194 Properly invalidate client after CRD install ... As the CRDs are installed before the capabilities are gathered, the current call to invalidate the discovery client is premature and expensive. What actually is required is an invalidation of the REST mapper, as otherwise the Helm install action may later on fail with a `resource mapping not found` error. More specifically when the caller of the action is making use of a persisting[1] `RESTClientGetter`. Which is not something done by the Helm CLI (albeit it could, and this would potentially save quite some resources?). But is a default configuration offered by the Helm SDK via `kube.New` when a nil value is provided as the `getter`. [1]: https://github.com/kubernetes/cli-runtime/blob/v0.26.2/pkg/genericclioptions/config_flags.go#L118 Signed-off-by: Hidde Beydals <hidde@hhh.computer>		3 years ago
..
action	Properly invalidate client after CRD install	3 years ago
chart	change linting error messages for null values in arrays	3 years ago
chartutil	bump version to v3.11.0	3 years ago
cli	Check status code before retrying request	3 years ago
downloader	Fix after CR	3 years ago
engine	Update to func handling	3 years ago
gates	…
getter	Add test for User-Agent header setting and refactor	3 years ago
helmpath	…
kube	update k8s registry domain	3 years ago
lint	…
plugin	improve error message on plugin install	3 years ago
postrender	…
provenance	…
pusher	…
registry	…
release	Addressing review comments - move printing code out of client.go	4 years ago
releaseutil	…
repo	Fix User-Agent header in requests made by Helm	3 years ago
storage	fixes #11142 missing array length check on release	4 years ago
strvals	Fix backwards compatibility	3 years ago
time	…
uploader	…