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

how can i get more information to debug this further?

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.

Do you see this every time now?

I don't think I've seen/heard this failure before.

&gt; 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()` in `applyVpcCniYaml` to see what `cniYamlText` and `kubeconfig` are being created.

yeah, happens every time. Will try that, thx

pulumi up with addition console.log

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.

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

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!