Merge pull request #68513 from amolnar-rh/TELCODOCS-1641

TELCODOCS-1641: Removed installedCSV section from Subscription configuration with TALO

Author: abhatt-rh

modules/cnf-topology-aware-lifecycle-manager-about-subscription-crs.adoc

@@ -6,16 +6,11 @@
 [id="talo-about-subscription-crs_{context}"]
 = Configuring Operator subscriptions for managed clusters that you install with {cgu-operator}
 
-{cgu-operator} can only approve the install plan for an Operator if the `Subscription` CR of the Operator contains a valid `status` field. You can use the following fields:
-
-* `status.state.AtLatestKnown` for the latest Operator version
-* `status.installedCSV` for a specific Operator version
+{cgu-operator-first} can only approve the install plan for an Operator if the `Subscription` custom resource (CR) of the Operator contains the `status.state.AtLatestKnown` field.
 
 .Procedure
 
-. Add one of the following status fields to the `Subscription` CR of the Operator:
-
-.. Add the `status.state.AtLatestKnown` field for the latest Operator version:
+. Add the `status.state.AtLatestKnown` field to the `Subscription` CR of the Operator:
 +
 .Example Subscription CR
 [source,yaml]
@@ -44,28 +39,5 @@ status:
 When a new version of the Operator is available in the registry, the associated policy becomes non-compliant.
 ====
 
-.. Add the `status.installedCSV` field for a specific Operator version:
-+
-.Example Subscription CR
-[source,yaml]
-----
-apiVersion: operators.coreos.com/v1alpha1
-kind: Subscription
-metadata:
-  name: cluster-logging
-  namespace: openshift-logging
-  annotations:
-    ran.openshift.io/ztp-deploy-wave: "2"
-spec:
-  channel: "stable"
-  name: cluster-logging
-  source: redhat-operators
-  sourceNamespace: openshift-marketplace
-  installPlanApproval: Manual
-status:
-  installedCSV: cluster-logging.v5.7.5 <1>
-----
-<1> The `status.installedCSV` field with the CSV value is used for a specific version of an Operator, for example, `status.installedCSV: cluster-logging.v5.7.5`.
-
 +
 . Apply the changed `Subscription` policy to your managed clusters with a `ClusterGroupUpgrade` CR.