Skip to content

Commit 376e689

Browse files
committed
Updated from review comments
1 parent 9e67839 commit 376e689

File tree

1 file changed

+12
-7
lines changed

1 file changed

+12
-7
lines changed

site/kubernetes.md

Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,18 @@
22

33
The Extract Domain Resource Tool can be used to create a domain resource file for use with the Oracle WebLogic Server Kubernetes Operator. This allows the domain configuration and the Kubernetes container configuration to be specified in a single model file.
44

5-
The Extract Domain Resource Tool is available with WDT releases 1.7.0 and later.
5+
This is especially useful when making configuration changes to the domain that also need to be reflected in the domain resource file. For example, adding a cluster to the domain only requires that it be added to the `topology` section of the WDT model, then a new domain resource file can be generated to apply to Kubernetes.
66

7-
More information about the Oracle WebLogic Server Kubernetes Operator can be found [here](https://github.com/oracle/weblogic-kubernetes-operator).
7+
More information about the Oracle WebLogic Server Kubernetes Operator can be found [here](https://oracle.github.io/weblogic-kubernetes-operator).
8+
9+
NOTE: The Extract Domain Resource Tool is available with WDT releases 1.7.0 and later.
810

911
Here is an example command line for the Extract Domain Resource Tool:
1012
```
11-
<wls-deploy-home>/bin/extractDomainResource.sh -oracle_home /tmp/oracle -domain_home /u01/mydomain -model_file /tmp/mymodel.yaml -domain_resource_file /tmp/operator/domain-resource.yaml
13+
<wls-deploy-home>/bin/extractDomainResource.sh -oracle_home /tmp/oracle -domain_home /u01/mydomain -model_file /tmp/mymodel.yaml -variable_file /tmp/my.properties -domain_resource_file /tmp/operator/domain-resource.yaml
1214
```
1315

14-
For the simplest case, the Extract Domain Resource Tool will create a sparse domain file. This is what is generated when there is not `kubernetes` section in the model, or that section is empty.
16+
For the simplest case, the Extract Domain Resource Tool will create a sparse domain file. This is what is generated when there is not a `kubernetes` section in the model, or that section is empty.
1517
```yaml
1618
apiVersion: weblogic.oracle/v6
1719
kind: Domain
@@ -30,9 +32,11 @@ spec:
3032
replicas: 4
3133
```
3234
33-
For this example, the user is expected to fill in the image and secrets information identified by `--FIX ME--` in the domain resource output. The value for `domainHome` was set from the command line. The `kind` and `name` were set to the domain name derived from the topology section of the model, or the default `base_domain`. The cluster entries are pulled from the topology section of the model, and their replica counts were derived from the number of servers for each cluster.
35+
In this example, the value for `domainHome` was set from the command line. The `kind` and `name` were set to the domain name derived from the topology section of the model, or the default `base_domain`. The cluster entries are pulled from the topology section of the model, and their replica counts were derived from the number of servers for each cluster.
36+
37+
The user is expected to fill in the image and secrets information identified by `--FIX ME--` in the domain resource output.
3438

35-
For more advanced configurations, the user can populate the `kubernetes` section of the WDT model, and those values will appear in the resulting domain resources file. This model section overrides and adds some values to the result.
39+
For more advanced configurations, including pre-populating the `--FIX ME--` values, the user can populate the `kubernetes` section of the WDT model, and those values will appear in the resulting domain resources file. This model section overrides and adds some values to the result.
3640
```yaml
3741
kubernetes:
3842
metadata:
@@ -43,14 +47,15 @@ kubernetes:
4347
imagePullSecrets:
4448
WEBLOGIC_IMAGE_PULL_SECRET_NAME:
4549
webLogicCredentialsSecret:
46-
name: WEBLOGIC_CREDENTIALS_SECRET_NAME
50+
name: '@@PROP:mySecret@@'
4751
serverPod:
4852
env:
4953
USER_MEM_ARGS:
5054
value: '-XX:+UseContainerSupport -Djava.security.egd=file:/dev/./urandom'
5155
JAVA_OPTIONS:
5256
value: '-Dmydir=/home/me'
5357
```
58+
This example uses `@@PROP:mySecret@@` to pull the value for `webLogicCredentialsSecret` from the variables file specified on the command line. This can be done with any of the values in the `kubernetes` section of the model. More details about using model variables can be found [here](../README.md/#simple-example).
5459

5560
For this example, the resulting domain resource file would contain:
5661
```yaml

0 commit comments

Comments
 (0)