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

Most examples are just pulling in the kubeconfig via a stack reference from elsewhere.

<@UFM2CJXA5> the `getClusterOutput` will return the:

certificateAuthority data : <https://www.pulumi.com/registry/packages/aws/api-docs/eks/cluster/#data_nodejs>
endpoint: <https://www.pulumi.com/registry/packages/aws/api-docs/eks/cluster/#endpoint_nodejs>

You can use that to generate your own kubeconfig: <https://github.com/pulumi/examples/blob/258d3bad0a00020704743e37911c51be63c06bb4/aws-py-eks/utils.py#L4-L39>

Thanks! Definitely seems like something that would be a great feature exposed from `pulumi/eks`, since it does all this already.

pulumi/eks manages creating a cluster and exports a kubeconfig. I don’t expect we’ll add support for existing clusters to that