Hey everyone,
Just wanted to share an update on the FlinkBlueGreenDeployment ingress enhancements we've been working on now that we have a higher fidelity prototype working. We have added support for parent-level ingress management to enable automatic traffic switching during Blue/Green transitions. Design Overview: We're adding an optional ingress field at the FlinkBlueGreenDeployment spec level (alongside the existing template field). When configured, the operator will create and automatically manage an ingress that routes to the currently active deployment. Key behaviours: Automatic backend switching - During state transitions (e.g., ACTIVE_BLUE → ACTIVE_GREEN), the ingress backend automatically updates to point to the active deployment's service Finalization integration - Ingress reconciliation happens during deployment finalization, so traffic only switches after the new deployment is confirmed ready. (i.e called in BlueGreenDeploymentService.finalizeBlueGreenDeployment) Backwards compatible - The ingress field is optional. Existing deployments work unchanged, and this won't affect FlinkDeployment-level ingress definitions in the template spec Would love to hear your thoughts on this approach. Any concerns about the approach or suggestions for improvements? We are cleaning up the PR on our side and hopefully have some code to accompany this description soon. Thanks again, Daniel
