This message was deleted.

sparse-intern-71089

10/27/2021, 3:02 PM

This message was deleted.

gray-city-50684

10/27/2021, 3:03 PM

I have the following code:

Copy 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,
            }
        );

gray-city-50684

10/27/2021, 3:03 PM

It is inside a pulumi.ComponentResource

gray-city-50684

10/27/2021, 3:04 PM

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

gray-city-50684

10/27/2021, 3:05 PM

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

gray-city-50684

10/27/2021, 3:07 PM

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

gray-city-50684

10/27/2021, 3:08 PM

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

billowy-army-68599

10/27/2021, 4:01 PM

@gray-city-50684 there is a ready attribute on the helm chart which you can use: https://github.com/pulumi/pulumi-kubernetes/pull/1364

billowy-army-68599

10/27/2021, 4:01 PM

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

gray-city-50684

10/27/2021, 4:22 PM

Thx, I’ll try this right away

billowy-army-68599

10/27/2021, 4:28 PM

if you do want this level of readiness, the

helm.Release

resource might be a better bet

gray-city-50684

10/27/2021, 4:31 PM

Copy code

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.ready ],
                parent: this,
            }
        );

billowy-army-68599

10/27/2021, 4:32 PM

that should do it

gray-city-50684

10/27/2021, 4:34 PM

I had a compile error with this, but then I figured out (reading a bug report answered by Luke):

dependsOn:  linkerdChart.ready

is working, or do an apply on ready and then I can add other dependencies too

❤️ 1

gray-city-50684

10/27/2021, 4:34 PM

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

2 Views

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.