Forum Discussion
openshift multi cluster CIS HA
- Feb 26, 2025
I think I found the reason. The check probe of bigip-ctlr was configured as an Openshift route managed by cis itself. So when starting the primary CIS it had to configure this first on the F5 to get the health check to work. While the secondary did not had this route and was still active, so blocking the creation of this route.
Creating a static route for the health check, using the default ingress controller on port 80 solved the issue
The logging is not the only issue. 2.19.1 also doe snot create F5 objects in HA cis active-active mode on the primary CIS. The secondary CIs works fine. Switched the primary back to 2.18.1 for now.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com