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

-.txt

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"

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. 

I tried to run with "pulumi up -p 0", but the same thing happened, it tried to create the kubernetes related resources sequentially

If you run with `-p 100` I expect it should work. 