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
Currently, most customers deploy F5 Container Ingress Services (CIS) on top of their existing BIG-IP infrastructure. This infrastructure is often configured in a High Availability (HA) setup with autosync enabled. Given this widespread usage pattern, clear and detailed documentation on HA configuration options is essential to ensure smooth integration and optimal performance.
It would be very useful to know, which CNIs supports using a single CIS that points to a floating selfIP that with failover to the standby unit in case of a HA event and which CNIs required two CIS (one per BIGIP).
I know that there is a different behaviour if you are using Flannel, compared to Calico or StaticRoutes
The text was updated successfully, but these errors were encountered:
Currently, most customers deploy F5 Container Ingress Services (CIS) on top of their existing BIG-IP infrastructure. This infrastructure is often configured in a High Availability (HA) setup with autosync enabled. Given this widespread usage pattern, clear and detailed documentation on HA configuration options is essential to ensure smooth integration and optimal performance.
It would be very useful to know, which CNIs supports using a single CIS that points to a floating selfIP that with failover to the standby unit in case of a HA event and which CNIs required two CIS (one per BIGIP).
I know that there is a different behaviour if you are using Flannel, compared to Calico or StaticRoutes
The text was updated successfully, but these errors were encountered: