[CN-1206]: Add Notes to HA Documentation about Multi Member Routing (#…

…206)

docs/modules/ROOT/examples/hazelcast-high-availability-mode-multi-member-routing.yaml

@@ -0,0 +1,10 @@
+apiVersion: hazelcast.com/v1alpha1
+kind: Hazelcast
+metadata:
+  name: hazelcast
+spec:
+  highAvailabilityMode: ZONE
+  exposeExternally:
+    type: Smart
+    discoveryServiceType: LoadBalancer
+    memberAccess: LoadBalancer

docs/modules/ROOT/pages/high-availability-mode.adoc

@@ -10,7 +10,7 @@ When using either type of partition grouping (ZONE_AWARE or NODE_AWARE) with a H
 The `highAvailabilityMode` parameter allows you to specify partition groups and to automatically distribute members across availability zones and nodes, using the Kubernetes policy `topologySpreadConstraints`.
 
 
-== Configuring High Availability Mode 
+== Configuring High Availability Mode
 
 Below are the configuration options for the High Availability Mode feature.
 
@@ -57,4 +57,57 @@ Below are the configuration options for the High Availability Mode feature.
 [source,yaml,subs="attributes+"]
 ----
 include::ROOT:example$/hazelcast-high-availability-mode.yaml[]
-----
+----
+
+== High Availability Mode and MULTI_MEMBER Routing
+
+`MULTI_MEMBER` routing is a client feature that allows a client to connect to a subset of members that is determined by a grouping strategy. To benefit from `MULTI_MEMBER` routing, you must enable high availability mode, because this parameter is used to determine partition groups. Also, if the `MULTI_MEMBER` routing mode is used on the client-side, `exposeExternally.type` must be set to `smart` in the Hazelcast CR.
+
+Example server and client configurations to use `MULTI_MEMBER` routing:
+
+[source,yaml,subs="attributes+"]
+----
+include::ROOT:example$/hazelcast-high-availability-mode-multi-member-routing.yaml[]
+----
+
+[tabs]
+====
+Java::
++
+--
+[source, java]
+----
+ClientConfig clientConfig = new ClientConfig();
+ClientNetworkConfig networkConfig = clientConfig.getNetworkConfig();
+networkConfig.getClusterRoutingConfig().setRoutingMode(RoutingMode.MULTI_MEMBER);
+// PARTITION_GROUPS is the default strategy, so it does not need to be explicitly defined
+networkConfig.getClusterRoutingConfig().setRoutingStrategy(RoutingStrategy.PARTITION_GROUPS);
+----
+--
+
+XML::
++
+--
+[source, xml]
+----
+...
+    <network>
+        <cluster-routing mode="MULTI_MEMBER">
+          <grouping-strategy>PARTITION_GROUPS</grouping-strategy>
+        </cluster-routing>
+    </network>
+...
+----
+--
+
+YAML::
++
+--
+[source, yaml]
+----
+  network:
+    cluster-routing:
+      mode: MULTI_MEMBER
+      grouping-strategy: PARTITION_GROUPS
+----
+--