Merge pull request #64890 from rh-tokeefe/OSSM-4843

/lgtm, merging OSSM-4843: Update conditional tagging

Author: JoeAldinger

modules/ossm-about-smcp.adoc

@@ -22,6 +22,6 @@ Red Hat OpenShift Service on AWS (ROSA) places additional restrictions on where
 The {SMProductShortName} documentation uses `istio-system` as the example project, but you can deploy the service mesh to any project.
 ====
 
-ifndef::openshift-enterprise[]
+ifdef::openshift-rosa[]
 If you are deploying the control plane for use on {product-rosa}, see the Red Hat Knowledgebase article link:https://access.redhat.com/solutions/6529231[OpenShift service mesh operator Istio basic not starting due to authentication errors], which discusses adding a new project and starting pods.
-endif::openshift-enterprise[]
+endif::openshift-rosa[]

modules/ossm-federation-across-cluster.adoc

@@ -14,8 +14,8 @@ The service must be exposed through a load balancer that operates at Layer4 of t
 If the cluster runs on bare metal and fully supports `LoadBalancer` services, the IP address found in the `.status.loadBalancer.ingress.ip` field of the ingress gateway `Service` object should be specified as one of the entries in the `.spec.remote.addresses` field of the `ServiceMeshPeer` object.
 
 If the cluster does not support `LoadBalancer` services, using a `NodePort` service could be an option if the nodes are accessible from the cluster running the other mesh. In the `ServiceMeshPeer` object, specify the IP addresses of the nodes in the `.spec.remote.addresses` field and the service's node ports in the `.spec.remote.discoveryPort` and `.spec.remote.servicePort` fields.
-ifndef::openshift-rosa[]
 
+ifndef::openshift-rosa[]
 == Exposing the federation ingress on clusters running on {ibmpowerProductName} and {ibmzProductName}
 If the cluster runs on {ibmpowerProductName} or {ibmzProductName} infrastructure and fully supports `LoadBalancer` services, the IP address found in the `.status.loadBalancer.ingress.ip` field of the ingress gateway `Service` object should be specified as one of the entries in the `.spec.remote.addresses` field of the `ServiceMeshPeer` object.