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: site/domains.md
+2-27Lines changed: 2 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,3 @@
1
-
**TODO** write me
2
-
3
1
## Create and manage WebLogic domains
4
2
5
3
In this version of the operator, a WebLogic domain can be located either in a persistent volume (PV) or in a Docker image.
@@ -19,14 +17,6 @@ You can also mix and match on a domain by domain basis.
19
17
| There are less images to manage and store, which could provide significant storage and network savings. | There are more images to manage and store in this approach. |
20
18
| You may be able to use standard Oracle-provided images or at least a very small number of self-built images, e.g. with patches installed. | You may need to do more work to set up processes to build and maintain your images. |
21
19
22
-
* WebLogic binary image when domain is persisted to a PV (as in Operator v1.1)
23
-
* WebLogic domain image where the domain is persisted to a Docker image (new for Operator v2.0). The WebLogic domain image will contain the WebLogic binaries, domain configuration, and applications.
24
-
25
-
You create the WebLogic domain inside of a Docker image or in a PV using WebLogic Scripting Tool (WLST) or WebLogic Deploy Tooling (WDT).
26
-
* (Describe the advantages of using WDT. See samples, Domain in image WDT, Domain in image WLST, Domain in PV WDT, Domain in PV WLST.)
27
-
28
-
(What images do we need before we get started? Operator 2.0 requires you to patch your WebLogic image 12.2.1.3 with patch #.)
29
-
30
20
### Preparing the Kubernetes cluster to run WebLogic domains
31
21
32
22
Perform these steps to prepare your Kubernetes cluster to run a WebLogic domain:
@@ -40,7 +30,6 @@ Perform these steps to prepare your Kubernetes cluster to run a WebLogic domain:
40
30
Replace `domain-namespace-1` with name you want to use. The name must follow standard Kubernetes naming conventions, i.e. lower case,
41
31
numbers and hyphens.
42
32
43
-
1. Define RBAC roles for the domain. **TODO** what RBAC roles?
44
33
1. Create a Kubernetes secret containing the Administration Server boot credentials. You can do this manually or using
45
34
[the provided sample](/kubernetes/samples/scripts/create-weblogic-domain-credentials/README.md). To create
46
35
the secret manually, use this command:
@@ -91,9 +80,7 @@ Please consult My Oracle Support Doc ID 2349228.1 for up-to-date information abo
91
80
92
81
### Creating and managing WebLogic domains
93
82
94
-
To create and manage a WebLogic domain in Kubernetes we create a deployment type, the domain custom resource. The operator introspects the custom resource and manages the domain deployment to adjust to the definitions in the custom resource. This custom resource can also be managed using the Kubernetes command-line interface `kubectl`.
95
-
* (Point to documentation how to edit the domain inputs YAML and how to create the domain custom resource.)
96
-
* Create Ingress controllers if you are using a load balancer that supports them, such as Traefik or Voyager.
83
+
Please see [this page](creating-domain.md) for information about creating and managing domains.
97
84
98
85
### Modifying domain configurations
99
86
@@ -104,15 +91,11 @@ You can modify the WebLogic domain configuration for both the "domain in persist
104
91
105
92
Configuration overrides allow changing a configuration without modifying its original `config.xml` or system resource xml files, and also support parameterizing overrides so that you can inject values into them from Kubernetes secrets. For example, you can inject database usernames, passwords, and URLs that are stored in a secret.
106
93
107
-
### Managing lifecycle operations
94
+
### Managing lifecycle operations including shutting down and deleting domains
108
95
109
96
In Operator 2.0 you can perform lifecycle operations on WebLogic servers, clusters, or domains.
110
97
See [Starting, stopping and restarting servers](server-lifecycle.md).
111
98
112
-
### Patching WebLogic and performing application updates
113
-
114
-
**TODO** write me
115
-
116
99
### Scaling clusters
117
100
118
101
The operator allows you to initiate scaling of clusters in various ways:
@@ -122,11 +105,3 @@ The operator allows you to initiate scaling of clusters in various ways:
0 commit comments