Hello all, I have some issues with

pulumi-eks v3

. ManagedNodeGroup example crashes when I create k8s ressources with

parent:cluster

as opts. Also in my program, having some

dependsOn

causes some issues, like the resource not being created at all and completely ignored. Do some of you have noticed these kind of issues?

Hey, did I understand it correctly that you're adding a child to the

Cluster

component from outside of the component (by setting the cluster as the parent of the ManagedNodeGroup)? Adding a child to the component outside of the component can lead to cyclical dependencies and/or promise leaks. You could workaround that by not setting a parent, or setting the parent to

parent: cluster.eksCluster.id

instead. (see) The issue with dependsOn definitely sounds odd, do you mind opening a GitHub issue here with a minimal repro so we can further dig into it? Thanks!

ok thanks Florian. the

parent: cluster.eksCluster.id

does not work because of a type issue. The cluster as parent was working fine with

pulumi eks v1

, is there a change? For the

dependsOn

I stil have to reproduce it in the example.

Ah sorry, you're right. The

id

sneaked its way in there, you could try

parent: cluster.eksCluster

. Just out of curiosity, what's the reason for adding childs to the cluster? Previously pulumi-eks was just a regular npm package for nodejs, not a provider, while the other languages where already exposed via a multi-language component provider. This discrepancy had several drawbacks (e.g. inaccurate docs), due to that we aligned all the languages in v3 (see migration guide). We do not recommend parenting resources to components from outside of them as it can lead to these cyclical dependencies / promise leaks you're seeing. Without diving deeper I'm suspecting that it worked previously because there was no provider involved and the component was only local to your program.