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

Maybe this is a bit more complex than just one index.ts? <https://github.com/pulumi/examples/tree/master/kubernetes-ts-multicloud>

I’m pretty happy using `ComponentResource`s for encapsulating things instead of plain classes because eventually you’ll pass down some `pulumi.Output`s.

Besides that I also use several stacks and `StackReference`s to avoid putting too many resources into one project/stack that don’t really have a 1:1 relationship. But this takes some caution to not end up in exporting/importing tens of properties just to get some association right (good example here is AKS, DNS, Service Principals, Resource Group Names required for the LoadBalancer public IP).

You might also be interested in <https://www.pulumi.com/docs/guides/crosswalk/kubernetes/>

These guides include links to a GitHub repo with full examples

<https://github.com/pulumi/kubernetes-guides>