hi all, I'm playng with the pulumi kubernetes operator. In my use case we want to have an other system trigger a "sync" so we don't really need continous drift detection. I was a little surprised to see that the pulumi operator spins up a pod that just seems to sit there. For us that would mean wasted resources as we're talking a large number of stacks. I was hoping it'd be possible for the operator to spin up the "workspace pod" and do a "pulumi up" on demand rather than continously. Anyone know how it's meant to behave and whether it's possible to get rid of the pod when there's no need for it?

The

workspaceReclaimPolicy

might help https://www.pulumi.com/blog/pulumi-kubernetes-operator-2-0/#scalability