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
To manually remove the persistent volume claim and the persistent volume, use these commands:
172
+
By default, the domain's persistent volume claim and the persistent volume are created by the [Create WebLogic domain](kubernetes/create-weblogic-domain.sh) script, and are removed by the [Delete WebLogic domain resources](kubernetes/delete-weblogic-domain-resources.sh) script. To manually remove the persistent volume claim and the persistent volume, use these commands:
173
173
174
174
```
175
175
kubectl delete pvc PVC-NAME -n NAMESPACE
176
176
kubectl delete pv PV-NAME
177
177
```
178
178
179
-
Find the names of the persistent volume claim (represented above as `PVC-NAME`) and the persistent volume (represented as `PV-NAME`) in the domain custom resource YAML file, or if it is not available, check for the `domainUID` in the metadata on the persistent volumes. Replace `NAMESPACE` with the namespace that the operator is running in.
179
+
Find the names of the persistent volume claim (represented above as `PVC-NAME`) and the persistent volume (represented as `PV-NAME`) in the domain custom resource YAML file, or if it is not available, check for the `domainUID` in the metadata on the persistent volumes. Replace `NAMESPACE` with the namespace that the domain is running in.
180
180
181
181
To permanently delete the actual WebLogic domain configuration and domain home, delete the physical volume using the appropriate tools. For example, if the persistent volume used the `HostPath` provider, then delete the corresponding directory on the Kubernetes master.
182
182
183
+
## Updating a domain
184
+
There are times when a running domain needs to be updated with modified properties.
185
+
This can be achieved by following the steps below. For convenience of discussion, we assume that the domain is originally created by the following example command, where `/path/to/weblogic-operator-output-directory` is a directory that is created in advance to store the files that are generated by the operator.
186
+
187
+
```
188
+
./create-weblogic-domain.sh \
189
+
-i create-domain-job-inputs.yaml \
190
+
-o /path/to/weblogic-operator-output-directory
191
+
```
192
+
193
+
* Delete the domain using the [Delete WebLogic domain resources](kubernetes/delete-weblogic-domain-resources.sh) script.
* Delete the contents of the physical volume using the appropriate tools. See the descriptions in the previous section for removing a domain.
200
+
* Delete the contents in the `weblogic-domains/<domainUID>` directory under the output directory that is specified when the domain is originally created, which is `/path/to/weblogic-operator-output-directory` in our example.
201
+
* Update the create WebLogic domain inputs file `create-domain-job-inputs.yaml`.
202
+
* Recreate all resources that are labeled with the `domainUID`, but are not created by the [Create WebLogic domain](kubernetes/create-weblogic-domain.sh) script. One example of such resources is the `secret` for the domain credentials, which often is created manually and may be labeled with `domainUID`. Any resources that are not labeled with the `domainUID` are not affected because they are not deleted by the [Delete WebLogic domain resources](kubernetes/delete-weblogic-domain-resources.sh) script.
203
+
* Recreate the domain using the [Create WebLogic domain](kubectles/create-weblogic-domain.sh) script with the updated create WebLogic domain inputs file.
204
+
205
+
If for some reason the last step fails, then repeat the steps above after deleting the failed create WebLogic domain job, using the following command. The `<output-dir>` is the directory that is specified to the create WebLogic domain script via the `-o` option, which is `/path/to/weblogic-operator-output-directory` in our example if the same command is used to recreate the domain.
0 commit comments