re-asking this: is there a recommended way to scale usage of the pulumi-k8s-operator?

what are you looking to scale? number of repos?

let's say hypothetically someone has single operator running in a k8s cluster and at one point there's changes made to 20 repos in quick succession, each one requiring that operator to update a stack. But just one operator won't be able to deploy these in parallel. Is there a recommended way to handle this type of situation?

we have a lot of improvements planned for this quarter, but the short answer now is to scale like any other operator: more controller pods

Thanks! Is one of the improvements to change the operator architecture into a controller-worker model? While one operator per namespace is a possibility, it's not quite ideal. But luckily I am not hitting this issue yet - it's just something I want to consider for the future.

we are still flehsing out the details, I'm sure @sparse-park-68967 would appreciate any feedback!

Is one of the improvements to change the operator architecture into a controller-worker model

This is tracked in https://github.com/pulumi/pulumi-kubernetes-operator/issues/78. Please upvote. We do intend to scope out our plans for this shortly.