Forum Discussion
Altocumulusopenshift multi cluster CIS HA
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
MVPI admit I am not the biggest specialist on CIS multi cluster with openshift or kubernetes but I could suggest following (323) Mark Dittmer - YouTube (see his videos and example config) and if needed to write an issue under his git examples mdditt2000 (mdditt2000) / Repositories · GitHub . You can also enable a debug to see if there is more info Collect Support data for CIS issues / CIS Troubleshooting — F5 CIS Operations Guide documentation
