Can the ambient configuration be disabled? I'm thinking, perhaps I can turn

pulumi config set kubernetes:context my-context

into a required variable(?) re: https://www.pulumi.com/docs/intro/cloud-providers/kubernetes/setup/#kubernetes-configuration My goal is to avoid running pulumi against the wrong cluster (I need to switch between two live clusters often...) Is there perhaps another defensible way to configure pulumi?

the way to handle this is to set a provider resource on your Kubernetes resources: https://www.pulumi.com/docs/reference/pkg/kubernetes/provider/ you can specify a specific context for each https://www.pulumi.com/docs/reference/pkg/kubernetes/provider/#context_nodejs

Didn’t know there was an ambient context for kubernetes