Support dynamic --api-versions and --kube-version in template
#11240
Comments
howardjohn
added a commit
to howardjohn/istio
that referenced
this issue
Aug 18, 2022
This allows `manifest generate` to use cluster specific settings as well. The only install method left is `helm template`; I have a bug filed in helm/helm#11240.
istio-testing
pushed a commit
to istio/istio
that referenced
this issue
Aug 26, 2022
This allows `manifest generate` to use cluster specific settings as well. The only install method left is `helm template`; I have a bug filed in helm/helm#11240.
mt-inside
pushed a commit
to mt-inside/istio
that referenced
this issue
Oct 12, 2022
This allows `manifest generate` to use cluster specific settings as well. The only install method left is `helm template`; I have a bug filed in helm/helm#11240.
|
This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs. |
|
Not stale |
|
This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs. |
|
I think its still useful personally but cannot re-open. Maybe will find some time to submit a PR to revive this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently,
helm templatetakes--api-versionsand--kube-version, which is great for use with charts that depend on these values.It is also, IMO, a good idea that these field are not auto-populated on
helm templateby default. However, when we do want them populated, manually inputting them is painful.It would be nice to add a flag to auto detect this (same as
helm install). This would be useful for cases likehelm template --detect-kube-version | kubectl apply -f -or equivalent, where we already know the cluster we are going to apply to eventually.The text was updated successfully, but these errors were encountered: