Make sure that all of your k8s resources are setting the
provider
opt to that exported value. If this opt is not set, it will default to using the ambient kubeconfig settings, so it may be pointing to a locally configured cluster by mistake.
p
purple-coat-77714
01/28/2020, 5:22 PM
Ah yes thats it! For one of the resources I forgot to set the provider. This saved me a ton of googling, thank you!
👍 1
g
gorgeous-egg-16927
01/28/2020, 5:23 PM
Some users also like to set an invalid
kubeconfig
as part of the stack config to prevent this mistake.
pulumi config set kubernetes:config:kubeconfig "dummy"
gorgeous-egg-16927
01/28/2020, 5:23 PM
This will cause those resources to fail with an error
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.