F5 BIG-IP deployment with OpenShift - platform and networking options

Introduction This article is an architectural overview on how F5 BIG-IP can be used with Red Hat OpenShift. Several topics are covered, including: 1-tier or 2-tier arrangements, where the BIG-I...
Screenshot 2023-09-29 at 09.06.41.png
Updated Feb 21, 2024
Version 2.0
application delivery
cloud
devops
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
rgfarid's avatar
rgfarid
Icon for Nimbostratus rankNimbostratus
Jul 22, 2024

Hi MichaelOLeary ,

Thanks for your reply.

My question is related to the default operator channel when trying to install the operator from the openshift redhat catalog.

When we list the catalog, under certified-operator-index, we get this output:

NAME                                         DISPLAY NAME                                                          DEFAULT CHANNEL

f5-bigip-ctlr-operator                       F5 Container Ingress Services                                         beta

 

We have a requirement for our production environment, the operator must be in stable channel.

 

We have check with redhat and they have reply to check with the ISV, that is to say F5 support.

 

Thanks for your help

  • rgfarid's avatar
    rgfarid
    Icon for Nimbostratus rankNimbostratus
    Jul 23, 2024

    Hi Trinath_Somanch

    Thanks for your reply.

    I have open a github RFE.

    Bellow the corresponding ticket:

    https://github.com/F5Networks/k8s-bigip-ctlr/issues/3495