No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

If I recall correctly the `namespace` property on `Provider` instances used to be ignored, and was recently changed to actually set a default namespace.  That said, I agree it should not override the namespace if provided explicitly on a resource.

Could you open an issue?  This sounds like a bug to me.

ok makes sense. Yep, let me open an issue

Actually, that is the intended behavior, currently.
<https://github.com/pulumi/pulumi-kubernetes/pull/538/files#diff-5d82f691515dea3a9f870cf8d1a0fc84R74>
<https://github.com/pulumi/pulumi-kubernetes/pull/506#issue-265491527>

Feel free to open an issue if you disagree with that design, and we can discuss further.

If you don’t want the resource to be in that namespace, you can create a new provider that references the same kubeconfig/cluster without the namespace arg set.

just opened the issue <https://github.com/pulumi/pulumi-kubernetes/issues/576>