Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Best Practices on BIGIP HA with CIS depending on the CNI used. #3730

Open
skenderidis opened this issue Jan 27, 2025 · 1 comment
Open

Best Practices on BIGIP HA with CIS depending on the CNI used. #3730

skenderidis opened this issue Jan 27, 2025 · 1 comment

Comments

@skenderidis
Copy link

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

@trinaths
Copy link
Contributor

Created [CONTCNTR-5194]for internal tracking.

@trinaths trinaths added JIRA and removed untriaged no JIRA created labels Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants