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

Config set on the first-class provider should override ambient config. Precedence is
1. First-class provider
2. pulumi config values
3. Ambient KUBECONFIG

If that’s not the case for you, please file an issue on the pulumi-kubernetes repo

Okay cool, i will do some testing and make sure this is working correctly.

for me, I had missed setting the provider on one resource which meant it was reverting to the `KUBECONFIG` var

Would be nice to disable the KUBECONFIG var since my shell does some automatic work to set this and allow me to quickly switch files. I only want pulumi to use config and fiest-class.

else it could cause some issues with modifying clusters that I did not mean too

<https://pulumi-community.slack.com/archives/CRFURDVQB/p1580232202054500?thread_ts=1580231515.053800&amp;cid=CRFURDVQB> has a workaround

We’ve also considered adding a stack configuration to disable ambient KUBECONFIG. It’s nice for users getting started, but can cause the problem you found.

Here’s a tracking issue for that: <https://github.com/pulumi/pulumi/issues/3383>

Okay cool, I just commented on that issue.

setting the dummy value should fix it for now