When a cluster is deployed with no capabilities enabled, and the Build capability is later enabled, it's related cluster configuration CRD is not installed. This prevents admins from fine-tuning builds and ocm-o from fully reconciling its state.

    

4.16.0
    

Always
    

    1. Launch a cluster with no capabilities enabled (via cluster-bot: launch 4.16.0.0-ci aws,no-capabilities 
    2. Edit the clusterversion to enable the build capability: oc patch clusterversion/version --type merge -p '{"spec":{"capabilities":{"additionalEnabledCapabilities":["Build"]}}}'
    3. Wait for the openshift-apiserver and openshift-controller-manager to roll out
    

APIs for BuildConfig (build.openshift.io) are enabled.
Cluster configuration API for build system is not:

$ oc api-resources | grep "build"
buildconfigs  bc  build.openshift.io/v1 true         BuildConfig
builds                   build.openshift.io/v1 true         Build
    

Cluster configuration API is enabled.

$ oc api-resources | grep "build"
buildconfigs  bc  build.openshift.io/v1    true  BuildConfig
builds                   build.openshift.io/v1    true  Build
builds                   config.openshift.io/v1  true  Build     
    

This causes list errors in openshift-controller-manager-operator, breaking the controller that reconciles state for builds and the image registry.

W0523 18:23:38.551022       1 reflector.go:539] k8s.io/client-go@v0.29.0/tools/cache/reflector.go:229: failed to list *v1.Build: the server could not find the requested resource (get builds.config.openshift.io)
E0523 18:23:38.551334       1 reflector.go:147] k8s.io/client-go@v0.29.0/tools/cache/reflector.go:229: Failed to watch *v1.Build: failed to list *v1.Build: the server could not find the requested resource (get builds.config.openshift.io)