https://pulumi.com logo
#general
Title
# general
c

cold-coat-35200

10/29/2018, 9:33 AM
I think I bumped into this issue: https://github.com/pulumi/pulumi/issues/1990 I'm using a slightly modified version of the eks lib with the kubernetes dashboard deploy enabled, which creates the dashboard based on yaml files: https://github.com/pulumi/eks/blob/master/nodejs/eks/cluster.ts#L427 As you can see it tries to create the service for the dashboard first, but fails, because unable to find any pods based on the selector, because the deployment didn't started. Read through the issue, but can't see a workaround for this, besides separating the yaml files and use "k8s.yaml.ConfigFile" instead of "k8s.yaml.ConfigGroup" with correct "dependsOn". Last week it worked out of the box, I assume the ordering was correct, today I destroyed the whole stack and found this issue
after it failed, I run "pulumi refresh", but it does not see that the service already exists, so when I run "pulumi up" the second time it fails with "error: Plan apply failed: services "kubernetes-dashboard" already exists"
w

white-balloon-205

10/29/2018, 3:25 PM
I suspect from the screenshot that you may have run into https://github.com/pulumi/pulumi/issues/2108 here. We will have a fix out for that today.
c

cold-coat-35200

10/29/2018, 4:38 PM
I tried to run with "pulumi up -p 0", but the same thing happened, it tried to create the kubernetes related resources sequentially
w

white-balloon-205

10/29/2018, 4:52 PM
If you run with
-p 100
I expect it should work.