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

Hey everyone!

I would like to ask a question about managing Kubernetes resources. A standard way to go is using Helm + Kustomize, but as complexity grows, working with (essentially) plain YAML starts to show its limitations (e.g. managing different environments, configuration, any logic, etc.).

Pulumi is able to <https://www.pulumi.com/docs/using-pulumi/adopting-pulumi/migrating-to-pulumi/from-kubernetes/#rendering-kubernetes-yaml|render Kubernetes YAML>, so my idea would be to replace Kustomize with a Pulumi program that generates K8s YAML. Note that this would NOT use Pulumi to manage K8s state, but really only generate YAML (this means any existing GitOps/Deployment setup stay exactly the same)

Is anyone using Pulumi in this way? Can someone offer more insights on this idea?

as a follow-up question, what would be the difference between using Pulumi to generate K8s YAML vs using the <https://github.com/learnk8s/templating-kubernetes/tree/master/python|K8s client libraries> directly?