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.

Pulumi Community

Not sure if this helps but this shows how it can be done with C# if I understand right <https://github.com/pulumi/examples/blob/master/azure-cs-aks-helm/MyStack.cs>

I tried this approach, but it just stuck forever on pulumi up

hi <@U02H5JANBV3>,
I managed to get it work like this (I'm using TS).
```const certManagerRelease = new k8s.helm.v3.Release(
      'cert-manager', 
      {
        chart: "cert-manager",
        version: version,
        repositoryOpts: {
          repo: repoUrl
        },
        values: { 'installCRDs': true },
        namespace: 'cert-manager'
      },
      {
        parent: this,
        dependsOn: [cluster],
        provider: cluster.provider
      }
    );```
Perhaps you want to make sure that pulumi is fetching the chart correctly, which you can test by setting the parameter *`{verify: true}`* in args.
As for the provider, you can pass it on the opts. I found these docs that are really insightful: <https://www.pulumi.com/docs/tutorials/kubernetes/gke/>
```export const kubeconfig = pulumi.
    all([ cluster.name, cluster.endpoint, cluster.masterAuth ]).
    apply(([ name, endpoint, masterAuth ]) =&gt; {
        const context = `${gcp.config.project}_${gcp.config.zone}_${name}`;
        return `apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: ${masterAuth.clusterCaCertificate}
    server: https://${endpoint}
  name: ${context}
contexts:
- context:
    cluster: ${context}
    user: ${context}
  name: ${context}
current-context: ${context}
kind: Config
preferences: {}
users:
- name: ${context}
  user:
    auth-provider:
      config:
        cmd-args: config config-helper --format=json
        cmd-path: gcloud
        expiry-key: '{.credential.token_expiry}'
        token-key: '{.credential.access_token}'
      name: gcp
`;
    });

// Create a Kubernetes provider instance that uses our cluster from above.
const clusterProvider = new k8s.Provider(name, {
    kubeconfig: kubeconfig,
});```
This works like a charm on GCP. Basically, what you want to do is to implement a provider factory that you can pass to your Helm.Release resource.

Hope this helps,