Merge pull request #1002 from oracle/release/2.1

Version 2.1

Author: rjeberhard

README.md

@@ -21,8 +21,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 2.0.1.
-This release was published on March 4, 2019.
+The [current release of the operator](https://github.com/oracle/weblogic-kubernetes-operator/releases) is 2.1.
+This release was published on April 4, 2019.
 ***
 
 # Documentation

buildtime-reports/pom.xml

@@ -5,7 +5,7 @@
     <parent>
         <artifactId>operator-parent</artifactId>
         <groupId>oracle.kubernetes</groupId>
-        <version>2.0.1</version>
+        <version>2.1</version>
     </parent>
     <modelVersion>4.0.0</modelVersion>
 

docs-source/content/_index.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]({{< 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" >}}).
 
 ***
-The [current release of the operator](https://github.com/oracle/weblogic-kubernetes-operator/releases) is 2.0.1.
-This release was published on March 4, 2019.
+The [current release of the operator](https://github.com/oracle/weblogic-kubernetes-operator/releases) is 2.1.
+This release was published on April 4, 2019.
 ***
 
 #### Operator earlier versions

docs-source/content/developerguide/backwards-compatibility.md

@@ -5,4 +5,4 @@ draft: false
 weight: 9
 ---
 
-Starting with the 2.0 release, future operator releases must be backward compatible with respect to the domain resource schema, operator Helm chart input values, configuration overrides template, Kubernetes resources created by the operator Helm chart, Kubernetes resources created by the operator, and the operator REST interface.  We will maintain compatibility for three releases, except in the case of a clearly communicated deprecated feature, which will be maintained for one release after a replacement is available.
+Starting with the 2.0.1 release, operator releases must be backward compatible with respect to the domain resource schema, operator Helm chart input values, configuration overrides template, Kubernetes resources created by the operator Helm chart, Kubernetes resources created by the operator, and the operator REST interface.  We will maintain compatibility for three releases, except in the case of a clearly communicated deprecated feature, which will be maintained for one release after a replacement is available.

docs-source/content/developerguide/documentation.md

@@ -5,31 +5,31 @@ draft: false
 weight: 9
 ---
 
-This documentation is produced using [Hugo](http://gohugo.io).  To make an 
+This documentation is produced using [Hugo](http://gohugo.io).  To make an
 update to the documentation, follow this process:
 
-1. Clone the repository if you have not already
+1. If you have not already done so, clone the repository.
 
     ```
     git clone https://github.com/oracle/weblogic-kubernetes-operator
     ```
 
-2. Create a new branch from master
+2. Create a new branch from master.
 
     ```
     git checkout master
     git pull origin master
     git checkout -b your-branch
     ```
 
-3. Make your documentation updates by editing the source files in 
+3. Make your documentation updates by editing the source files in
 `docs-source/content`.
 {{% notice note %}}
-Make sure you only check in the changes from the `docs-source/content` area;
+Make sure you _only_ check in the changes from the `docs-source/content` area;
 do not build the site and check in the static files.
 {{% /notice %}}
 
-4. If you wish to view your changes you can run the site locally using 
+4. If you wish to view your changes, you can run the site locally using
 these commands; the site will be available on the URL shown here:
 
     ```
@@ -38,7 +38,6 @@ these commands; the site will be available on the URL shown here:
     ```
 
 5. When you are ready to submit your changes, push your branch to `origin`
-and submit a pull request. Remember to follow the guidelines in the 
+and submit a pull request. Remember to follow the guidelines in the
 [CONTRIBUTING](https://github.com/oracle/weblogic-kubernetes-operator/blob/master/CONTRIBUTING.md)
 document.
-

docs-source/content/faq/cannot-pull-image.md

@@ -6,59 +6,59 @@ draft: false
 
 > My domain will not start and I see errors like `ImagePullBackoff` or `Cannot pull image`
 
-When you see these kinds of errors it means that Kubernetes cannot find your Docker image.
-The most common causes are: 
+When you see these kinds of errors, it means that Kubernetes cannot find your Docker image.
+The most common causes are:
 
-* The `image` value in your domain resource is set incorrectly, meaning Kubernetes will be 
-  trying to pull the wrong image
-* The image requires authentication or permission in order to pull it and you have not 
-  configured Kubernetes with the necessary credentials, for example in an `imagePullSecret`
+* The `image` value in your domain resource is set incorrectly, meaning Kubernetes will be
+  trying to pull the wrong image.
+* The image requires authentication or permission in order to pull it and you have not
+  configured Kubernetes with the necessary credentials, for example in an `imagePullSecret`.
 * You built the image on a machine that is not where your `kubelet` is running and Kubernetes
-  cannot see the image, meaning you need to copy the image to the worker nodes or put it in 
-  a Docker registry that is accessible the to all of the worker nodes
+  cannot see the image, meaning you need to copy the image to the worker nodes or put it in
+  a Docker registry that is accessible the to all of the worker nodes.
 
 Let's review what happens when Kubernetes starts a pod.
 
 ![Pulling an image](/weblogic-kubernetes-operator/images/image-pull.png)
 
-The definition of the pod contains a list of container specifications.  Each container 
-specificiation contains the name (and optionally tag) of the image that should be used
+The definition of the pod contains a list of container specifications.  Each container
+specification contains the name (and optionally, tag) of the image that should be used
 to run that container.  In the example above, there is a container called `c1` which is
 configured to use the Docker image `some.registry.com/owner/domain1:1.0`.  This image
-name is in the format `registry address / owner / name : tag`, so in this case the 
-registry is `some.registry.com`, then owner is `owner`, the image name is `domain` 
-and the tag is `1.0`.  Tags are a lot like version numbers, but they are not required 
-to be numbers or to be in any particular sequence or format.  If you omit the tag, it 
+name is in the format `registry address / owner / name : tag`, so in this case the
+registry is `some.registry.com`, the owner is `owner`, the image name is `domain`
+and the tag is `1.0`.  Tags are a lot like version numbers, but they are not required
+to be numbers or to be in any particular sequence or format.  If you omit the tag, it
 is assumed to be `latest`.
 
 {{% notice note %}}
-The Docker tag `latest` is confusing - it does not actually mean the latest version of 
-the image that was created or published in the registry, it just literally means 
-whichever version the owner decided to call "latest".  Docker and Kubernetes make 
+The Docker tag `latest` is confusing - it does not actually mean the latest version of
+the image that was created or published in the registry; it just literally means
+whichever version the owner decided to call "latest".  Docker and Kubernetes make
 some assumptions about latest, and it is generally recommended to avoid using it and instead
-specify the actual version/tag that you really want. 
+specify the actual version/tag that you really want.
 {{% /notice %}}
 
-First, Kubernetes will check to see if the requested image is available in the local 
+First, Kubernetes will check to see if the requested image is available in the local
 Docker image store on whichever worker node the pod was scheduled on.  If it is there,
 then it will use that image to start the container.  If it is not there, then Kubernetes
 will attempt to pull the image from a remote Docker registry.
 
 {{% notice note %}}
-There is another setting called `imagePullPolicy` that can be used to force Kubernetes 
-to always pull the image, even if it is already present in the local Docker image 
+There is another setting called `imagePullPolicy` that can be used to force Kubernetes
+to always pull the image, even if it is already present in the local Docker image
 store.
 {{% /notice %}}
 
-If the image is available in the remote registry and it is public, that is it does not 
+If the image is available in the remote registry and it is public, that is it does not
 require authentication, then Kubernetes will pull the image to the local Docker image
-store and start the container. 
+store and start the container.
 
 #### Images that require authentication
 
 If the remote Docker registry requires authentication, then you will need to provide
 the authentication details in a Kubernetes `docker-registry` secret and tell Kubernetes
-to use that secret when pulling the image. 
+to use that secret when pulling the image.
 
 To create a secret, you can use the following command:
 
@@ -73,7 +73,7 @@ kubectl create secret docker-registry secret1 \
 
 In this command, you would replace `secret1` with the name of the secret; the `docker-server`
 is set to the registry name, without the `https://` prefix; the `docker-username`, `docker-password`
-and `docker-email` are set to match the credentials you use to authenticate to the remote 
+and `docker-email` are set to match the credentials you use to authenticate to the remote
 Docker registry; and the `namespace` must be set to the same namespace where you intend to
 use the image.
 
@@ -82,11 +82,11 @@ Some registries may need a suffix making the `docker-server` something like `som
 for example.  You will need to check with your registry provider's documentation to see if this is needed.
 {{% /notice %}}
 
-After the secret is created, you need to tell Kubernetes to use it.  This is done by adding 
-an `imagePullSecret` to your Kubernetes YAML file.  In the case of a WebLogic domain, you 
+After the secret is created, you need to tell Kubernetes to use it.  This is done by adding
+an `imagePullSecret` to your Kubernetes YAML file.  In the case of a WebLogic domain, you
 add the secret name to the `imagePullSecret` in the domain custom resource YAML file.  
 
-Here is an example of part of a domain custom resource file with the `imagePullSecret` above 
+Here is an example of part of a domain custom resource file with the `imagePullSecret` above
 specified:
 
 ```
@@ -107,7 +107,7 @@ spec:
   - name: secret1
 ```
 
-Alternatively, you can associate the secret with the service account that will be used to run 
+Alternatively, you can associate the secret with the service account that will be used to run
 the pod.  If you do this, then you will not need to add the `imagePullSecret` to the domain
 resource.  This is useful if you are running multiple domains in the same namespace.
 
@@ -121,17 +121,17 @@ kubectl patch serviceaccount default \
 ```
 
 {{% notice note %}}
-You can provide mutliple `imagePullSecrets` if you need to pull Docker images from multiple 
+You can provide mutliple `imagePullSecrets` if you need to pull Docker images from multiple
 remote Docker registries or if your images require different authentication credentials.
 For more information, see [Docker Image Protection]({{<relref "/security/domain-security/image-protection.md#weblogic-domain-in-docker-image-protection">}})
 under **Security**.
 {{% /notice %}}
 
 #### Manually copying the image to your worker nodes
 
-If you are not able to use a remote Docker registry, for example if your Kubernetes cluster is 
+If you are not able to use a remote Docker registry, for example if your Kubernetes cluster is
 in a secure network with no external access, you can manually copy the Docker images to the
-cluster instead. 
+cluster instead.
 
 On the machine where you created the image, export it into a tar file using this command:
 
@@ -149,5 +149,5 @@ docker load < domain1.tar
 #### Restart pods to clear the error
 
 After you have ensured that the images are accessible on all worker nodes, you may need to restart
-the pods so that Kubernetes will attempt to pull the images again.   You can do this by 
-deleting the pods themselves, or deleting the domain resource and then recreating it. 
+the pods so that Kubernetes will attempt to pull the images again.   You can do this by
+deleting the pods themselves, or deleting the domain resource and then recreating it.

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:2.0.1
+    $ docker pull oracle/weblogic-kubernetes-operator:2.1
     ```
 
 1. Pull the Traefik load balancer image:

docs-source/content/quickstart/install.md

@@ -57,7 +57,7 @@ $ helm install stable/traefik \
     $ helm install kubernetes/charts/weblogic-operator \
       --name sample-weblogic-operator \
       --namespace sample-weblogic-operator-ns \
-      --set image=oracle/weblogic-kubernetes-operator:2.0.1 \
+      --set image=oracle/weblogic-kubernetes-operator:2.1 \
       --set serviceAccount=sample-weblogic-operator-sa \
       --set "domainNamespaces={}" \
       --wait

docs-source/content/quickstart/prerequisites.md

@@ -11,6 +11,6 @@ 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:
-```
+```bash
 $ git clone https://github.com/oracle/weblogic-kubernetes-operator
 ```

docs-source/content/recent-changes.md

@@ -10,6 +10,7 @@ This document tracks recent changes to the operator, especially ones that introd
 
 | Date | Version | Introduces backward incompatibilities | Change |
 | --- | --- | --- | --- |
+| April 4, 2019 | v2.1 | no  | Customers can add init and sidecar containers to generated pods.  
 | 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.  
 | 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.  
 | January 16, 2019 | v2.0-rc2 | yes | Schema updates are completed, and various bugs fixed.