Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Helm Chart Fails to Deploy

See original GitHub issue

When deploying the GitLab Helm chart on EKS the deployment hangs. If I run the same chart manually from Helm directly, it works just fine.

Expected Behavior

GitLab Helm chart should deploy just like I can from Helm CLI.

Current Behavior

Pods fail to start, Pulumi hangs.

Steps to Reproduce

Try running this:

const gitlab = new k8s.helm.v3.Chart("gitlab-server", {
    chart: "gitlab",
    fetchOpts:{
        repo: "https://charts.gitlab.io/",
    },
    values: {
        "certmanager-issuer": {
            email: "admin@mydomain.com",
        },
        global: {
            hosts: {
                domain: "mydomain.com",
            },
        },
    }
});

Context (Environment)

I’m going to have to use Helm to install GitLab which is fine but ideally I keep all my IaC in one place. This also makes me hesitant to use Pulumi’s Helm support because I’m unsure why this is failing.

Issue Analytics

State:
Created 3 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

4reactions

joeduffycommented, Jan 26, 2021

Since this issue is related to application configuration rather than Pulumi’s k8s provider, I’m going to close this out now.

A chart written for Helm, which gets to define the rules of what is a legal Helm chart, could not be deployed by a default Pulumi configuration. That very much feels like a Pulumi problem to me.

0reactions

lblackstonecommented, Jan 26, 2021

It appears that the root of the problem is related to the GitLab configuration you’re using, but here’s a workaround to skip the readiness checks so that you get the same behavior as vanilla Helm (create the resources, but don’t check for readiness):

const gitlab = new k8s.helm.v3.Chart("gitlab", {
    chart: "gitlab/gitlab",
    fetchOpts: {
        repo: "https://charts.gitlab.io/",
    },
    values: {
        "certmanager-issuer": {
            email: `cameron@${domain_name}`,
        },
        global: {
            hosts: {
                domain: domain_name,
            },
        },
    }
}, {
    transformations: [
        (args: pulumi.ResourceTransformationArgs) => {
            if (args.props.metadata) {
                return {
                    props: {
                        ...args.props,
                        metadata: {
                            ...args.props.metadata,
                            annotations: {
                                ...args.props.metadata.annotations,
                                "pulumi.com/skipAwait": "true",
                            }
                        }
                    },
                    opts: args.opts,
                }
            }
            return undefined;
        },
    ]
});

We’ve opened the following issues to track improving this experience:

Since this issue is related to application configuration rather than Pulumi’s k8s provider, I’m going to close this out now.