Merge pull request #64802 from michaelryanpeter/ocpbugs-13336-olm-po-remove-cert-manager

OCPBUGS#13336: Platform Operator change cert-manager to service-mesh

Author: michaelryanpeter

modules/olm-installing-po-after.adoc

@@ -12,25 +12,25 @@ As a cluster administrator, you can install platform Operators after cluster cre
 
 . Choose a platform Operator from the supported set of OLM-based Operators. For the list of this set and details on current limitations, see "Technology Preview restrictions for platform Operators".
 
-. Create a `PlatformOperator` object YAML file for your chosen platform Operator, for example a `cert-manager.yaml` file for the {cert-manager-operator}:
+. Create a `PlatformOperator` object YAML file for your chosen platform Operator, for example a `service-mesh-po.yaml` file for the {SMProductName} Operator:
 +
-.Example `cert-manager.yaml` file
+.Example `sevice-mesh-po.yaml` file
 [source,yaml]
 ----
 apiVersion: platform.openshift.io/v1alpha1
 kind: PlatformOperator
 metadata:
-  name: cert-manager
+  name: service-mesh-po
 spec:
   package:
-    name: openshift-cert-manager-operator
+    name: servicemeshoperator
 ----
 
 . Create the `PlatformOperator` object by running the following command:
 +
 [source,terminal]
 ----
-$ oc apply -f cert-manager.yaml
+$ oc apply -f service-mesh-po.yaml
 ----
 +
 [NOTE]
@@ -39,18 +39,18 @@ If your cluster does not have the `TechPreviewNoUpgrades` feature set enabled, t
 
 [source,terminal]
 ----
-error: resource mapping not found for name: "cert-manager" namespace: "" from "cert-manager.yaml": no matches for kind "PlatformOperator" in version "platform.openshift.io/v1alpha1"
+error: resource mapping not found for name: "service-mesh-po" namespace: "" from "service-mesh-po.yaml": no matches for kind "PlatformOperator" in version "platform.openshift.io/v1alpha1"
 ensure CRDs are installed first
 ----
 ====
 
 .Verification
 
-. Check the status of the `cert-manager` platform Operator by running the following command:
+. Check the status of the `service-mesh-po` platform Operator by running the following command:
 +
 [source,terminal]
 ----
-$ oc get platformoperator cert-manager -o yaml
+$ oc get platformoperator service-mesh-po -o yaml
 ----
 +
 .Example output
@@ -59,10 +59,10 @@ $ oc get platformoperator cert-manager -o yaml
 ...
 status:
   activeBundleDeployment:
-    name: cert-manager
+    name: service-mesh-po
   conditions:
   - lastTransitionTime: "2022-10-24T17:24:40Z"
-    message: Successfully applied the cert-manager BundleDeployment resource
+    message: Successfully applied the service-mesh-po BundleDeployment resource
     reason: InstallSuccessful
     status: "True" <1>
     type: Installed
@@ -95,4 +95,4 @@ status:
     reason: AsExpected
     status: "True"
     type: Available
-----
+----

modules/olm-installing-po-during.adoc

@@ -40,18 +40,18 @@ spec:
 ----
 <1> Enable the `TechPreviewNoUpgrade` feature set.
 
-. Create a `PlatformOperator` object YAML file for your chosen platform Operator in the `<installation_directory>/manifests/` directory, for example a `cert-manager.yaml` file for the {cert-manager-operator}:
+. Create a `PlatformOperator` object YAML file for your chosen platform Operator in the `<installation_directory>/manifests/` directory, for example a `service-mesh-po.yaml` file for the {SMProductName} Operator:
 +
-.Example `cert-manager.yaml` file
+.Example `service-mesh-po.yaml` file
 [source,yaml]
 ----
 apiVersion: platform.openshift.io/v1alpha1
 kind: PlatformOperator
 metadata:
-  name: cert-manager
+  name: service-mesh-po
 spec:
   package:
-    name: openshift-cert-manager-operator
+    name: servicemeshoperator
 ----
 
 . When you are ready to complete the cluster install, refer to your chosen installation method and continue through running the `openshift-install create cluster` command.
@@ -65,11 +65,11 @@ Failure of the platform Operator to successfully install will block the cluster
 
 .Verification
 
-. Check the status of the `cert-manager` platform Operator by running the following command:
+. Check the status of the `service-mesh-po` platform Operator by running the following command:
 +
 [source,terminal]
 ----
-$ oc get platformoperator cert-manager -o yaml
+$ oc get platformoperator service-mesh-po -o yaml
 ----
 +
 .Example output
@@ -78,10 +78,10 @@ $ oc get platformoperator cert-manager -o yaml
 ...
 status:
   activeBundleDeployment:
-    name: cert-manager
+    name: service-mesh-po
   conditions:
   - lastTransitionTime: "2022-10-24T17:24:40Z"
-    message: Successfully applied the cert-manager BundleDeployment resource
+    message: Successfully applied the service-mesh-po BundleDeployment resource
     reason: InstallSuccessful
     status: "True" <1>
     type: Installed
@@ -114,4 +114,4 @@ status:
     reason: AsExpected
     status: "True"
     type: Available
-----
+----

modules/olm-po-techpreview.adoc

@@ -43,20 +43,20 @@ After considering these restrictions, the following Operators can be successfull
 |odf-csi-addons-operator
 |odr-hub-operator
 
-|openshift-cert-manager-operator
 |openshift-custom-metrics-autoscaler-operator
-
 |openshift-gitops-operator
-|openshift-pipelines-operator-rh
 
+|openshift-pipelines-operator-rh
 |quay-operator
-|red-hat-camel-k
 
+|red-hat-camel-k
 |rhpam-kogito-operator
-|service-registry-operator
 
+|service-registry-operator
 |servicemeshoperator
+
 |skupper-operator
+|
 |===
 
 [NOTE]
@@ -65,4 +65,4 @@ The following features are not available during this Technology Preview release:
 
 * Automatically upgrading platform Operator packages after cluster rollout
 * Extending the platform Operator mechanism to support any optional, CVO-based components
-====
+====