Hi Together, I´m using the Pulumi Operator 1.16.0 in a productive environment. As the number of stacks in the environment grows the operator takes over 20 mins to react on a stack change. Is there a solution for this version to gain more responsiveness? I already tried pod scaling without any effect. Another problem i faced is that the stack-crd status for some stacks is on failed but the resources that the stack is implementing are successfullly created/updated. Is there also a solution known, that we can rely on the stack state info?

Have you tried version 2.0 of the operator?

i will, but as long this is only beta its no option for our prod envs

I tossed a link to this thread in our engineering channel for K8s as this is beyond my expertise.

FWIW I am reasonably confident we'll be graduating 2.0 out of beta within the next 2-5 weeks.

nice, thanks for the info