Skip to content

Commit 54669e3

Browse files
committed
wip
1 parent 795f0ca commit 54669e3

File tree

1 file changed

+7
-7
lines changed
  • kubernetes/samples/scripts/create-weblogic-domain/domain-home-on-pv

1 file changed

+7
-7
lines changed

kubernetes/samples/scripts/create-weblogic-domain/domain-home-on-pv/README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Before you begin, read this guide, [Domain Resource](../../../../../site/domain-
88

99
The following prerequisites must be handled prior to running the create domain script:
1010
* Make sure the WebLogic operator is running.
11-
* The operator requires WebLogic Server 12.2.1.3.0 with patch 28076014 applied. Refer to [Weblogic docker images](../../../../../site/weblogic-docker-images.md) for details on how to create one.
11+
* The operator requires WebLogic Server 12.2.1.3.0 with patch 28076014 applied. Refer to [WebLogic docker images](../../../../../site/weblogic-docker-images.md) for details on how to create one.
1212
* Create a Kubernetes namespace for the domain unless the intention is to use the default namespace.
1313
* In the same Kubernetes namespace, create the Kubernetes persistent volume where the domain home will be hosted, and the Kubernetes persistent volume claim for the domain. For samples to create a PV and PVC, see [Create sample PV and PVC](../../create-weblogic-domain-pv-pvc/README.md).
1414
* Create the Kubernetes secrets `username` and `password` of the admin account in the same Kubernetes namespace as the domain.
@@ -18,19 +18,19 @@ The following prerequisites must be handled prior to running the create domain s
1818
Make a copy of the `create-domain-inputs.yaml` file, and run the create script, pointing it at your inputs file and an output directory:
1919

2020
```
21-
./create-domain.sh \
21+
$ ./create-domain.sh \
2222
-i create-domain-inputs.yaml \
2323
-o /path/to/output-directory
2424
```
2525

2626
The script will perform the following steps:
2727

28-
* Create a directory for the generated Kubernetes YAML files for this domain if it does not already exist. The pathname is `/path/to/weblogic-operator-output-directory/weblogic-domains/<domainUID>`. If the directory already exists, its contents will be removed.
28+
* Create a directory for the generated Kubernetes YAML files for this domain if it does not already exist. The pathname is `/path/to/weblogic-operator-output-directory/weblogic-domains/<domainUID>`. If the directory already exists, its contents must be removed before using this script.
2929
* Create a Kubernetes job that will start up a utility WebLogic Server container and run offline WLST scripts, or WebLogic Deploy Tool (WDT) scripts, to create the domain on the shared storage.
3030
* Run and wait for the job to finish.
3131
* Create a Kubernetes domain YAML file, `domain.yaml`, in the directory that is created above. This YAML file can be used to create the Kubernetes resource using the `kubectl create -f` or `kubectl apply -f` command:
3232
```
33-
kubectl apply -f /path/to/output-directory/weblogic-domains/<domainUID>/domain.yaml
33+
$ kubectl apply -f /path/to/output-directory/weblogic-domains/<domainUID>/domain.yaml
3434
```
3535

3636
* Create a convenient utility script, `delete-domain-job.yaml`, to clean up the domain home created by the create script.
@@ -206,7 +206,7 @@ spec:
206206
To confirm that the domain was created, use this command:
207207

208208
```
209-
kubectl describe domain DOMAINUID -n NAMESPACE
209+
$ kubectl describe domain DOMAINUID -n NAMESPACE
210210
```
211211

212212
Replace `DOMAINUID` with the `domainUID` and `NAMESPACE` with the actual namespace.
@@ -321,7 +321,7 @@ In the `Status` section of the output, the available servers and clusters are li
321321
Use the following command to see the pods running the servers:
322322

323323
```
324-
kubectl get pods -n NAMESPACE
324+
$ kubectl get pods -n NAMESPACE
325325
```
326326

327327
Here is an example of the output of this command:
@@ -339,7 +339,7 @@ domain1-managed-server2 1/1 Running 0 8m
339339
Use the following command to see the services for the domain:
340340

341341
```
342-
kubectl get services -n NAMESPACE
342+
$ kubectl get services -n NAMESPACE
343343
```
344344

345345
Here is an example of the output of this command:

0 commit comments

Comments
 (0)