You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We could really use a load balancer in ESI. To expose openshift nodeport services via the existing "floating ip port forwarding" mechanism, we are only able to forward to a single worker node. If this node goes offline, we lose access to all our services (which would probably render all hosted clusters unusable). A load balancer would allow us to forward that traffic to "all worker nodes" (or a subset thereof), so that we can offer a more robust service.
A question though - shouldn't this sort of failover handled in the OpenShift architecture? If we move towards the ACM/baremetal-operator model, I don't think we'd be able to take care of this use case in OpenStack.
A question though - shouldn't this sort of failover [be] handled in the OpenShift architecture?
Load balancers at the network layer are an extremely common bit of infrastructure -- we're making use of them for effectively all of our public-facing openshift clusters. Having something like this available in ESI would be incredibly useful, and not just for OpenShift.
It's possible to solve this in OpenShift instead, but having this feature at the network layer is substantially simpler.
It's unfortunate that Octavia seems to have a fairly weighty set of requirements (it appears to requires both Nova and Barbican, for example).
We could really use a load balancer in ESI. To expose openshift nodeport services via the existing "floating ip port forwarding" mechanism, we are only able to forward to a single worker node. If this node goes offline, we lose access to all our services (which would probably render all hosted clusters unusable). A load balancer would allow us to forward that traffic to "all worker nodes" (or a subset thereof), so that we can offer a more robust service.
LBaaS docs
The text was updated successfully, but these errors were encountered: