targetPort and reviewing suggestions

Author: eedugon

deploy-manage/remote-clusters/_snippets/eck_rcs_expose.md

@@ -2,27 +2,10 @@ When the remote cluster server is enabled, ECK automatically creates a Kubernete
 
 To allow clusters running outside your Kubernetes environment to connect to this {{es}} cluster, you must expose this service externally. The way to expose this service depends on your ECK version.
 
-::::{applies-switch}
+:::::{applies-switch}
 
-:::{applies-item} eck: ga 3.0
-
-In ECK 3.2 and earlier you cannot customize the service that ECK generates for the remote cluster interface, but you can create your own `LoadBalancer` service, `Ingress` object, or use another method available in your environment.
-
-For example, for a cluster named `quickstart`, the following command creates a separate `LoadBalancer` service named `quickstart-es-remote-cluster-lb`, pointing to the ECK-managed service `quickstart-es-remote-cluster`:
-
-```sh
-kubectl expose service quickstart-es-remote-cluster \
-  --name=quickstart-es-remote-cluster-lb \
-  --type=LoadBalancer \ <1>
-  --port=9443 --target-port=9443
-```
-1. On cloud providers that support external load balancers, setting the type to `LoadBalancer` provisions a load balancer for your service. Alternatively, expose the service `<cluster-name>-es-remote-cluster` through one of the Kubernetes Ingress controllers that support TCP services.
-
-:::
-
-:::{applies-item} eck: ga 3.3
-
-You can expose the remote cluster service directly from the {{es}} resource manifest. By default, this service is exposed on port 9443.
+::::{applies-item} eck: ga 3.3
+You can customize how the remote cluster service is exposed by overriding its service specification directly under `spec.remoteClusterServer.service` in the {{es}} resource. By default, this service listens on port 9443.
 
 ```yaml
 apiVersion: elasticsearch.k8s.elastic.co/v1
@@ -43,6 +26,26 @@ spec:
       ...
 ```
 1. On cloud providers that support external load balancers, setting the type to `LoadBalancer` provisions a load balancer for your service. Alternatively, expose the service `<cluster-name>-es-remote-cluster` through one of the Kubernetes Ingress controllers that support TCP services.
-:::
 ::::
 
+::::{applies-item} eck: ga 3.0
+
+In ECK 3.2 and earlier, you can't customize the service that ECK generates for the remote cluster interface, but you can create your own `LoadBalancer` service, `Ingress` object, or use another method available in your environment.
+
+For example, for a cluster named `quickstart`, the following command creates a separate `LoadBalancer` service named `quickstart-es-remote-cluster-lb`, pointing to the ECK-managed service `quickstart-es-remote-cluster`:
+
+```sh
+kubectl expose service quickstart-es-remote-cluster \
+  --name=quickstart-es-remote-cluster-lb \
+  --type=LoadBalancer \ <1>
+  --port=9443 --target-port=9443
+```
+1. On cloud providers that support external load balancers, setting the type to `LoadBalancer` provisions a load balancer for your service. Alternatively, expose the service `<cluster-name>-es-remote-cluster` through one of the Kubernetes Ingress controllers that support TCP services.
+
+::::
+:::::
+
+:::{warning}
+If you change the service’s `port`, set `targetPort` explicitly to `9443`, which is the default remote cluster server listening port. Otherwise, Kubernetes uses the same value for both fields, resulting in failed connections.
+:::
+