Allow setting namespace in helm template
without a kubeconfig
#12126
+3
−0
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.
What this PR does / why we need it:
If you don't have a working kubeconfig,
helm template
does not respect the--namespace
option, instead silently ignoring it and using "default". It gets set on the settings object, but does not get returned by theNamespace()
method.helm template
should not require a working kubeconfig or any communication with a kubernetes cluster, as it is only generating templates.This PR adds a fallback to return the already set namespace field, rather than ignoring the user's intentions and returning "default".
Closes #12124
Special notes for your reviewer:
If applicable: