abundant-author-13372
02/12/2020, 12:33 PMconst vpc = new awsx.ec2.Vpc(name, {
subnets: [{type: 'public'}],
tags: tags,
});
const cluster = new eks.Cluster(name, {
vpcId: vpc.id,
subnetIds: vpc.publicSubnetIds, }
Any idea on why it's not destroying properly? Could this be a bug? It's happened before, and I've had to go and manually destroy some underlying resources (load blancers I think). I do have some Helm charts deployed in the cluster (manged with pulumi as well) that include Load Balancer services, and these seem to be scheduled for destruction after the subnet and ig. Might this be it? any suggestions on how to properly manage dependencies for these charts?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.
Powered by