Description of problem: Container Security operator cannot install for all namespaces Version-Release number of selected component (if applicable): 4.3.0-0.nightly-2019-11-29-051144 How reproducible: Always Steps to Reproduce: 1. create cso catalogsource $ cat cso.catalogsource.yaml apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: name: container-security-operator spec: sourceType: grpc image: quay.io/quay/cso-catalog@sha256:e664ffe5d207a537f2b0245e6c10c1d198a8de69c9ffa5aed531c2edb24c355d $ oc create -f cso.catalogsource.yaml 2. Try to install cso for all namspaces: operatorHub page -> install container Security Operator on webconsole for all namespaces. 3. Actual results: 2. The console will give an error: Operator not available for selected namespaces $ oc get csv container-security-operator.v1.0.0 -n default -o 'jsonpath={.spec.installModes} - supported: true type: OwnNamespace - supported: true type: SingleNamespace - supported: true type: MultiNamespace - supported: true type: AllNamespaces Expected results: The CSO can install for all namespaces Additional info:
*** Bug 1779081 has been marked as a duplicate of this bug. ***
It looks like the CatalogSource needs to be in the openshift-marketplace namespace. Alec, can you confirm that this is expected? apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: name: container-security-operator namespace: openshift-marketplace spec: sourceType: grpc image: quay.io/quay/cso-catalog@sha256:e664ffe5d207a537f2b0245e6c10c1d198a8de69c9ffa5aed531c2edb24c355d
Yes, it needs to be in the `openshift-marketplace` namespace, as it says in the docs (https://github.com/quay/container-security-operator#deploying-using-olm).