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
* Have explicit default values in the input files
Signed-off-by: doxiao <[email protected]>
* Update README
Signed-off-by: doxiao <[email protected]>
* More update to the README
Signed-off-by: doxiao <[email protected]>
* Update one more property
Signed-off-by: doxiao <[email protected]>
echo" -n namespace, optional. The value is default if not specified"
46
-
echo" -d domainUID, optional. The default value is `domain1`. When specified, the secret will be label with the domainUID unless the given value is an empty string."
47
-
echo" -s secretName, optional. When not specified, the secret name will be determined based on the domainUID option"
45
+
echo" -d domainUID, optional. The default value is domain1. If specified, the secret will be labeled with the domainUID unless the given value is an empty string."
46
+
echo" -n namespace, optional. Use the default namespace if not specified"
47
+
echo" -s secretName, optional. If not specified, the secret name will be determined based on the domainUID value"
Copy file name to clipboardExpand all lines: kubernetes/samples/scripts/create-weblogic-domain/domain-home-on-pv/README.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,7 +73,7 @@ The following parameters can be provided in the inputs file.
73
73
|`createDomainFilesDir`| Directory to get all the create domain scripts and supporting files, including the script that is specified by the `createDomainScriptName` property. By default, this directory is set to the relative path `wlst`, and the create script will use the built-in WLST offline scripts in the `wlst` directory to create the WebLogic domain. It can also be set to the relative path `wdt`, and then the built-in WDT scripts will be used instead. An absolute path is also supported to point to an arbitrary directory in the file system. |`wlst`|
74
74
|`createDomainScriptsMountPath`| Mount path of the directory where the create domain scripts are located inside the pod. |`/u01/weblogic`|
75
75
|`createDomainScriptName`| Script that creates the domain. |`create-domain-job.sh`|
76
-
|`domainHome`| Home directory of the WebLogic domain. |`/shared/domains/<domainUID>`|
76
+
|`domainHome`| Home directory of the WebLogic domain. If not specified, the value is derived from the `domainUID` as `/shared/domains/<domainUID>`. |`/shared/domains/domain1`|
77
77
|`domainPVMountPath`| Mount path of the domain persistent volume. |`/shared`|
78
78
|`domainUID`| Unique ID that will be used to identify this particular domain. Used as the name of the generated WebLogic domain as well as the name of the Kubernetes domain resource. This ID must be unique across all domains in a Kubernetes cluster. This ID cannot contain any character that is not valid in a Kubernetes service name. |`domain1`|
79
79
|`exposeAdminNodePort`| Boolean indicating if the Administration Server is exposed outside of the Kubernetes cluster. |`false`|
@@ -84,15 +84,16 @@ The following parameters can be provided in the inputs file.
84
84
|`includeServerOutInPodLog`| Boolean indicating whether to include server .out to the pod's stdout. |`true`|
85
85
|`initialManagedServerReplicas`| Number of Managed Servers to initially start for the domain. |`2`|
86
86
|`javaOptions`| Java options for starting the Administration and Managed Servers. A Java option can have references to one or more of the following pre-defined variables to obtain WebLogic domain information: `$(DOMAIN_NAME)`, `$(DOMAIN_HOME)`, `$(ADMIN_NAME)`, `$(ADMIN_PORT)`, and `$(SERVER_NAME)`. |`-Dweblogic.StdoutDebugEnabled=false`|
87
-
|`logHome`| The in-pod name of the directory to store the domain, node manager, server logs, and server .out files in. |`/shared/logs/<domainUID>`|
87
+
|`logHome`| The in-pod name of the directory to store the domain, node manager, server logs, and server .out files in. If not specified, the value is derived from the `domainUID` as `/shared/logs/<domainUID>`. |`/shared/logs/domain1`|
88
88
|`managedServerNameBase`| Base string used to generate Managed Server names. |`managed-server`|
89
89
|`managedServerPort`| Port number for each Managed Server. |`8001`|
90
90
|`namespace`| Kubernetes namespace in which to create the domain. |`default`|
91
+
|`persistentVolumeClaimName`| Name of the persistent volume claim. If not specified, the value is derived from the `domainUID` as `<domainUID>-weblogic-sample-pvc`|`domain1-weblogic-sample-pvc`|
91
92
|`productionModeEnabled`| Boolean indicating if production mode is enabled for the domain. |`true`|
92
93
|`serverStartPolicy`| Determines which WebLogic Servers will be started up. Legal values are `NEVER`, `ALWAYS`, `IF_NEEDED`, `ADMIN_ONLY`. |`IF_NEEDED`|
93
94
|`t3ChannelPort`| Port for the T3 channel of the NetworkAccessPoint. |`30012`|
94
95
|`t3PublicAddress`| Public address for the T3 channel. |`kubernetes`|
95
-
|`weblogicCredentialsSecretName`| Name of the Kubernetes secret for the Administration Server's username and password. |`domain1-weblogic-credentials`|
96
+
|`weblogicCredentialsSecretName`| Name of the Kubernetes secret for the Administration Server's username and password. If not specified, the value is derived from the `domainUID` as `<domainUID>-weblogic-credentials`. |`domain1-weblogic-credentials`|
96
97
|`weblogicImagePullSecretName`| Name of the Kubernetes secret for the Docker Store, used to pull the WebLogic Server image. |`docker-store-secret`|
97
98
98
99
Note that the names of the Kubernetes resources in the generated YAML files may be formed with the value of some of the properties specified in the `create-inputs.yaml` file. Those properties include the `adminServerName`, `clusterName` and `managedServerNameBase`. If those values contain any characters that are invalid in a Kubernetes service name, those characters are converted to valid values in the generated YAML files. For example, an uppercase letter is converted to a lowercase letter and an underscore `("_")` is converted to a hyphen `("-")`.
0 commit comments