You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: site/domains.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,7 +80,7 @@ running in Kubernetes.
80
80
administration port or a T3 channel to allow WLST access, you need to ensure that you allocate each channel a
81
81
unique port number across the entire Kubernetes cluster. If you expose the administration port in each WebLogic domain in
82
82
the Kubernetes cluster, then each one must have a different port. This is required because `NodePorts` are used to
83
-
expose channels outside the Kubernetes cluster. *IMPORTANT:* Exposing admin, RMI, or t3 capable channels via a node port
83
+
expose channels outside the Kubernetes cluster. **IMPORTANT:** Exposing admin, RMI, or t3 capable channels via a node port
84
84
can create an insecure configuration; in general only http protocols should be made available externally and this exposure
85
85
is usually accomplished by setting up an external load balancer that can access internal (non-nodeport) services.
86
86
*_Host Path Persistent Volumes:_ If using a `hostPath` persistent volume, then it must be available on all worker nodes in the cluster and have read/write/many permissions for all container/pods in the WebLogic Server deployment. Be aware
0 commit comments