This message was deleted.

I believe you are hitting the issue in https://github.com/pulumi/pulumi-kubernetes/issues/861. @gorgeous-egg-16927 may have additional thoughts beyond what's already captured in the issue there.

Thanks Luke for providing the link ... Just reading up on the issues... https://github.com/pulumi/pulumi/issues/3282#issuecomment-606907860 you marked Node.js as being fixed, but I am experiencing it using Node.js...

@red-area-47037 our helm implementation just uses

helm template

but it also doesn't support the dependencies in the right way. One thing you can do is run

helm template --values v.yaml

and then pass that rendered yaml into https://www.pulumi.com/kube2pulumi/

@billowy-army-68599 thanks for the tip... good to have options 😉 I am a bit hesitant as this - as you say - introduces additional steps / effort as we use a number of helm charts. Any chance that the issue linked by Luke gets fixed in the foreseeable future? In #861 Luke mentioned that Node.js should be fixed and although it is not working for me at least I have the hope that there is some interest to get this fixed. If this related to the implementation using

helm template

why is dependsOn also not working for

ConfigFile

(https://github.com/pulumi/pulumi-kubernetes/issues/1315)? When I was thinking about how to work around the issue I thought maybe I will use the install yaml offered by some of the projects, but this would also not solve the issue as it seems... And I think then #1315 was marked incorrectly as a Duplicate of #861, or? In the current state it limits the usefulness of

Helm

and

ConfigFile

in a bit more complex scenarios (non demo / examples) quite a bit as it impacts the reliability 😞

We made some progress on fixing the underlying issue recently; there’s a WIP PR here: https://github.com/pulumi/pulumi-kubernetes/pull/1364. I’m hoping to finish that work in the not-too-distant future, but we don’t have a firm timeline yet. As you noted, this affects both the Helm

Chart

and YAML `ConfigFile`/`ConfigGroup` APIs. In short, the issue is that they rely on creating resources inside an

apply

, meaning that child resources don’t get registered as dependents automatically. In the meantime, your options are 1. Convert to native Pulumi resources as Lee suggested 2. Use the

getResource

method to manually depend on resources of interest (see https://github.com/pulumi/pulumi-kubernetes/blob/743646b17c68a6863355f0109825f60de2ca0452/tests/sdk/nodejs/istio/step1/istio.ts#L43-L69)

@gorgeous-egg-16927 thanks for the additional background. Looking forward to your WIP PR, I know it is hard to give firm fix date, but as long as it is high on the priority list I am happy. I think I will investigate option 2 as a workaround first. But I think there should be a remark in the documentation of

dependsOn

which describes the currently limitations as it cost me and others quite some time to investigate and try work arounds (e.g.. see https://github.com/pulumi/pulumi-kubernetes/issues/1315#issuecomment-692282116). Happy to contribute to the documentation if this is possible,

Thanks for the PR. Yes, we’re planning to fix both Helm and YAML. This issue impacts a lot of users, so it’s definitely high priority.

I just saw that the PR has been merged and released as part of v2.7.0, great 😉 I will test in the next few days