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 may see some performance issues but I don't have concrete numbers. I will say I try to encourage customers not to have large stacks mainly because of the "blast radius" consideration. Is there a reason your stacks are so large?

We are deploying on demand software on top of on demand (shared/dedicated) k8s clusters. Going to use the automation api to handle that  (everything is built ourselves atm) and i’m exploring stack references and trying to determine the “optimal” setup.

This question came from the idea, that if i have shared clusters and a single stack per cluster. But i ’m currently doing a separate stack for a cluster and then a stack per namespace.

feels “better” under control if i do small parts. Just needs a bit more stack management.