Worker Controller can scale a drained version’s Kubernetes Deployment to 0 after scaledownDelay, then delete it later after deleteDelay.
We should verify what happens if, during that retention window, the version becomes Draining again because someone moves workflows onto it with a Versioning Override.
Expected behaviour: while the Deployment still exists, the controller should be able to scale it back up so workers can poll for that version again and resume/complete work. There is some existing logic that may already handle this for rollback/target-version cases, but we should add a regression test to confirm the drained-to-zero Deployment can be revived before deleteDelay expires. If the test fails, we may need a small adjustment to the scaling logic.
Worker Controller can scale a drained version’s Kubernetes Deployment to 0 after
scaledownDelay, then delete it later after deleteDelay.We should verify what happens if, during that retention window, the version becomes
Drainingagain because someone moves workflows onto it with a Versioning Override.Expected behaviour: while the Deployment still exists, the controller should be able to scale it back up so workers can poll for that version again and resume/complete work. There is some existing logic that may already handle this for rollback/target-version cases, but we should add a regression test to confirm the drained-to-zero Deployment can be revived before deleteDelay expires. If the test fails, we may need a small adjustment to the scaling logic.