Describe the bug

In version 4.19, the OperatorHub was located in the Operators section. Since version 4.20, the OperatorHub has been included in the Software Catalog with the Operators type.

When installing a cluster, we don't use all the default Capabilities. We include the following:

• Console
• Ingress
• CSISnapshot
• marketplace
• ImageRegistry
• DeploymentConfig
• OperatorLifecycleManager
• OperatorLifecycleManagerV1

When updating to version 4.20.0-okd-scos.0, the Operators type does not appear in the Software Catalog, and all pods are running.

Going through all the Capabilities, we found out that the Operators type appears if you add CloudControllerManager and CloudCredential to the Capabilities.

To test updates, we use a single-node installation with install-config.yaml:

apiVersion: v1
baseDomain: example.com
compute:
- architecture: amd64
  hyperthreading: Enabled
  name: worker
  replicas: 0
controlPlane:
  architecture: amd64
  hyperthreading: Enabled
  name: master
  replicas: 1
metadata:
  name: okd
networking:
  clusterNetwork:
  - cidr: 10.128.0.0/14
    hostPrefix: 23
  machineNetwork:
  - cidr: 10.0.0.0/16
  networkType: OVNKubernetes
  serviceNetwork:
  - 172.30.0.0/16
platform:
  none: {}
capabilities:
  baselineCapabilitySet: None
  additionalEnabledCapabilities:
  - Console
  - Ingress
  - CSISnapshot
  - marketplace
  - ImageRegistry
  - DeploymentConfig
  - OperatorLifecycleManager
  - OperatorLifecycleManagerV1
bootstrapInPlace:
  installationDisk: /dev/sda
sshKey: ...
pullSecret: ...

Is this a bug or a feature?
Is it possible to enable the specified Capabilities in an existing cluster?

Version

4.20.0-okd-scos.0

Reproducibility

100%

Log Bundle

https://disk.yandex.ru/d/GFWSP29pHdS0XQ