Kustomize support defaults to wrong namespace

[jaxxstorm]

What happened?

A customer is running a kustomize deploy within a Kubernetes cluster CI/CD pipeline.

They kustomize deployment does not set a namespace in the manifests.

The CI/CD pipeline runner sets .kube/config globally inside the pod it runs

When provisioning the resources, the kustomize deploy correctly targets the right cluster frok the KUBECONFIG but somehow inherits the namespace from the pipeline it's running in, which doesn't exist in the remote cluster.

Expected Behavior

The deployment should not inherit the namespace from where it's running

Steps to reproduce

It's not an easy repro, but.

• define a cluster
• run a pulumi up from a pod inside the cluster kustomize deployment with a kubeconfig for ANOTHER cluster, but don't set any namespace on the kustomize resources

Output of pulumi about

N/A

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[EronWright]

@jaxxstorm could you clarify which namespace is actually used? Is the context namespace in the .kube/config honored?

[jaxxstorm]

@EronWright no, it doesn't seem to be