Was this article helpful?
Hi rgfarid
CIS operator should be available for production use cases also. I've deployed CIS (both using YAML manifests and using the Openshift Operator) many times. Can you shoot me a message (you can use this DevCentral platform) if you need help with this?
Mike.
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
- MichaelOLearyJul 23, 2024
Employee
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.
- rgfaridJul 23, 2024
Nimbostratus
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
- Trinath_SomanchJul 23, 2024
Employee
rgfarid Please create a github RFE https://github.com/F5Networks/k8s-bigip-ctlr/issues.
- rgfaridJul 23, 2024
Nimbostratus
Thanks for your reply.
I have open a github RFE.
Bellow the corresponding ticket:
https://github.com/F5Networks/k8s-bigip-ctlr/issues/3495