Update dependencies and prepare for release

Author: rjeberhard

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.2.0.
-This release was published on March 26, 2021.
+The [current release of the operator](https://github.com/oracle/weblogic-kubernetes-operator/releases) is 3.2.1.
+This release was published on April 5, 2021.
 ***
 
 # Documentation

buildDockerImage.sh

@@ -33,7 +33,7 @@ while getopts "t:" optname; do
   esac
 done
 
-IMAGE_NAME=${name:-ghcr.io/oracle/weblogic-kubernetes-operator:3.3.0}
+IMAGE_NAME=${name:-ghcr.io/oracle/weblogic-kubernetes-operator:3.2.1}
 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.3.0</version>
+        <version>3.2.1</version>
     </parent>
 
     <artifactId>buildtime-reports</artifactId>

documentation/3.2/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.2.0.
-This release was published on March 31, 2021. 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.2.1.
+This release was published on April 5, 2021. See the operator prerequisites and supported environments [here]({{< relref "/userguide/introduction/introduction#operator-prerequisites" >}}).
 
 ***
 

documentation/3.2/content/faq/namespace-management.md

@@ -45,7 +45,7 @@ elkIntegrationEnabled: false
 externalDebugHttpPort: 30999
 externalRestEnabled: false
 externalRestHttpsPort: 31001
-image: ghcr.io/oracle/weblogic-kubernetes-operator:3.2.0
+image: ghcr.io/oracle/weblogic-kubernetes-operator:3.2.1
 imagePullPolicy: IfNotPresent
 internalDebugHttpPort: 30999
 istioEnabled: false

documentation/3.2/content/quickstart/get-images.md

@@ -10,7 +10,7 @@ weight: 3
 1. Pull the operator image:
 
     ```shell
-    $ docker pull ghcr.io/oracle/weblogic-kubernetes-operator:3.2.0
+    $ docker pull ghcr.io/oracle/weblogic-kubernetes-operator:3.2.1
     ```
 
 1. Pull the Traefik ingress controller image:

documentation/3.2/content/quickstart/install.md

@@ -50,7 +50,7 @@ $ helm install traefik-operator traefik/traefik \
     ```shell
     $ helm install sample-weblogic-operator kubernetes/charts/weblogic-operator \
       --namespace sample-weblogic-operator-ns \
-      --set image=ghcr.io/oracle/weblogic-kubernetes-operator:3.2.0 \
+      --set image=ghcr.io/oracle/weblogic-kubernetes-operator:3.2.1 \
       --set serviceAccount=sample-weblogic-operator-sa \
       --set "enableClusterRoleBinding=true" \
       --set "domainNamespaceSelectionStrategy=LabelSelector" \

documentation/3.2/content/quickstart/prerequisites.md

@@ -12,5 +12,5 @@ The operator uses Helm to create and deploy the necessary resources and then run
 You should clone this repository to your local machine so that you have access to the
 various sample files mentioned throughout this guide:
 ```shell
-$ git clone --branch v3.2.0 https://github.com/oracle/weblogic-kubernetes-operator
+$ git clone --branch v3.2.1 https://github.com/oracle/weblogic-kubernetes-operator
 ```

documentation/3.2/content/release-notes.md

@@ -8,6 +8,7 @@ draft: false
 
 | Date | Version | Introduces backward incompatibilities? | Change |
 | --- | --- | --- | --- |
+| April 5, 2021 | v3.2.1 | no | Updated several dependencies, including the Oracle Linux base for the container image. |
 | March 31, 2021 | v3.2.0 | no | Online updates for dynamic changes for Model in Image, injection of the WebLogic Monitoring Exporter, other features, and a significant number of additional fixes. |
 | March 1, 2021 | v3.1.4 | no | Resolved an issue where the operator would ignore live data that was older than cached data, such as following an etcd restore and updated Kubernetes Java Client and Bouncy Castle dependencies. |
 | February 12, 2021 | v3.1.3 | no | Resolved a pair of issues related to the operator running well in very large Kubernetes clusters. |
@@ -39,6 +40,10 @@ draft: false
 
 #### Operator 3.2.0
 
+Updated several dependencies, including the Oracle Linux base for the container image.
+
+#### Operator 3.2.0
+
 ##### Features
 
 * The operator's container image is based on Oracle Linux 8.

documentation/3.2/content/samples/simple/azure-kubernetes-service/domain-on-pv.md

@@ -29,7 +29,7 @@ This sample demonstrates how to use the [Oracle WebLogic Server Kubernetes Opera
 Clone the [Oracle WebLogic Server Kubernetes Operator repository](https://github.com/oracle/weblogic-kubernetes-operator) to your machine. We will use several scripts in this repository to create a WebLogic domain. This sample was tested with v3.1.1, but should work with the latest release.
 
 ```shell
-$ git clone --branch v3.2.0 https://github.com/oracle/weblogic-kubernetes-operator.git
+$ git clone --branch v3.2.1 https://github.com/oracle/weblogic-kubernetes-operator.git
 ```
 
 {{% notice info %}} The following sections of the sample instructions will guide you, step-by-step, through the process of setting up a WebLogic cluster on AKS - remaining as close as possible to a native Kubernetes experience. This lets you understand and customize each step. If you wish to have a more automated experience that abstracts some lower level details, you can skip to the [Automation](#automation) section.