This message was deleted.

sparse-intern-71089

09/26/2018, 3:55 PM

This message was deleted.

white-balloon-205

09/26/2018, 4:02 PM

cc @creamy-potato-29402 This error looks like it will happen when the

kubeconfig

cannot be found - meaning it isn't available in provider configuration and can't be found ambiently from the environment. Are you providing configuration via

new kubernetes.Provider(...)

creamy-potato-29402

09/26/2018, 4:05 PM

That's right

creamy-potato-29402

09/26/2018, 4:06 PM

Client go is failing to get a kube config file

white-balloon-205

09/26/2018, 4:08 PM

@creamy-potato-29402 Any tips on how to diagnose why this would be happening?

creamy-potato-29402

09/26/2018, 4:10 PM

It is ought to be fairly straight forward: KUBECONFIG env var is not set, and there is no kubeconfig at ~/.kube/config

wooden-toddler-96888

09/26/2018, 4:14 PM

Oh.... wait let me try that. Any way to repro this locally? That way I can rinse-repeat without pushing out to github. I assume my ~/.kube/config is being picked up locally, and deleting that should repro this?

creamy-potato-29402

09/26/2018, 4:22 PM

It should

creamy-potato-29402

09/26/2018, 4:23 PM

I suspect you're not using the eks provider though

creamy-potato-29402

09/26/2018, 4:24 PM

So when deploying locally you are just deploying to the active context in your kubeconfig

2 Views

Open in Slack

Previous Next

Pulumi Community

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.