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 :slightly_smiling_face: Does the stack in K8s should be in the same namespace as the pulumi-operator itself?

nope, with the v2 operator at least stack/workspace/program lives in the "user" namespace.

Great. How to handle `PULUMI_ACCESS_TOKEN` in that case? Since stack cannot reference to secrets in different namespace. Create same secrets in all namespaces?

yeah, you have to create secrets in the same namespace as the stack (same for git source, etc..). At the end it depends how you manage things, you could also throw all stacks into the same namespace.

Thanks for response. One namespace it is then. I'm need to enable developers to create stacks themselves, so I guess I'll need to create a CRD for that or prepare a stack YAML template with those tokens predefined :smile: