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: docs-source/content/_index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,8 +17,8 @@ Oracle is finding ways for organizations using WebLogic Server to run important
17
17
The fastest way to experience the operator is to follow the [Quick Start guide]({{< relref "/quickstart/_index.md" >}}), or you can peruse our [documentation]({{< relref "/userguide/_index.md" >}}), read our [blogs](https://blogs.oracle.com/weblogicserver/updated-weblogic-kubernetes-support-with-operator-20), or try out the [samples]({{< relref "/samples/_index.md" >}}).
18
18
19
19
***
20
-
The [current release of the operator](https://github.com/oracle/weblogic-kubernetes-operator/releases) is 2.2.1.
21
-
This release was published on June 20, 2019.
20
+
The [current release of the operator](https://github.com/oracle/weblogic-kubernetes-operator/releases) is 2.3.0.
Copy file name to clipboardExpand all lines: docs-source/content/release-notes.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,8 +8,9 @@ draft: false
8
8
9
9
| Date | Version | Introduces backward incompatibilities | Change |
10
10
| --- | --- | --- | --- |
11
-
| June 20, 2019 | v2.2.1 | no | The operator now supports Kubernetes 1.14.0+. This release is primarily a bug fix release and resolves the following issues:<br><ul><li>Servers in domains, where the domain home is on a persistent volume, would sometimes fail to start. These failures would be during the introspection phase following a full domain shutdown. Now, the introspection script better handles the relevant error conditions.</li><li>The domain resource provides an option to <ahref="https://github.com/oracle/weblogic-kubernetes-operator/blob/master/docs/domains/Domain.md#server-service">pre-create Kubernetes services</a> for WebLogic Servers that are not yet running so that the DNS addresses of these services are resolvable. These services are now created as non-headless so that they have an IP address.</li></ul>
12
-
| June 6, 2019 | v2.2.0 | no | Added support for FMW Infrastructure domains. WebLogic Server instances are now gracefully shut down by default and shutdown options are configurable. Operator is now built and runs on JDK 11.
11
+
|| v2.3.0 | no |
12
+
| June 20, 2019 | v2.2.1 | no | The operator now supports Kubernetes 1.14.0+. This release is primarily a bug fix release and resolves the following issues:<br><ul><li>Servers in domains, where the domain home is on a persistent volume, would sometimes fail to start. These failures would be during the introspection phase following a full domain shutdown. Now, the introspection script better handles the relevant error conditions.</li><li>The domain resource provides an option to <ahref="https://github.com/oracle/weblogic-kubernetes-operator/blob/master/docs/domains/Domain.md#server-service">pre-create Kubernetes services</a> for WebLogic Servers that are not yet running so that the DNS addresses of these services are resolvable. These services are now created as non-headless so that they have an IP address.</li></ul>
13
+
| June 6, 2019 | v2.2.0 | no | Added support for FMW Infrastructure domains. WebLogic Server instances are now gracefully shut down by default and shutdown options are configurable. Operator is now built and runs on JDK 11.
13
14
| April 4, 2019 | v2.1 | no | Customers can add init and sidecar containers to generated pods.
14
15
| March 4, 2019 | v2.0.1 | no | OpenShift support is now certified. Many bug fixes, including fixes for configuration overrides, cluster services, and domain status processing.
15
16
| January 24, 2019 | v2.0 | yes; not compatible with 1.x releases, but is compatible with 2.0-rc2. | Final version numbers and documentation updates.
Copy file name to clipboardExpand all lines: docs-source/content/samples/simple/storage/_index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,7 +68,7 @@ The PV and PVC creation inputs can be customized by editing the `create-pv-pvc-i
68
68
69
69
#### Shared versus dedicated PVC
70
70
71
-
By default, the `domainUID` is left empty in the inputs file, which means the generated PV and PVC will not be associated with a particular domain, but can be shared by multiple domain resources in the same Kubernetes namespaces as the PV and PVC.
71
+
By default, the `domainUID` is left empty in the inputs file, which means the generated PV and PVC will not be associated with a particular domain, but can be shared by multiple domain resources in the same Kubernetes namespaces as the PV and PVC. If the PV/PVC is being shared across domains, then, as a best practice, you should specify a unique `baseName`.
72
72
73
73
For the use cases where dedicated PV and PVC are desired for a particular domain, the `domainUID` needs to be set in the `create-pv-pvc-inputs.yaml` file. The presence of a non-empty `domainUID` in the inputs file will cause the generated PV and PVC to be associated with the specified `domainUID`. The association includes that the names of the generated YAML files and the Kubernetes PV and PVC objects are decorated with the `domainUID`, and the PV and PVC objects are also labeled with the `domainUID`.
For more details on acquiring the operator image and prerequisites for installing the operator, consult the [Quick Start guide]({{< relref "/quickstart/_index.md" >}}).
Copy file name to clipboardExpand all lines: integration-tests/README.md
+16-17Lines changed: 16 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,8 +7,8 @@ This documentation describes the functional use cases that are covered in integr
7
7
The tests currently run in three modes: "shared cluster", "Jenkins", and "standalone" Oracle Linux, where the mode is controlled by the `SHARED_CLUSTER` and `JENKINS` environment variables described below. The default is "standalone".
8
8
9
9
* "Standalone" Oracle Linux, i.e, run the tests manually with the `mvn` command.
* Jenkins - http://wls-jenkins.us.oracle.com/view/weblogic-operator/job/weblogic-kubernetes-operator-javatest/ - Jenkins Run is restricted to Oracle Internal development process.
* Jenkins - http://wls-jenkins.us.oracle.com/view/weblogic-operator/job/weblogic-kubernetes-operator-javatest/ - Jenkins Run is restricted to Oracle Internal development process.
12
12
13
13
Shared cluster runs only Quick test use cases, Jenkins runs both Quick and Full test use cases.
14
14
@@ -183,18 +183,18 @@ K8sTestUtils - uses k8s java client api, this is used only for delete domain use
183
183
* export WEBLOGIC_IMAGE_NAME and WEBLOGIC_IMAGE_TAG if different from container-registry.oracle.com/middleware/weblogic and 12.2.1.3
184
184
* Setup docker access to WebLogic 12c Images
185
185
186
-
Method 1
187
-
- Setup a personal account on container-registry.oracle.com
188
-
- Then sign in to container-registry.oracle.com and signup for access to WebLogic 12.2.1.3 images from container-registry.oracle.com/middleware/weblogic:12.2.1.3
189
-
- Then export the following before running the tests:
186
+
*Method 1
187
+
- Setup a personal account on container-registry.oracle.com
188
+
- Then sign in to container-registry.oracle.com and signup for access to WebLogic 12.2.1.3 images from container-registry.oracle.com/middleware/weblogic:12.2.1.3
189
+
- Then export the following before running the tests:
190
190
```
191
191
export OCR_USERNAME=<ocr_username>
192
192
export OCR_PASSWORD=<ocr_password>
193
193
```
194
194
195
-
Method 2
196
-
- Make sure the weblogic image i.e. container-registry.oracle.com/middleware/weblogic:12.2.1.3 already exists locally in a docker repository the k8s cluster can access
197
-
- Make sure the weblogic image has patch p29135930 (required for the WebLogic Kubernetes Operator).
195
+
*Method 2
196
+
- Make sure the weblogic image i.e. container-registry.oracle.com/middleware/weblogic:12.2.1.3 already exists locally in a docker repository the k8s cluster can access
197
+
- Make sure the weblogic image has patch p29135930 (required for the WebLogic Kubernetes Operator).
198
198
199
199
200
200
* Command to run the tests:
@@ -296,20 +296,19 @@ JUnit test results can be seen at "integration-tests/target/failsafe-reports/TES
296
296
297
297
# How to run JRF domain In Operator related tests
298
298
* Setup docker access to FMW Infrastructure 12c Image and Oracle Database 12c Image
299
-
300
-
Method 1
301
-
- Setup a personal account on container-registry.oracle.com
302
-
- Then sign in to container-registry.oracle.com and accept license for access to Oracle Database 12c Images: **_container-registry.oracle.com/database/enterprise:12.2.0.1-slim_**
303
-
- And get access to FMW Infrastructure 12c Image: **_container-registry.oracle.com/middleware/fmw-infrastructure:12.2.1.3_**
304
-
- export the following before running the tests:
299
+
* Method 1
300
+
- Setup a personal account on container-registry.oracle.com
301
+
- Then sign in to container-registry.oracle.com and accept license for access to Oracle Database 12c Images: **_container-registry.oracle.com/database/enterprise:12.2.0.1-slim_**
302
+
- And get access to FMW Infrastructure 12c Image: **_container-registry.oracle.com/middleware/fmw-infrastructure:12.2.1.3_**
303
+
- export the following before running the tests:
305
304
```
306
305
export REPO_USERNAME=<ocr_username>
307
306
export REPO_PASSWORD=<ocr_password>
308
307
export REPO_EMAIL=<ocr_email>
309
308
```
310
309
311
-
Method 2
312
-
- Make sure the FMW Infrastructure image i.e. **_container-registry.oracle.com/middleware/fmw-infrastructure:12.2.1.3_** and the Oracle database image i.e. **_container-registry.oracle.com/database/enterprise:12.2.0.1-slim_** already exist locally in a docker repository the k8s cluster can access
310
+
* Method 2
311
+
- Make sure the FMW Infrastructure image i.e. **_container-registry.oracle.com/middleware/fmw-infrastructure:12.2.1.3_** and the Oracle database image i.e. **_container-registry.oracle.com/database/enterprise:12.2.0.1-slim_** already exist locally in a docker repository the k8s cluster can access
0 commit comments