Hello everyone, Starting a discussion thread about improvements that can be made to the Kubernetes networking attached to the FlinkBlueGreenDeployments. I have raised the issue that prompted this discussion in FLINK-38577 <https://issues.apache.org/jira/browse/FLINK-38577> and wanted to see what approaches people are thinking would be best.
As mentioned in the ticket the first thoughts I had would be something like 1 svc and 1 ingress that will dynamically bind to whatever FlinkDeployment is active. That way would avoid the need for multiple services and ingresses to keep coming up and keep naming + address of those resources stable despite the underlying Flink deployments changing. Have yet to prototype that though (will try to get something early this week there), but would love preliminary feedback and thoughts. Thanks, Daniel
