Cluster Profiles support for IBM Cloud
@@ -167,6 +167,10 @@ An operator that:
generated by the router and the service CA operator.
#### Cluster Version Operator Changes
+
+> :warning: NOTE: Use of the exclude annotation is deprecated in favor of
+ [Cluster Profiles](https://github.com/openshift/enhancements/blob/master/enhancements/update/cluster-profiles.md)
+
In phase I the cluster version operator excludes operator manifests that
have an annotation in the form:
@@ -180,6 +184,10 @@ is present. For IBM public cloud, the value of \[identifier\] is
`internal-openshift-hosted`
#### Excluded Manifests
+
+> :warning: NOTE: Use of the exclude annotation is deprecated in favor of
+ [Cluster Profiles](https://github.com/openshift/enhancements/blob/master/enhancements/update/cluster-profiles.md)
+
Manifests for the components that should be skipped by the CVO whenever
the `EXCLUDE_MANIFESTS=internal-openshift-hosted` environment variable is
present, should include the annotation to exclude them. In most cases, only the
@@ -189,6 +197,16 @@ the CRDs that represent machines, machinesets and autoscalers should also be
skipped. Monitoring alerts for components that do not get installed in the user
cluster should also be skipped where possible.
+#### Cluster Profiles Support
+
+Manifests that should be rendered in an IBM Cloud managed cluster must include
+the following annotation:
+```
+include.release.openshift.io/ibm-cloud-managed=true
+```
+Manifests that should not be excluded such as control plane operators will not
+include that annotation.
+
#### Console Changes
The console should not report the control plane as being down if no metrics
datapoints exist for control plane components in this configuration.
