Skip to content

Commit b34e123

Browse files
authored
Revert "OSSM-4843: Update conditional tagging"
1 parent 75cab08 commit b34e123

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

modules/ossm-about-smcp.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,6 @@ Red Hat OpenShift Service on AWS (ROSA) places additional restrictions on where
2222
The {SMProductShortName} documentation uses `istio-system` as the example project, but you can deploy the service mesh to any project.
2323
====
2424

25-
ifdef::openshift-rosa[]
25+
ifndef::openshift-enterprise[]
2626
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.
27-
endif::openshift-rosa[]
27+
endif::openshift-enterprise[]

modules/ossm-federation-across-cluster.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,8 @@ The service must be exposed through a load balancer that operates at Layer4 of t
1414
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.
1515

1616
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.
17-
1817
ifndef::openshift-rosa[]
18+
1919
== Exposing the federation ingress on clusters running on {ibmpowerProductName} and {ibmzProductName}
2020
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.
2121

0 commit comments

Comments
 (0)