F5Networks / k8s-bigip-ctlr

Repository for F5 Container Ingress Services for Kubernetes & OpenShift.
Apache License 2.0
355 stars 193 forks source link

Add stable channel for the f5-bigip-ctlr-operator in **Redhat Openshift Catalog** #3495

Open rgfarid opened 1 month ago

rgfarid commented 1 month ago

Title

Add stable channel for the f5-bigip-ctlr-operator in Redhat Openshift Catalog

Description

When we list the Redhat Openshift 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.

Actual Problem

The f5-bigip-ctlr-operator is only available in beta channel.

To check the default operator channel you can execute this command on an openshift cluster

$ oc get subs -n <operator_namespace>

output:

NAME               PACKAGE            SOURCE                  CHANNEL

xxx                    xxxxxxxxx            xxxxxxx                    operator_default_channel

Bellow the link to the discussion in F5 Devcentral:

https://community.f5.com/kb/TechnicalArticles/f5-big-ip-deployment-with-openshift---platform-and-networking-options/318249/comments/331905?emcs_t=S2h8ZW1haWx8bWVudGlvbl9zdWJzY3JpcHRpb258TFlYUUE5T1lZSU5PTFh8LTF8QVRfTUVOVElPTlN8aEs

Solution Proposed

Deliver the operator in stable channel in the redhat catalogue, check with redhat if needed.

trinaths commented 1 month ago

Created [CONTCNTR-4808] for internal tracking.