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
MichaelOLeary's avatar
MichaelOLeary
Icon for Employee rankEmployee
Jul 22, 2024

rgfarid , thanks, I understand you now.

It looks like beta channel is the only option. See the video around the 1m 55 second mark: https://www.youtube.com/watch?v=d8OvxoDjvuo

If you need a different default channel I think you should raise a github issue here: https://github.com/F5Networks/k8s-bigip-ctlr/issues

Also can you share the command you run to show the default operator channel? (I have never done that from command line)

Trinath_Somanch you may be interested in this request.

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

Dear team,

Thanks for your support.

I will raise a github issue related to this RFE.

MichaelOLearyto get the default channel you can use this command:

prerequisite:

the operator must be installed on the openshift cluster first!

command:

$ oc get subs -n <operator_namespace>

output:

NAME               PACKAGE            SOURCE                  CHANNEL

xxx                    xxxxxxxxx            xxxxxxx                    operator_default_channel

 

Regards,

Rabah