Updates cluster capabilities docs with optional IR disablement

Author: Steven Smith

installing/cluster-capabilities.adoc

@@ -80,6 +80,12 @@ include::modules/cluster-samples-operator.adoc[leveloffset=+2]
 .Additional resources
 * xref:../openshift_images/configuring-samples-operator.adoc#configuring-samples-operator[Configuring the Cluster Samples Operator]
 
+include::modules/cluster-image-registry-operator.adoc[leveloffset=+2]
+
+[role="_additional-resources"]
+.Additional resources
+* xref:../registry/configuring-registry-operator.adoc#configuring-registry-operator[Image Registry Operator in {product-title}]
+
 [role="_additional-resources"]
 [id="additional-resources_{context}"]
 == Additional resources

modules/cluster-image-registry-operator.adoc

@@ -1,13 +1,28 @@
 // Module included in the following assemblies:
 //
 // * operators/operator-reference.adoc
+// * installing/cluster-capabilities.adoc
+
+// operators/operator-reference.adoc
+ifeval::["{context}" == "cluster-operators-ref"]
+:operator-ref:
+endif::[]
+
+// installing/cluster-capabilities.adoc
+ifeval::["{context}" == "cluster-capabilities"]
+:cluster-caps:
+endif::[]
 
 [id="cluster-image-registry-operator_{context}"]
 = Cluster Image Registry Operator
 
 [discrete]
 == Purpose
 
+ifdef::cluster-caps[]
+The Cluster Image Registry Operator provides features for the `ImageRegistry` capability.
+endif::[]
+
 The Cluster Image Registry Operator manages a singleton instance of the {product-registry}. It manages all configuration of the registry, including creating storage.
 
 On initial start up, the Operator creates a default `image-registry` resource instance based on the configuration detected in the cluster. This indicates what cloud storage type to use based on the cloud provider.
@@ -16,6 +31,10 @@ If insufficient information is available to define a complete `image-registry` r
 
 The Cluster Image Registry Operator runs in the `openshift-image-registry` namespace and it also manages the registry instance in that location. All configuration and workload resources for the registry reside in that namespace.
 
+ifdef::cluster-caps[]
+If you disable the `ImageRegistry` capability, you can reduce the overall resource footprint of {product-title} in Telco environments. Depending on your deployment, you can disable this component if you do not need it.
+endif::[]
+
 [discrete]
 == Project
 

snippets/capabilities-table.adoc

@@ -19,6 +19,9 @@ The following table describes the `baselineCapabilitySet` values.
 |`v4.13`
 |Specify this option when you want to enable the default capabilities for {product-title} 4.13. By specifying `v4.13`, capabilities that are introduced in newer versions of {product-title} are not enabled. The default capabilities in {product-title} 4.13 are `baremetal`, `marketplace`, `openshift-samples`, `Console`, `Insights`, `Storage`, `CSISnapshot` and `NodeTuning`.
 
+|`v4.14`
+|Specify this option when you want to enable the default capabilities for {product-title} 4.14. By specifying `v4.14`, capabilities that are introduced in newer versions of {product-title} are not enabled. The default capabilities in {product-title} 4.14 are `baremetal`, `marketplace`, `openshift-samples`, `Console`, `Insights`, `Storage`, `CSISnapshot`, `NodeTuning`, and `ImageRegistry`.
+
 // TODO: Add `Build` and `DeploymentConfig` to the list for 4.14.
 
 |`None`