RELEASED: Public: {YYYY-MM-RELEASE-DATE}
Resolved issues
- Managed controller’s URL was activated in OC before the controller was ready to serve traffic (BEE-1351)
-
The controller URL is now shown only after the underlying pod is ready and routing is registered by the load balancer. Previously, users were shown the URL immediately after provisioning/start, navigating to which could lead to a 503 Service Unavailable error during initial pod readiness. Now, users remain on the provisioning page where live pod status is visible, avoiding premature redirect and improving clarity during startup.