F5 BIG-IP deployment with Red Hat OpenShift - the no CIS option

Overview There are deployments where F5 BIG-IP is used in front of a Red Hat OpenShift cluster without the Container Ingress Services (CIS) controller. In general, this is not recommended because w...
Updated Oct 02, 2025
Version 4.0
cloud
devops
Red Hat OpenShift
Ulises_Alonso's avatar
Icon for Employee rankEmployee
Solutions architect in Business Development with focus in automation and integration with partner's technologies. Prior to this role I was consultant in Professional Services and escalations engineer in Technical Support. Outside F5, I worked in mobile and wired network operators as network engineer. I started my career in academic research. In all these years, no matter what I've been doing Linux has been always the best tool. Not the one in the picture :-)
View Profile
anael's avatar
anael
Icon for Nimbostratus rankNimbostratus
Sep 30, 2025

Hello, thank you for this article, it is very helpfull.


For the API monitor, you are using the "/healthz" enpoint.
However, in the RedHat docs, they recommend using the "/readyz" endpoint. 

 

IMO, it makes more sense to use the /readyz, as it means the API is ready to receive calls.

What do you think ?

Thanks

 

  • Ulises_Alonso's avatar
    Ulises_Alonso
    Icon for Employee rankEmployee
    Oct 01, 2025

    Looks like a mistake from my part. I will correct this in the article. Thanks!

    • Ulises_Alonso's avatar
      Ulises_Alonso
      Icon for Employee rankEmployee
      Oct 02, 2025

      Tested and article update submitted. It shouldn´t take long to see the change online.

      Thanks for reporting the errata anael​