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

How to disable ambient k8s? re: <https://www.pulumi.com/docs/intro/cloud-providers/kubernetes/setup/#kubernetes-configuration>

I'd like to do a `config.require('kubernetes:context')` to ensure only the expected cluster gets modified by Pulumi, but this seems to be scoped to the stack

I want to make sure folks who fork my pulumi program don't mess up their default k8s context, whatever that happens to be on their machines... I'd like them to be explicit about the k8s cluster they want to target

or is there a way to change the default k8s provider to use one instantiated in code?

the prospect of adding

```{
  provider: myK8sProvider
}
```
on all my resources' constructors seems tedious...

Hey Paul - I recently asked a similar question:

<https://pulumi-community.slack.com/archives/C84L4E3N1/p1623109482120700|https://pulumi-community.slack.com/archives/C84L4E3N1/p1623109482120700>