[Helm/Release] Does not accept an Output in the chart values

The current implementation of k8s.helm.v3.Release is not accepting pulumi.Output in the chart values, which was supported in k8s.helm.v3.Chart from what I can tell, or at least the Chart did not error in the preview stage with the same values which the Release does.

In my case, I’m trying to deploy the ingress-nginx helm chart with a controller.service.loadBalancerIP value fed in from a previously created gcp.compute.GlobalAddress resource. Currently this fails in the chart rendering phase and I have to work around it.

[lblackstone]

Here’s a simpler repro case:

import * as random from "@pulumi/random";
import * as k8s from "@pulumi/kubernetes";

const nsName = new random.RandomPet("test");

const ns = new k8s.core.v1.Namespace("test", {
    metadata: {
        name: nsName.id
    }
});

new k8s.helm.v3.Release("nginx", {
    chart: "nginx",
    namespace: ns.metadata.name,
    repositoryOpts: {
        repo: "https://charts.bitnami.com/bitnami",
    },
    values: {},
});

Running pulumi up on an empty stack returns the following error:

  kubernetes:helm.sh/v3:Release (nginx):
    error: decoding failure: 1 error(s) decoding:

    * 'Namespace' expected type 'string', got unconvertible type 'resource.Computed', value: '{{}}'

[gitfool]

I’m also hitting this issue:

// aws load balancer controller; https://github.com/aws/eks-charts/tree/master/stable/aws-load-balancer-controller
Logger.LogDebug("Installing aws load balancer controller");
var awsLbcRole = new RoleX($"{k8sPrefix}-aws-load-balancer-controller",
    new RoleXArgs
    {
        AssumeRolePolicy = IamHelpers.AssumeRoleForServiceAccount(oidcArn, oidcUrl, "kube-system", "aws-load-balancer-controller", awsProvider),
        InlinePolicies = { ["policy"] = ReadResource("AwsLoadBalancerPolicy.json") }
    },
    new ComponentResourceOptions { Provider = awsProvider });

var awsLbcCrds = new ConfigGroup("aws-load-balancer-controller-crds",
    new ConfigGroupArgs { Yaml = ReadResource("AwsLoadBalancerCrds.yaml") },
    new ComponentResourceOptions { Provider = k8sProvider });

var awsLbcValues = Output.Tuple(clusterName, awsLbcRole.Arn).Apply(((string ClusterName, string RoleArn) tuple) =>
    new Dictionary<string, object>
    {
        ["clusterName"] = tuple.ClusterName,
        ["enableCertManager"] = true,
        ["serviceAccount"] = new { annotations = new Dictionary<string, string> { ["eks.amazonaws.com/role-arn"] = tuple.RoleArn } }
    }.ToDictionary());

var awsLbcRelease = new Release("aws-load-balancer-controller", // ingress records with alb.ingress.kubernetes.io annotations depend on chart finalizers
    new ReleaseArgs
    {
        Namespace = "kube-system",
        Name = "aws-load-balancer-controller",
        RepositoryOpts = new RepositoryOptsArgs { Repo = "https://aws.github.io/eks-charts" },
        Chart = "aws-load-balancer-controller",
        Version = K8sConfig.AwsLbcChartVersion,
        Values = awsLbcValues,
        SkipCrds = true,
        Atomic = true
    },
    new CustomResourceOptions { DependsOn = { awsLbcCrds, certManagerRelease }, Provider = k8sProvider });

Fails with error coming from aws-load-balancer-controller/deployment:

Diagnostics:
 
aws-load-balancer-controller (kubernetes:helm.sh:Release)
error: failed to create chart from template: execution error at (aws-load-balancer-controller/templates/deployment.yaml:52:28): Chart cannot be installed without a valid clusterName!

Where clusterName is valid and being passed, albeit via an output tuple.