Operator version 3.0.2

README.md

@@ -17,8 +17,8 @@ Oracle is finding ways for organizations using WebLogic Server to run important
 The fastest way to experience the operator is to follow the [Quick Start guide](https://oracle.github.io/weblogic-kubernetes-operator/quickstart/), or you can peruse our [documentation](https://oracle.github.io/weblogic-kubernetes-operator), read our [blogs](https://blogs.oracle.com/weblogicserver/updated-weblogic-kubernetes-support-with-operator-20), or try out the [samples](https://oracle.github.io/weblogic-kubernetes-operator/samples/).
 
 ***
-The [current release of the operator](https://github.com/oracle/weblogic-kubernetes-operator/releases) is 3.0.1.
-This release was published on August 13, 2020.
+The [current release of the operator](https://github.com/oracle/weblogic-kubernetes-operator/releases) is 3.0.2.
+This release was published on September 15, 2020.
 ***
 
 # Documentation

buildDockerImage.sh

@@ -33,7 +33,7 @@ while getopts "t:" optname; do
   esac
 done
 
-IMAGE_NAME=${name:-oracle/weblogic-kubernetes-operator:3.0.1}
+IMAGE_NAME=${name:-oracle/weblogic-kubernetes-operator:3.0.2}
 SCRIPTPATH="$( cd "$(dirname "$0")" > /dev/null 2>&1 ; pwd -P )"
 
 # Proxy settings

buildtime-reports/pom.xml

@@ -8,7 +8,7 @@
     <parent>
         <artifactId>operator-parent</artifactId>
         <groupId>oracle.kubernetes</groupId>
-        <version>3.0.1</version>
+        <version>3.0.2</version>
     </parent>
 
     <artifactId>buildtime-reports</artifactId>

docs-source/content/_index.md

@@ -23,8 +23,8 @@ using the operator to deploy and run a WebLogic domain container-packaged web ap
 ***
 #### Current production release
 
-The [current release of the operator](https://github.com/oracle/weblogic-kubernetes-operator/releases) is 3.0.1.
-This release was published on August 13, 2020. See the operator prerequisites and supported environments [here]({{< relref "/userguide/introduction/introduction#operator-prerequisites" >}}).
+The [current release of the operator](https://github.com/oracle/weblogic-kubernetes-operator/releases) is 3.0.2.
+This release was published on September 15, 2020. See the operator prerequisites and supported environments [here]({{< relref "/userguide/introduction/introduction#operator-prerequisites" >}}).
 
 This release introduces _non-backward compatible_ changes; however, operators using this release can be run in the same
 Kubernetes cluster as operators using the 2.6.0 version allowing for staged migration. You can replace a 2.6.0 operator with a 3.x operator without needing to recreate any existing domains; however, you must delete the 2.6.0 Helm release and then install the 3.x version rather than using a Helm upgrade. When the 3.x operator starts, it will roll any running WebLogic Server instances

docs-source/content/faq/namespace-management.md

@@ -40,7 +40,7 @@ elkIntegrationEnabled: false
 externalDebugHttpPort: 30999
 externalRestEnabled: false
 externalRestHttpsPort: 31001
-image: oracle/weblogic-kubernetes-operator:3.0.1
+image: oracle/weblogic-kubernetes-operator:3.0.2
 imagePullPolicy: IfNotPresent
 internalDebugHttpPort: 30999
 istioEnabled: false

docs-source/content/quickstart/get-images.md

@@ -19,7 +19,7 @@ and accept the license agreement for the [WebLogic Server image](https://hub.doc
 1. Pull the operator image:
 
     ```bash
-    $ docker pull oracle/weblogic-kubernetes-operator:3.0.1
+    $ docker pull oracle/weblogic-kubernetes-operator:3.0.2
     ```
 
 1. Pull the Traefik load balancer image:

docs-source/content/quickstart/install.md

@@ -71,7 +71,7 @@ $ helm install traefik-operator stable/traefik \
     ```bash
     $ helm install sample-weblogic-operator kubernetes/charts/weblogic-operator \
       --namespace sample-weblogic-operator-ns \
-      --set image=oracle/weblogic-kubernetes-operator:3.0.1 \
+      --set image=oracle/weblogic-kubernetes-operator:3.0.2 \
       --set serviceAccount=sample-weblogic-operator-sa \
       --set "domainNamespaces={}" \
       --wait

docs-source/content/release-notes.md

@@ -4,10 +4,11 @@ date: 2019-03-15T11:25:28-04:00
 draft: false
 ---
 
-### Recent changes
+### Releases
 
-| Date | Version | Introduces backward incompatibilities | Change |
+| Date | Version | Introduces backward incompatibilities? | Changes |
 | --- | --- | --- | --- |
+| September 15, 2020 | v3.0.2 | no | This release contains several fixes, including improvements to log rotation and a fix that avoids unnecessarily updating the domain status. |
 | August 13, 2020 | v3.0.1 | no | Fixed an issue preventing the REST interface from working after a Helm upgrade. Helm 3.1.3+ now required. |
 | July 17, 2020 | v3.0.0 | yes | Adds Model in Image feature and support for applying topology and configuration override changes without downtime. Removal of support for Helm 2.x. Operator performance improvements to manage many domains in the same Kubernetes cluster. |
 | June 22, 2020 | v2.6.0 | no | Kubernetes 1.16, 1.17, and 1.18 support. Removal of support for Kubernetes 1.13 and earlier. This release can be run in the same cluster with operators of either 2.5.0 and below, or with 3.x providing an upgrade path. Certified support of Oracle Linux Cloud Native Environment (OLCNE) 1.1 with Kubernetes 1.17.0.
@@ -26,6 +27,22 @@ draft: false
 | April 4, 2018 | 0.2 | yes | Many Kubernetes artifact names and labels have changed. Also, the names of generated YAML files for creating a domain's PV and PVC have changed.  Because of these changes, customers must recreate their operators and domains.
 | March 20, 2018 |  | yes | Several files and input parameters have been renamed.  This affects how operators and domains are created.  It also changes generated Kubernetes artifacts, therefore customers must recreate their operators and domains.
 
+### Change log
+
+#### Operator 3.0.2
+
+* Removed unnecessary duplicated parameter in initialize-internal-operator-identity.sh script ([#1867](https://github.com/oracle/weblogic-kubernetes-operator/pull/1867)).
+* Support nodeAffinity and nodeSelector for the operator in its Helm chart ([#1869](https://github.com/oracle/weblogic-kubernetes-operator/pull/1869)).
+* Log file rotation enhancements and documentation ([#1872](https://github.com/oracle/weblogic-kubernetes-operator/pull/1872), [#1827](https://github.com/oracle/weblogic-kubernetes-operator/pull/1827)).
+* Production support for the NGINX ingress controller ([#1878](https://github.com/oracle/weblogic-kubernetes-operator/pull/1878)).
+* Prevent unnecessary changes to Domain status that were causing churn to the resourceVersion ([#1879](https://github.com/oracle/weblogic-kubernetes-operator/pull/1879)).
+* Better reflect introspector status in the Domain status ([#1832](https://github.com/oracle/weblogic-kubernetes-operator/pull/1832)).
+* Create each pod after any previous pods have been scheduled to allow for correct anti-affinity behavior ([#1855](https://github.com/oracle/weblogic-kubernetes-operator/pull/1855)).
+
+#### Operator 3.0.1
+
+* Resolved an issue where a Helm upgrade was incorrectly removing the operator's private key thereby disabling the operator's REST interface ([#1846](https://github.com/oracle/weblogic-kubernetes-operator/pull/1846)).
+
 ### Known issues
 
 | Issue | Description |

docs-source/content/userguide/introduction/architecture.md

@@ -18,7 +18,7 @@ The operator is packaged in a [Docker image](https://hub.docker.com/r/oracle/web
 
 ```
 $ docker login
-$ docker pull oracle/weblogic-kubernetes-operator:3.0.1
+$ docker pull oracle/weblogic-kubernetes-operator:3.0.2
 ```
 
 For more details on acquiring the operator image and prerequisites for installing the operator, consult the [Quick Start guide]({{< relref "/quickstart/_index.md" >}}).

docs-source/content/userguide/introduction/introduction.md

@@ -16,7 +16,7 @@ Detailed instructions are available [here]({{< relref "/userguide/managing-opera
 
 ### Operator prerequisites
 
-For the current production release 3.0.1:
+For the current production release 3.0.2:
 
 * Kubernetes 1.14.8+, 1.15.7+, 1.16.0+, 1.17.0+, and 1.18.0+ (check with `kubectl version`).
 * Flannel networking v0.9.1-amd64 or later (check with `docker images | grep flannel`) *or* OpenShift SDN on OpenShift 4.3 systems.

docs-source/content/userguide/managing-domains/_index.md

@@ -13,6 +13,7 @@ description: "Important considerations for WebLogic domains in Kubernetes."
 * [About the Domain resource](#about-the-domain-resource)
 * [Managing life cycle operations](#managing-life-cycle-operations)
 * [Scaling clusters](#scaling-clusters)
+* [Log files](#log-files)
 
 #### Important considerations for WebLogic domains in Kubernetes
 
@@ -32,9 +33,10 @@ Be aware of the following important considerations for WebLogic domains running
   [WebLogic domain in Docker image protection]({{<relref "/security/domain-security/image-protection#weblogic-domain-in-docker-image-protection">}}).
   {{% /notice %}}
 
-* _Log File Locations:_ The operator can automatically override WebLogic domain and server log locations using
-  configuration overrides.  This occurs if the Domain `logHomeEnabled` field is explicitly set to `true`, or if `logHomeEnabled` isn't set
+* _Log File Locations:_ The operator can automatically override WebLogic Server, domain, and introspector log locations.
+  This occurs if the Domain `logHomeEnabled` field is explicitly set to `true`, or if `logHomeEnabled` isn't set
   and `domainHomeSourceType` is set to `PersistentVolume`.  When overriding, the log location will be the location specified by the `logHome` setting.
+  For additional log file tuning information, see [Log files](#log-files).
 
 * _Listen Address Overrides:_  The operator will automatically override all WebLogic domain default,
   SSL, admin, or custom channel listen addresses (using situational configuration overrides).  These will become `domainUID` followed by a
@@ -132,3 +134,65 @@ The operator let's you initiate scaling of clusters in various ways:
 * [Using the operator's REST APIs]({{< relref "/userguide/managing-domains/domain-lifecycle/scaling#calling-the-operators-rest-scale-api" >}})
 * [Using WLDF policies]({{< relref "/userguide/managing-domains/domain-lifecycle/scaling#using-a-wldf-policy-rule-and-script-action-to-call-the-operators-rest-scale-api" >}})
 * [Using a Prometheus action]({{< relref "/userguide/managing-domains/domain-lifecycle/scaling#using-a-prometheus-alert-action-to-call-the-operators-rest-scale-api" >}})
+
+### Log files
+
+The operator can automatically override WebLogic Server, domain, and introspector `.log` and `.out` locations.
+This occurs if the Domain `logHomeEnabled` field is explicitly set to `true`, or if `logHomeEnabled` isn't set
+and `domainHomeSourceType` is set to `PersistentVolume`.  When overriding, the log location will be the location specified by the `logHome` setting.
+
+If you want to fine tune the `.log` and `.out` rotation behavior for WebLogic Servers and domains, then
+you can update the related `Log MBean` in your WebLogic configuration. Alternatively, for WebLogic
+Servers, you can set corresponding system properties in `JAVA_OPTIONS`:
+
+- Here are some WLST offline examples for creating and accessing commonly tuned Log MBeans:
+
+  ```bash
+  # domain log
+  cd('/')
+  create(dname,'Log')
+  cd('/Log/' + dname);
+
+  # configured server log for a server named 'sname'
+  cd('/Servers/' + sname)
+  create(sname, 'Log')
+  cd('/Servers/' + sname + '/Log/' + sname)
+
+  # templated (dynamic) server log for a template named 'tname'
+  cd('/ServerTemplates/' + tname)
+  create(tname,'Log')
+  cd('/ServerTemplates/' + tname + '/Log/' + tname)
+  ```
+
+- Here is sample WLST offline code for commonly tuned Log MBean attributes:
+
+  ```bash
+  # minimum log file size before rotation in kilobytes
+  set('FileMinSize', 1000)
+
+  # maximum number of rotated files
+  set('FileCount', 10)
+
+  # set to true to rotate file every time on startup (instead of append)
+  set('RotateLogOnStartup', 'true')
+  ```
+
+- Here are the defaults for commonly tuned Log MBean attributes:
+
+  | Log MBean Attribute | Production Mode Default | Development Mode Default |
+  | --------- | ----------------------- | ------------------------ |
+  | FileMinSize (in kilobytes) | 5000 | 500 |
+  | FileCount | 100 | 7 |
+  | RotateLogOnStartup | false | true |
+
+- For WebLogic Server `.log` and `.out` files (including both dynamic and configured servers), you can alternatively
+set logging attributes using system properties that start with `weblogic.log.`
+and that end with the corresponding Log MBean attribute name. 
+
+  For example, you can include `-Dweblogic.log.FileMinSize=1000 -Dweblogic.log.FileCount=10 -Dweblogic.log.RotateLogOnStartup=true` in `domain.spec.serverPod.env.name.JAVA_OPTIONS` to set the behavior for all WebLogic Servers in your domain. For information about setting `JAVA_OPTIONS`, see [Domain resource]({{< relref "/userguide/managing-domains/domain-resource/_index.md#jvm-memory-and-java-option-environment-variables" >}}).
+
+{{% notice warning %}}
+Kubernetes stores pod logs on each of its nodes, and, depending on the Kubernetes implementation, extra steps may be necessary to limit their disk space usage.
+For more information, see [Kubernetes Logging Architecture](https://kubernetes.io/docs/concepts/cluster-administration/logging/).
+{{% /notice %}}
+

docs-source/content/userguide/managing-domains/domain-lifecycle/restarting.md

@@ -188,7 +188,7 @@ d. Update the `image` field of the Domain YAML file, specifying the new image na
      ```
      domain:
        spec:
-         image: oracle/weblogic-updated:3.0.1
+         image: oracle/weblogic-updated:3.0.2
      ```
 e. The operator will now initiate a rolling restart, which will apply the updated image, for all the servers in the domain.