Backport of OWLS-92894 from main branch to release/3.3 branch (#2598)

* Backport of OWLS-92894 from main branch to release/3.3

Co-authored-by: Rosemary Marano <[email protected]>

Author: lennyphan

documentation/domains/Domain.json

@@ -572,8 +572,16 @@
     "Istio": {
       "type": "object",
       "properties": {
+        "replicationChannelPort": {
+          "description": "The operator will create a `T3` protocol WebLogic network access point on each WebLogic Server that is part of a cluster with this port to handle EJB and servlet session state replication traffic between servers. This setting is ignored for clusters where the WebLogic cluster configuration already defines a `replication-channel` attribute. Defaults to 4564.",
+          "type": "number"
+        },
+        "localhostBindingsEnabled": {
+          "description": "This setting was added in operator version 3.3.3, defaults to the Helm chart configuration value `istioLocalhostBindingsEnabled` which in turn defaults to `true`. When `true`, the operator creates a WebLogic network access point with a `localhost` binding for each existing channel and protocol.  Use `true` for Istio versions prior to 1.10 and set to `false` for version 1.10 and later.",
+          "type": "boolean"
+        },
         "readinessPort": {
-          "description": "The operator will create a WebLogic network access point with this port that will then be exposed from the container running the WebLogic Server instance. The readiness probe will use this network access point to verify that the server instance is ready for application traffic. Defaults to 8888.",
+          "description": "The operator will create WebLogic network access points with this port on each WebLogic Server. The readiness probe on each pod will use these network access points to verify that the pod is ready for application traffic. Defaults to 8888.",
           "type": "number"
         },
         "enabled": {

documentation/domains/Domain.md

@@ -224,7 +224,9 @@ The current status of the operation of the WebLogic domain. Updated automaticall
 | Name | Type | Description |
 | --- | --- | --- |
 | `enabled` | Boolean | True, if this domain is deployed under an Istio service mesh. Defaults to true when the `istio` field is specified. |
-| `readinessPort` | number | The operator will create a WebLogic network access point with this port that will then be exposed from the container running the WebLogic Server instance. The readiness probe will use this network access point to verify that the server instance is ready for application traffic. Defaults to 8888. |
+| `localhostBindingsEnabled` | Boolean | This setting was added in operator version 3.3.3; it defaults to the Helm chart configuration value `istioLocalhostBindingsEnabled`, which in turn defaults to `true`. When `true`, the operator creates a WebLogic network access point with a `localhost` binding for each existing channel and protocol.  Use `true` for Istio versions prior to 1.10 and set to `false` for versions 1.10 and later. |
+| `readinessPort` | number | The operator will create WebLogic network access points with this port on each WebLogic Server. The readiness probe on each pod will use these network access points to verify that the pod is ready for application traffic. Defaults to 8888. |
+| `replicationChannelPort` | number | The operator will create a `T3` protocol WebLogic network access point on each WebLogic Server that is part of a cluster with this port to handle EJB and servlet session state replication traffic between servers. This setting is ignored for clusters where the WebLogic cluster configuration already defines a `replication-channel` attribute. Defaults to 4564. |
 
 ### Model
 
@@ -313,4 +315,4 @@ The current status of the operation of the WebLogic domain. Updated automaticall
 | `setServerGroupsTimeoutMillis` | number | WDT set server groups timeout for extending a JRF domain configured cluster in milliseconds. Default: 180000. |
 | `startApplicationTimeoutMillis` | number | WDT application start timeout in milliseconds. Default: 180000. |
 | `stopApplicationTimeoutMillis` | number | WDT application stop timeout in milliseconds. Default: 180000. |
-| `undeployTimeoutMillis` | number | WDT application or library undeployment timeout in milliseconds. Default: 180000. |
+| `undeployTimeoutMillis` | number | WDT application or library undeployment timeout in milliseconds. Default: 180000. |

documentation/domains/index.html

@@ -1493,8 +1493,16 @@
     "Istio": {
       "type": "object",
       "properties": {
+        "replicationChannelPort": {
+          "description": "The operator will create a `T3` protocol WebLogic network access point on each WebLogic Server that is part of a cluster with this port to handle EJB and servlet session state replication traffic between servers. This setting is ignored for clusters where the WebLogic cluster configuration already defines a `replication-channel` attribute. Defaults to 4564.",
+          "type": "number"
+        },
+        "localhostBindingsEnabled": {
+          "description": "This setting was added in operator version 3.3.3, defaults to the Helm chart configuration value `istioLocalhostBindingsEnabled` which in turn defaults to `true`. When `true`, the operator creates a WebLogic network access point with a `localhost` binding for each existing channel and protocol.  Use `true` for Istio versions prior to 1.10 and set to `false` for version 1.10 and later.",
+          "type": "boolean"
+        },
         "readinessPort": {
-          "description": "The operator will create a WebLogic network access point with this port that will then be exposed from the container running the WebLogic Server instance. The readiness probe will use this network access point to verify that the server instance is ready for application traffic. Defaults to 8888.",
+          "description": "The operator will create WebLogic network access points with this port on each WebLogic Server. The readiness probe on each pod will use these network access points to verify that the pod is ready for application traffic. Defaults to 8888.",
           "type": "number"
         },
         "enabled": {