This message was deleted.

sparse-intern-71089

10/30/2019, 4:38 PM

This message was deleted.

calm-parrot-72437

10/30/2019, 5:03 PM

background: i created the cluster once successfully than realized I didn't do it under the right organization, so used pulumi to bring it down and removed the project. Added the org and tried to bring back up.

white-balloon-205

10/30/2019, 5:20 PM

Do you see this every time now? I don't think I've seen/heard this failure before.

how can i get more information to debug this further?

You could go into

node_modules/@pulumi/eks/cni.js

and put a

console.log()

applyVpcCniYaml

to see what

cniYamlText

and

kubeconfig

are being created.

calm-parrot-72437

10/30/2019, 5:22 PM

yeah, happens every time. Will try that, thx

white-balloon-205

10/30/2019, 5:47 PM

Did you also log the

kubeconfig

? I don't see it in the output here? I'd suggest trying to store the

kubeconfig

and

cniYamlText

in files manually and see if the

kubectl apply

command works when run manually. I'm not sure exactly what would cause it to fail in this way - but I assume it should fail if you do this yourself with the same inputs as well.

calm-parrot-72437

10/30/2019, 6:18 PM

sorry, how do i get the kubeconfig out? tmpKubeconfig is is the object

calm-parrot-72437

10/30/2019, 6:29 PM

given the code is just calling kubectl, I took the opportunity to check the client version and I was on 1.9. Upgrading to version 1.14 resolved the issue. Thanks Luke!

white-balloon-205

10/30/2019, 9:32 PM

Great to hear.

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.