Inconsistent default namespace selection for Helm chart #1503
Labels
area/helm
kind/bug
Some behavior is incorrect or out of spec
mro2
Monica's list of 2st tier overlay related issues
resolution/fixed
This issue was fixed
By default, if a helm chart is deployed without a namespace - it is deployed into the
default
namespace. This behavior is different from other resources in this provider which default to the namespace specified in the provider config (or in the kubectl context).It would be ideal if the chart can be deployed into the namespace specified in the stack config. Alternatively, if this behavior is intentional it would be helpful if this could be documented and/or raise a warning.
Thank you!
Expected behavior
When no namespace is provided, the Helm chart resource should use the namespace specified in the provider selection logic specified here:
Current behavior
The default namespace is hard-coded to
default
. This behavior is programmed here:https://github.com/pulumi/pulumi-kubernetes/blob/155b56cd0718c05fe46e50d5fdbcc2f9a27d9f8f/provider/pkg/provider/invoke_helm_template.go#L205:L208
Steps to reproduce
pulumi config set kubernetes:namespace not-default
not-default
namespace as defined in the provider config:kubectl get all -n not-default
default
namespace despite the provider config.kubectl get all -n default
Context (Environment)
I am using Pulumi to orchestrate a stack that involves a helm chart along with a few different Kubernetes resources. I was expecting that the behavior for namespace selection would be the same across the entire provider.
Affected feature
PR: #1323
Issue: #1321
The text was updated successfully, but these errors were encountered: