Skip to content

Commit 9c4a731

Browse files
incorporate Tom B edits
1 parent d573c35 commit 9c4a731

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

site/user-guide.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -76,6 +76,9 @@ The operator can configure services to expose WebLogic applications and features
7676
* Is certificate-based integrity needed?
7777
* How will users authenticate?
7878
* Is the network channel encrypted?
79+
* Is exposing RMI required (T3 enables RMI), or IIOP, or would HTTP alone suffice?
80+
* Is it necessary to expose admin-capable channels?
81+
* Is it required to expose default channels (these accept T3/RMI, and by default, accept administrative traffic)?
7982

8083
While it is natural to expose web applications outside the cluster, exposing administrative features like the Administration Console and a T3 channel for WLST should be given more careful consideration. There are alternative options that should be weighed. For example, Kubernetes provides the ability to securely access a shell running in a container in a pod in the cluster. WLST could be executed from such an environment, meaning the T3 communications are entirely within the Kubernetes cluster and therefore more secure.
8184

0 commit comments

Comments
 (0)