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: kubernetes/samples/scripts/create-weblogic-domain/domain-home-in-image/README.md
+12-3Lines changed: 12 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,12 +60,21 @@ If you copy the sample scripts to a different location, make sure that you copy
60
60
The default domain created by the script has the following characteristics:
61
61
62
62
* An Administration Server named `admin-server` listening on port `7001`.
63
-
* A dynamic cluster named `cluster-1` of size 2.
63
+
* A dynamic cluster named `cluster-1` of size 5.
64
64
* Two Managed Servers, named `managed-server1` and `managed-server2`, listening on port `8001`.
65
65
* No applications deployed.
66
-
* A Derby data source.
67
66
* A T3 channel.
68
67
68
+
If you are running the sample from a machine that is remote to the Kubernetes cluster where the domain will be running, you need to push the new image to a registry that is local to the cluster. In this case, you need to do the following:
69
+
* Set the `image` property in the inputs file to the target image name (including the tag if needed).
70
+
* Run the `create-domain.sh` script without the `-e` option.
71
+
* Push the generated image domain-home-in-image-wdti:lastest (or domain-home-in-image-wlst:latest) to the target image name.
The domain creation inputs can be customized by editing `create-domain-inputs.yaml`.
70
79
71
80
### Configuration parameters
@@ -84,7 +93,7 @@ The following parameters can be provided in the inputs file.
84
93
|`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`|
85
94
|`exposeAdminNodePort`| Boolean indicating if the Administration Server is exposed outside of the Kubernetes cluster. |`false`|
86
95
|`exposeAdminT3Channel`| Boolean indicating if the T3 administrative channel is exposed outside the Kubernetes cluster. |`false`|
87
-
|`image`| WebLogic Docker image that the domain resource will pull if needed. You only need to specify this if you are going to push the generated image from the local Docker repository to another Docker repository. If not specified, the sample uses the internally generated image name, either "domain-home-in-image:latest" or "domain-home-in-image-wdt:latest". ||
96
+
|`image`| WebLogic Docker image that the domain resource will pull if needed. You only need to specify this if you are going to tag the generated image to a different name. If not specified, the sample uses the internally generated image name, either "domain-home-in-image-wdt:latest" or "domain-home-in-image-wlst:latest". ||
88
97
|`imagePullPolicy`| WebLogic Docker image pull policy. Legal values are "IfNotPresent", "Always", or "Never" |`IfNotPresent`|
89
98
|`imagePullSecretName`| Name of the Kubernetes secret to access the Docker Store to pull the WebLogic Server Docker image. The presence of the secret will be validated when this parameter is specified ||
90
99
|`includeServerOutInPodLog`| Boolean indicating whether to include server .out to the pod's stdout. |`true`|
Copy file name to clipboardExpand all lines: site/quickstart.md
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -162,7 +162,9 @@ domain namespace (`sample-domain1-ns`) and the `domainHomeImageBase` (`oracle/we
162
162
163
163
* Setting `weblogicCredentialsSecretName` to the name of the secret containing the WebLogic credentials.
164
164
By convention, the secret will be named`domainUID-weblogic-credentials` (where `domainUID` is replaced with the
165
-
actual `domainUID` value).
165
+
actual `domainUID` value).
166
+
167
+
* Leaving the `image` empty unless you need to tag the new image that the script builds to a different name.
166
168
167
169
For example, assuming you named your copy `my-inputs.yaml`:
168
170
```
@@ -175,6 +177,15 @@ respectively, as shown in the example. If you specify the `-e` option, the scri
175
177
Kubernetes YAML files *and* apply them to your cluster. If you omit the `-e` option, the
176
178
script will just generate the YAML files, but will not take any action on your cluster.
177
179
180
+
If you are running the sample from a machine that is remote to the Kubernetes cluster where the domain will be running, you need to push the new image to a registry that is local to the cluster. In this case, you need to do the following:
181
+
* Set the `image` property in the inputs file to the target image name (including the tag if needed).
182
+
* run the `create-domain.sh` script without the `-e` option.
183
+
* Push the generated image domain-home-in-image-wdti:lastest (or domain-home-in-image-wlst:latest) to the target image name.
0 commit comments