This message was deleted.

sparse-intern-71089

07/02/2019, 2:50 PM

This message was deleted.

busy-umbrella-36067

07/02/2019, 2:56 PM

The control plane is managed by Amazon, not having worker nodes should’t affect k8s operations

busy-air-16359

07/02/2019, 3:04 PM

sure, but a lot of resources are created by kubernetes operators these days

busy-air-16359

07/02/2019, 3:04 PM

if you kill the operator by removing the worker nodes, there is no way it can clean up its resources

busy-umbrella-36067

07/02/2019, 4:03 PM

I hadn’t thought of that, I think you could simulate the behavior you want by adding

dependsOn: this.defaultNodeGroup

here https://github.com/pulumi/pulumi-eks/blob/master/nodejs/eks/cluster.ts#L667

busy-umbrella-36067

07/02/2019, 4:04 PM

I’d be interested to hear if that manages to delete the K8S Resources deployed with the provider before it deletes the worker asg

busy-air-16359

07/02/2019, 4:41 PM

good point, I’ll try adding that

busy-air-16359

07/02/2019, 4:42 PM

I thought pulumi would figure out the dependency automatically, because the k8s provider is created from the aws/eks provider

busy-air-16359

07/02/2019, 8:05 PM

that did the trick, thx

👍 1

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.