I have the following code:

const linkerdChart = new k8s.helm.v2.Chart("linkerd2",
            {
                chart: "linkerd2",
                version: "2.10.2",
                namespace: "linkerd",
                values: {
                    ...
                },
                fetchOpts: {
                    repo: "<https://helm.linkerd.io/stable/>"
                },
                transformations: chartTransformations
            },
            {
                dependsOn: [ linkerdIdentityIssuerCertificate ],
                parent: this,
            }
        );

        const linkerdVizChart = new k8s.helm.v2.Chart("linkerd2-viz",
            {
                chart: "linkerd-viz",
                version: "2.10.2",
                namespace: "linkerd-viz",
                fetchOpts: {
                    repo: "<https://helm.linkerd.io/stable/>"
                },
                transformations: chartTransformations
            },
            {
                dependsOn: [ linkerdChart, linkerdIdentityIssuerCertificate ],
                parent: this,
            }
        );

It is inside a pulumi.ComponentResource

I would expect, that because the explicit dependsOn, the deployment of the linkerdVizChart to start only once the linkerdChart component has fully deployed the base chart

but that is not the case, which causes a problem, as the base chart is responsible to start a Kubernetes webhook, which in turn would do some side-container injection whn the Viz-chart is deployed

As the Viz-chart deployment starts too soon, it won’t be injected, and as it is required by the Deployments / Pods in there, they just keep on crash-looping

Is there any flag / workaround / trick, I could use to delay the Viz-chart deployment until the base-chart deployment fully finishes?

there are some limitations: https://github.com/pulumi/pulumi-kubernetes/issues/1773

I will also take a look at helm.Release, thx for the help!