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

Yes: a `kubeconfig` that is usable with the cluster is exported by the EKS component.

So in the Pulumi program that stands up your EKS cluster, you can do the following:

```
export const kubeconfig = cluster.kubeconfig;
```

(assuming you did `const cluster = new eks.Cluster(...);` earlier)

How does that feed into the helm chart deployment?

Once your stack has been created, you can run

`pulumi stack output kubeconfig &gt; eks-kubeconfig.json`

and then set the `KUBECONFIG` environment variable to point to `eks-kubeconfig.json`

Can this be done programmaticaly so I can just do `pulumi up` without running other commands?

i.e. that you're deploying the EKS cluster and the charts in the same Pulumi program

E.g. code the kubeconfig as the input to the helm chart:

something like:
```
// Deploy the Splunk forwarder to the cluster
const wordpress = new k8s.helm.v2.Chart("splunk-forwarder", {
    kubeconfig: cluster.kubeconfig,
    repo: "sdp-helm",
    version: "0.2.75",
    chart: "splunk-forwarder",
});
```

```
// Deploy the Splunk forwarder to the cluster
const wordpress = new k8s.helm.v2.Chart("splunk-forwarder", {
    repo: "sdp-helm",
    version: "0.2.75",
    chart: "splunk-forwarder",
}, {providers: {kubernetes: cluster.provider}});
```

The critical piece being `{providers: {kubernetes: cluster.provider}}`