OSDOCS-5592: Fixed removed references in OSD

Author: EricPonvelle

logging/cluster-logging-external.adoc

@@ -178,9 +178,9 @@ include::modules/cluster-logging-troubleshooting-loki-entry-out-of-order-errors.
 
 * link:https://grafana.com/docs/loki/latest/configuration/[Configuring Loki server]
 
-ifndef::openshift-dedicated,openshift-rosa[]
+ifndef::openshift-rosa[]
 include::modules/cluster-logging-collector-log-forward-gcp.adoc[leveloffset=+1]
-endif::openshift-dedicated,openshift-rosa[]
+endif::openshift-rosa[]
 
 include::modules/logging-forward-splunk.adoc[leveloffset=+1]
 

modules/osd-applications-config-custom-domains.adoc

@@ -84,7 +84,13 @@ NAME               ENDPOINT                                                    D
 <company_name>     xxrywp.<company_name>.cluster-01.opln.s1.openshiftapps.com  *.apps.<company_name>.io     Ready
 ----
 
+ifdef::openshift-rosa[]
 . Using the endpoint value, add a new wildcard CNAME recordset to your managed DNS provider, such as Route53.
+endif::openshift-rosa[]
+ifndef::openshift-rosa[]
+. Using the endpoint value, add a new wildcard CNAME recordset to your managed DNS provider, such as Route53, Azure DNS, or Google DNS.
+endif::openshift-rosa[]
+
 +
 .Example
 +

modules/ossm-federation-across-cluster.adoc

@@ -27,7 +27,7 @@ service.beta.kubernetes.io/aws-load-balancer-type: nlb
 
 The Fully Qualified Domain Name found in the `.status.loadBalancer.ingress.hostname` 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.
 
-ifndef::openshift-rosa,openshift-dedicated[]
+ifndef::openshift-rosa[]
 == Exposing the federation ingress on Azure
 On Microsoft Azure, merely setting the service type to `LoadBalancer` suffices for mesh federation to operate correctly.
 
@@ -37,4 +37,4 @@ The IP address found in the `.status.loadBalancer.ingress.ip` field of the ingre
 On Google Cloud Platform, merely setting the service type to `LoadBalancer` suffices for mesh federation to operate correctly.
 
 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.
-endif::openshift-rosa,openshift-dedicated[]
+endif::openshift-rosa[]

modules/ossm-rn-new-features.adoc

@@ -606,12 +606,12 @@ New Custom Resource Definitions (CRDs) have been added to support federating ser
 
 * `ImportedServiceSet` - Defines which services for a given `ServiceMeshPeer` are imported from the peer mesh. These services must also be made available by the peer’s `ExportedServiceMeshSet` resource.
 
-ifndef::openshift-dedicated,openshift-rosa[]
+ifndef::openshift-rosa[]
 Service Mesh Federation is not supported between clusters on Red Hat OpenShift Service on AWS (ROSA), Azure Red Hat OpenShift (ARO), or OpenShift Dedicated (OSD).
-endif::openshift-dedicated,openshift-rosa[]
-ifdef::openshift-dedicated,openshift-rosa[]
+endif::openshift-rosa[]
+ifdef::openshift-rosa[]
 Service Mesh Federation is not supported between clusters on Red Hat OpenShift Service on AWS (ROSA) or OpenShift Dedicated (OSD).
-endif::openshift-dedicated,openshift-rosa[]
+endif::openshift-rosa[]
 
 === OVN-Kubernetes Container Network Interface (CNI) generally available
 
@@ -829,16 +829,16 @@ spec:
 
 This release of {SMProductName} addresses Common Vulnerabilities and Exposures (CVEs) and bug fixes.
 
-ifndef::openshift-dedicated,openshift-rosa[]
+ifndef::openshift-rosa[]
 == {SMProductName} on {product-dedicated} and Microsoft Azure Red Hat OpenShift
 
 {SMProductName} is now supported through {product-dedicated} and Microsoft Azure Red Hat OpenShift.
-endif::openshift-dedicated,openshift-rosa[]
-ifdef::openshift-dedicated,openshift-rosa[]
+endif::openshift-rosa[]
+ifdef::openshift-rosa[]
 == {SMProductName} on {product-dedicated}
 
 {SMProductName} is now supported through {product-dedicated}.
-endif::openshift-dedicated,openshift-rosa[]
+endif::openshift-rosa[]
 
 
 == New features {SMProductName} 2.0.6

modules/ossm-supported-configurations.adoc

@@ -17,9 +17,9 @@ The {SMProductName} Operator supports multiple versions of the `ServiceMeshContr
 
 * Red Hat {product-title} version 4.9 or later.
 * {product-dedicated} version 4.
-ifndef::openshift-dedicated,openshift-rosa[]
+ifndef::openshift-rosa[]
 * Azure Red Hat OpenShift (ARO) version 4.
-endif::openshift-dedicated,openshift-rosa[]
+endif::openshift-rosa[]
 * Red Hat OpenShift Service on AWS (ROSA).
 
 [id="ossm-unsupported-configurations_{context}"]

networking/routes/secured-routes.adoc

@@ -9,7 +9,7 @@ toc::[]
 
 Secure routes provide the ability to use several types of TLS termination to serve certificates to the client. The following sections describe how to create re-encrypt, edge, and passthrough routes with custom certificates.
 
-ifndef::openshift-dedicated,openshift-rosa[]
+ifndef::openshift-rosa[]
 [IMPORTANT]
 ====
 If you create routes in Microsoft Azure through public endpoints, the resource
@@ -18,7 +18,7 @@ terms. For a list of terms that Azure restricts, see
 link:https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-manager-reserved-resource-name[Resolve reserved resource name errors]
 in the Azure documentation.
 ====
-endif::openshift-dedicated,openshift-rosa[]
+endif::openshift-rosa[]
 
 include::modules/nw-ingress-creating-a-reencrypt-route-with-a-custom-certificate.adoc[leveloffset=+1]