Skip to content

Commit a3e40e9

Browse files
committed
Initial cut of documentation for kubernetesPlatform property and Openshift.
1 parent d3f49eb commit a3e40e9

File tree

3 files changed

+26
-0
lines changed

3 files changed

+26
-0
lines changed

documentation/staging/content/security/openshift.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -116,3 +116,11 @@ see [OpenShift]({{<relref "/userguide/platforms/environments#openshift">}}).
116116
#### Using a dedicated namespace
117117

118118
When the user that installs an individual instance of the operator does not have the required privileges to create resources at the Kubernetes cluster level, a dedicated namespace can be used for the operator instance and all the WebLogic domains that it manages. For more details about the `dedicated` setting, please refer to [Operator Helm configuration values]({{< relref "/userguide/managing-operators/using-helm#operator-helm-configuration-values" >}}).
119+
120+
#### Set the Helm chart property `kubernetesPlatorm` to `Openshift`
121+
Beginning with operator version 4.0, you should specify the `kubernetesPlatorm` Helm chart property and set its value to `Openshift` when installing the operator in Openshift. With this setting, the operator:
122+
- Configures the correct file permissions for WebLogic Server to work in Openshift.
123+
- Sets `weblogic.SecureMode.WarnOnInsecureFileSystem` Java system property to `false` on each target WebLogic Server instance. This flag suppresses the insecure file system warnings in the WebLogic Server console in production mode. These warnings result from setting the correct file permissions to work with restricted security context constraints on Openshift.
124+
125+
For more information about the Helm chart, see the
126+
[Operator Helm configuration values]({{<relref "/userguide/managing-operators/using-helm#operator-helm-configuration-values">}}).

documentation/staging/content/userguide/managing-operators/using-helm.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -96,6 +96,18 @@ Example:
9696
javaLoggingLevel: "FINE"
9797
```
9898

99+
##### `kubernetesPlatform`
100+
Allows you to set the Kubernetes platform on which the operator is running. The value is case-insensitive.
101+
102+
This flag is helpful when using the operator in OpenShift because of the security requirements to run the WebLogic Server in OpenShift. See [Security requirements to run WebLogic in OpenShift]({{<relref "/security/openshift#security-requirements-to-run-weblogic-in-openshift">}}) for more details. When you set the `kubernetesPlatform` value to `Openshift`, the operator:
103+
- Configures the correct file permissions for WebLogic Server to work in Openshift.
104+
- Sets `weblogic.SecureMode.WarnOnInsecureFileSystem` Java system property to `false` on each target WebLogic Server instance. This flag suppresses the insecure file system warnings in the WebLogic Server console in production mode. These warnings result from setting the correct file permissions to work with restricted security context constraints on Openshift.
105+
106+
Example:
107+
```yaml
108+
kubernetesPlatform: Openshift
109+
```
110+
99111
#### Creating the operator pod
100112

101113
##### `image`

documentation/staging/content/userguide/platforms/environments.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -65,6 +65,12 @@ Operator 2.5.0+ is certified for use on OpenShift Container Platform 4.3.0+ with
6565
When using the operator in OpenShift, a security context constraint is required to ensure that WebLogic containers run with a UNIX UID that has the correct permissions on the domain file system.
6666
This could be either the `anyuid` SCC or a custom one that you define for user/group `1000`. For more information, see [OpenShift]({{<relref "/security/openshift.md">}}) in the Security section.
6767

68+
Beginning with operator version 4.0, you should specify the `kubernetesPlatorm` Helm chart property and set its value to `Openshift` when installing the operator in Openshift. With this setting, the operator:
69+
- Configures the correct file permissions for WebLogic Server to work in Openshift.
70+
- Sets `weblogic.SecureMode.WarnOnInsecureFileSystem` Java system property to `false` on each target WebLogic Server instance. This flag suppresses the insecure file system warnings in the WebLogic Server console in production mode. These warnings result from setting the correct file permissions to work with restricted security context constraints on Openshift.
71+
For more information about the Helm chart, see the
72+
[Operator Helm configuration values]({{<relref "/userguide/managing-operators/using-helm#operator-helm-configuration-values">}}).
73+
6874
### Important note about development-focused Kubernetes distributions
6975

7076
There are a number of development-focused distributions of Kubernetes, like kind, Minikube, Minishift, and so on.

0 commit comments

Comments
 (0)