Skip to content

Commit 01a9d76

Browse files
committed
Add additional info in quickstart and sample readme, and also tag the image if needed
Signed-off-by: doxiao <[email protected]>
1 parent 416f623 commit 01a9d76

File tree

4 files changed

+45
-14
lines changed

4 files changed

+45
-14
lines changed

kubernetes/samples/scripts/create-weblogic-domain/domain-home-in-image/README.md

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -60,12 +60,21 @@ If you copy the sample scripts to a different location, make sure that you copy
6060
The default domain created by the script has the following characteristics:
6161

6262
* 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.
6464
* Two Managed Servers, named `managed-server1` and `managed-server2`, listening on port `8001`.
6565
* No applications deployed.
66-
* A Derby data source.
6766
* A T3 channel.
6867

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.
72+
* Run the following command to create the domain.
73+
74+
```
75+
kubectl apply -f /path/to/output-directory/weblogic-domains/<domainUID>/domain.yaml
76+
```
77+
6978
The domain creation inputs can be customized by editing `create-domain-inputs.yaml`.
7079

7180
### Configuration parameters
@@ -84,7 +93,7 @@ The following parameters can be provided in the inputs file.
8493
| `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` |
8594
| `exposeAdminNodePort` | Boolean indicating if the Administration Server is exposed outside of the Kubernetes cluster. | `false` |
8695
| `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". | |
8897
| `imagePullPolicy` | WebLogic Docker image pull policy. Legal values are "IfNotPresent", "Always", or "Never" | `IfNotPresent` |
8998
| `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 | |
9099
| `includeServerOutInPodLog` | Boolean indicating whether to include server .out to the pod's stdout. | `true` |

kubernetes/samples/scripts/create-weblogic-domain/domain-home-in-image/create-domain-inputs.yaml

Lines changed: 19 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,8 @@ adminPort: 7001
1111
adminServerName: admin-server
1212

1313
# Unique ID identifying a domain.
14-
# This ID must not contain an underscope ("_"), and must be lowercase and unique across all domains in a Kubernetes cluster.
14+
# This ID must not contain an underscope ("_"), and must be lowercase and unique across all domains
15+
# in a Kubernetes cluster.
1516
domainUID: domain1
1617

1718
# Type of WebLogic Cluster
@@ -41,11 +42,18 @@ managedServerPort: 8001
4142
productionModeEnabled: true
4243

4344
# WebLogic Docker image that the domain resource will pull if needed.
44-
# You only need to specify this if you are going to push the generated image from the local Docker repository
45-
# to another Docker repository.
46-
# If not specified, the sample uses the internally generated image name, either "domain-home-in-image:latest"
47-
# or "domain-home-in-image-wdt:latest".
48-
# image:
45+
#
46+
# You only need to specify this if you want to tag the generated image to a different name.
47+
#
48+
# If you are running the sample script from a machine that is remote to the Kubernetes cluster,
49+
# you need to specify this to point to an image in a registry local to the cluster. You
50+
# then need to push the generate image to that registry before starting the domain.
51+
#
52+
# If not specified, the sample uses the internally generated image name,
53+
# either "domain-home-in-image-wdt:latest" or "domain-home-in-image-wlst:latest".
54+
#
55+
# See README.md for more help.
56+
#image:
4957

5058
# Image pull policy
5159
# Legal values are "IfNotPresent", "Always", or "Never"
@@ -89,13 +97,14 @@ namespace: default
8997
javaOptions: -Dweblogic.StdoutDebugEnabled=false
9098

9199
# Base WebLogic binary image used to build the WebLogic domain image
92-
# The operator requires WebLogic Server 12.2.1.3.0 with patch 28076014 applied. See README.md for more help.
93-
# domainHomeImageBase:
100+
# The operator requires WebLogic Server 12.2.1.3.0 with patch 28076014 applied.
101+
# See README.md for more help.
102+
#domainHomeImageBase:
94103

95104
# Location of the WebLogic "domain home in image" Docker image sample in the
96105
# `https://github.com/oracle/docker-images.git` project.
97106
# If not specified, use "./docker-images/OracleWebLogic/samples/12213-domain-home-in-image-wdt".
98-
# Another possible value is "./docker-images/OracleWebLogic/samples/12213-domain-home-in-image" which
99-
# uses WLST script, instead of WDT, to generate the domain configuration.
107+
# Another possible value is "./docker-images/OracleWebLogic/samples/12213-domain-home-in-image",
108+
# which uses a WLST script, instead of WDT, to generate the domain configuration.
100109
domainHomeImageBuildPath: ./docker-images/OracleWebLogic/samples/12213-domain-home-in-image-wdt
101110

kubernetes/samples/scripts/create-weblogic-domain/domain-home-in-image/create-domain.sh

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -289,6 +289,8 @@ function createDomainHome {
289289
# if use the default images, we tag it to a more generic name (without the release version numbers)
290290
if [ -z $image ]; then
291291
docker tag $imageNameOrigin:latest $imageName:latest
292+
else
293+
docker tag $imageNameOrigin:latest $image
292294
fi
293295

294296
if [ "$?" != "0" ]; then

site/quickstart.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -162,7 +162,9 @@ domain namespace (`sample-domain1-ns`) and the `domainHomeImageBase` (`oracle/we
162162

163163
* Setting `weblogicCredentialsSecretName` to the name of the secret containing the WebLogic credentials.
164164
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.
166168

167169
For example, assuming you named your copy `my-inputs.yaml`:
168170
```
@@ -175,6 +177,15 @@ respectively, as shown in the example. If you specify the `-e` option, the scri
175177
Kubernetes YAML files *and* apply them to your cluster. If you omit the `-e` option, the
176178
script will just generate the YAML files, but will not take any action on your cluster.
177179

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.
184+
* Run the following command to create the domain.
185+
186+
```
187+
kubectl create -f /some/output/directory/weblogic-domains/sample-domain1/domain.yaml
188+
```
178189
c. Confirm that the operator started the servers for the domain:
179190
* Use `kubectl` to show that the domain resource was created:
180191
```

0 commit comments

Comments
 (0)