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

I'm trying to figure out a safe way to use `pulumi-kubernetes`. Specifically, we have a shared setup and different developers have different clusters and contexts defined in their `.kube/config` (e.g. some devs run a local minicube cluster for testing).

I want to ensure that the stack is only applied to the cluster I want it applied to but I can't figure out how to do that. For example, I can explicitly construct a `Provider` passing `cluster=` to specify the cluster, but the `cluster` field refers to the name of the cluster in `~/.kube/config` file and it's just a nickname; each developer could pick a different nickname for the same cluster.

How can I (1) provide enough flexability for each dev to specify which kubeconfig, etc. to use and (2) still ensure that I'm going to apply my changes only to the desired cluster?

hmmm... Maybe the trick is to provide a full kubeconfig file contents so that the user can't change them and then provide a way for an individual user to override how they authenticate (e.g. if they need a proxy) so they can replace just the `user` part of the config?

Seems ugly but should work...