Description of problem: No clean way to specify operand issues to KEDA OLM operator
$ oc get pod -n openshift-keda NAME READY STATUS RESTARTS AGE custom-metrics-autoscaler-operator-6464c9bf86-22d8m 1/1 Running 0 38m keda-metrics-apiserver-85cc6b5968-5459d 1/1 Running 0 103s keda-operator-5856b799b4-mfw4x 1/1 Running 0 103s Custom Metrics Autoscaler 2.7.1 provided by Red Hat $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.11.0-0.nightly-2022-06-23-153912 True False 74m Cluster version is 4.11.0-0.nightly-2022-06-23-153912 Custom Metrics Autoscaler (Keda) installed successfully
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069