RELEASED: Public: May 28, 2025
Resolved issues
- HA managed controller startup probe did not handle cold start (BEE-57225)
-
When an HA managed controller defined a startup probe, during a cold start (scale up from zero replicas) the timeout would take effect (after the configured initial delay) for all replicas, even though only one can start at a time. Now the startup probe failure threshold at the Kubernetes level is implicitly multiplied by the configured maximum replica count, while the configured timeout will be applied to each replica internally.
Note that an effect of this change is that changing the replica or maximum replica fields may trigger a rolling restart of the controller.
- Fixed Race Condition in Non-Concurrent Pipelines Causing Simultaneous Builds in HA (BEE-57279)
-
Resolved an issue in High Availability (HA) environments where pipelines using the disableConcurrentBuilds() option could incorrectly run multiple builds at the same time across replicas. This fix ensures that non-concurrent pipeline settings are consistently respected.