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

You can generate the kubeconfig to be used with the kubernetes provider: <https://github.com/pulumi/examples/blob/267aba12c943d7a8032dee2676d1b8ab0a344695/gcp-ts-gke/cluster.ts#L43|https://github.com/pulumi/examples/blob/267aba12c943d7a8032dee2676d1b8ab0a344695/gcp-ts-gke/cluster.ts#L43>

I'd recommend keeping app deployment in a separate stack to cluster creation/management though

Ah, cool, thanks! :slightly_smiling_face:

<@U04D2DBKUF9> is there any documentation about good practices for separating IaC from app/manifest code? Like, how to properly structure configs + directory structure etc

I, too, would recommend separating the cluster and the application into separate stacks---they (quite likely) have different lifecycles.

Mostly, yes, but since I'm doing this for a self-managed service that's built by a third party, I'm putting it all together. In general, though, that's a good point, I agree :slightly_smiling_face: