Our operator is going to support AllNamespaces installation mode in the next release (1.15.0). But we have observed a UX issue: 

For channels that contain the 1.15.0 build (such as stable-v1 and stable-v1.15), even if the user selects an older version like 1.14.0 from the installation page, the Console will still use the info from CSV 1.15.0 to display that the operator can be installed in either "All namespaces on the cluster (default)" or "A specific namespace on the cluster."

This is what misleads users and may cause the installation to fail if they leave the option set to the default. It is only an issue when using the Web Console to install the operator.

    OCP 4.17 (not specific), cert-manager operator 1.15.0 staging build

    Always

    1. Create a catalogsource which contains the staging build of the cert-manager operator 1.15.0

$ oc create -f - <<EOF
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: rh-osbs
  namespace: openshift-marketplace
spec:
  displayName: rh-osbs
  image: brew.registry.redhat.io/rh-osbs/iib:801454 # 4.17 Index Image (use 801453 for 4.16, 801452 for 4.15, 801451 for 4.14)
  sourceType: grpc
  publisher: CVP
  updateStrategy:
    registryPoll:
      interval: 5m
EOF

    2. Navigate to the OperatorHub, select the operator from the created catalogsource "rh-osbs"
    3. Select channel "stable-v1" and version "1.14.0"
    4. Leave installation options as default and click the Install botton
    5. Wait to see "Installation Failed" error occur

    When user selects CSV 1.14.0 from "stable-v1" channel, the OperatorHub displays that the operator can be installed in either "All namespaces on the cluster (default)" or "A specific namespace on the cluster."

    When user selects CSV 1.14.0 from "stable-v1" channel, the OperatorHub should only display that the operator can be installed in "A specific namespace on the cluster."

    It seems the Console uses the information about the installMode and other associated info from the CSV at the head of the channel ('currentCSV' of the operator's PackageManifest object) being used for installation rather than the actual CSV which the user is trying to install. That causes this exact issue to thrive.