Synchronize documentation

Author: rjeberhard

documentation/3.4/content/_index.md

@@ -23,7 +23,7 @@ You can:
 
 {{% notice tip %}}
 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/how-to-weblogic-server-on-kubernetes), or try out the [samples]({{< relref "/samples/_index.md" >}}).
-Also, you can step through the [Tutorial](https://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/hands-on-lab/README.md)
+Also, you can step through the [Tutorial](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/kubernetes/hands-on-lab/README.md)
 using the operator to deploy and run a WebLogic domain container-packaged web application on an Oracle Cloud Infrastructure Container Engine for Kubernetes (OKE) cluster.
 {{% /notice %}}
 

documentation/3.4/content/developerguide/integration-tests.md

@@ -16,7 +16,7 @@ You will need to obtain the `kube.config` file for an administrative user and ma
 $ mvn clean verify -P java-integration-tests
 ```
 
-For more detailed information, see [How to run the Java integration tests ](https://github.com/oracle/weblogic-kubernetes-operator/tree/main/integration-tests#how-to-run-the-java-integration-tests).
+For more detailed information, see [How to run the Java integration tests ](https://github.com/oracle/weblogic-kubernetes-operator/tree/{{< latestMinorVersion >}}/integration-tests#how-to-run-the-java-integration-tests).
 
 {{% notice note %}}
 When you run the integrations tests, they do a cleanup of any operator or domains on that cluster.   

documentation/3.4/content/faq/configmaps.md

@@ -16,7 +16,7 @@ In each case, the access is configured within the `serverPod` element of the des
 For example, given
 a ConfigMap named `my-map` with entries `key-1` and `key-2`, you can provide access to both values as separate files
 in the same directory within the `cluster-1` cluster with the following
-in your [Domain](https://github.com/oracle/weblogic-kubernetes-operator/blob/main/documentation/domains/Domain.md):
+in your [Domain](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/documentation/domains/Domain.md):
 
 
 ```yaml

documentation/3.4/content/faq/node-selector.md

@@ -0,0 +1,40 @@
+---
+title: "Scheduling pods to particular nodes"
+date: 2020-06-30T08:55:00-05:00
+draft: false
+weight: 14
+description: "How do I constrain scheduling WebLogic Server pods to particular nodes?"
+---
+
+> How do I constrain scheduling WebLogic Server pods to a particular set of nodes?
+
+To do this:
+
+First, set a label on the nodes on which the WebLogic Server pods will run. For example:
+```shell
+$ kubectl label nodes name=weblogic-pods
+```
+
+In the Domain CR, set a `nodeSelector`: a selector which must match a node's labels for the pod to be scheduled on that node. See `kubectl explain pods.spec.nodeSelector`.
+
+You can set `nodeSelector` labels for WebLogic Server pods, all server pods in a cluster, or all server pods in a domain. `nodeSelector` is a field under the `serverPod` element, which occurs at several points in the Domain CR [schema](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/documentation/domains/Domain.md):
+
+- At the top-level `spec.severPod` for the entire domain
+- At `spec.adminServer.serverPod` for the Administration Server
+- At `spec.clusters[*].serverPod` for each cluster
+- At `spec.managedServers[*].serverPod` for individual Managed Servers
+
+
+```yaml
+spec:
+serverPod:
+nodeSelector:
+```
+Under that level, you specify labels and values that match the labels on the nodes you want to select. For example:
+
+```yaml
+nodeSelector:
+  name: weblogic-pods
+```
+
+For more details, see [Assign Pods to Nodes](https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes/) in the Kubernetes documentation.

documentation/3.4/content/faq/oci-fss-pv.md

@@ -31,7 +31,7 @@ see [Persistent storage]({{< relref "/userguide/managing-domains/persistent-stor
 
 #### Failure during domain creation with persistent volume sample
 
-The existing sample for [creation of a domain home on persistent volume](https://github.com/oracle/weblogic-kubernetes-operator/tree/main/kubernetes/samples/scripts/create-weblogic-domain/domain-home-on-pv)
+The existing sample for [creation of a domain home on persistent volume](https://github.com/oracle/weblogic-kubernetes-operator/tree/{{< latestMinorVersion >}}/kubernetes/samples/scripts/create-weblogic-domain/domain-home-on-pv)
 uses a Kubernetes Job to create the domain. The sample uses an
 `initContainers` section to change the file ownership which will
 fail for OCI FSS created volumes used with an OKE cluster.
@@ -65,7 +65,7 @@ Init Containers:
 ```
 
 #### Updating the domain on persistent volume sample
-In the following snippet of the [create-domain-job-template.yaml](https://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/scripts/create-weblogic-domain/domain-home-on-pv/create-domain-job-template.yaml),
+In the following snippet of the [create-domain-job-template.yaml](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/kubernetes/samples/scripts/create-weblogic-domain/domain-home-on-pv/create-domain-job-template.yaml),
 you can see the updated `command` for the init container:
 ```yaml
 apiVersion: batch/v1

documentation/3.4/content/faq/security-validation.md

@@ -2,7 +2,7 @@
 title: "Handling security validations"
 date: 2020-06-30T08:55:00-05:00
 draft: false
-weight: 14
+weight: 15
 description: "Why am I seeing these security warnings?"
 ---
 

documentation/3.4/content/faq/volumes.md

@@ -34,7 +34,7 @@ spec:
 ```
 
 To provide access to this claim to all Managed Servers in the `cluster-1` cluster, specify the following
-in your [Domain](https://github.com/oracle/weblogic-kubernetes-operator/blob/main/documentation/domains/Domain.md):
+in your [Domain](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/documentation/domains/Domain.md):
 
 ```yaml
   clusters:

documentation/3.4/content/quickstart/cleanup.md

@@ -14,7 +14,7 @@ weight: 7
     $ helm uninstall sample-domain1-ingress -n sample-domain1-ns
     ```
 
-1.	Remove the Kubernetes resources associated with the domain by using the sample [`delete-weblogic-domain-resources`](http://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/scripts/delete-domain/delete-weblogic-domain-resources.sh) script:
+1.	Remove the Kubernetes resources associated with the domain by using the sample [`delete-weblogic-domain-resources`](http://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/kubernetes/samples/scripts/delete-domain/delete-weblogic-domain-resources.sh) script:
 
     ```shell
     $ kubernetes/samples/scripts/delete-domain/delete-weblogic-domain-resources.sh -d sample-domain1

documentation/3.4/content/quickstart/create-domain.md

@@ -11,7 +11,7 @@ weight: 6
    * Select a user name and password, following the required rules for password creation (at least 8 alphanumeric characters with at least one number or special character).
    * Pick or create a directory to which you can write output.
 
-1. Create a Kubernetes Secret for the WebLogic domain administrator credentials containing the `username` and `password` for the domain, using the [create-weblogic-credentials](http://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/scripts/create-weblogic-domain-credentials/create-weblogic-credentials.sh) script:
+1. Create a Kubernetes Secret for the WebLogic domain administrator credentials containing the `username` and `password` for the domain, using the [create-weblogic-credentials](http://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/kubernetes/samples/scripts/create-weblogic-domain-credentials/create-weblogic-credentials.sh) script:
 
     ```shell
     $ kubernetes/samples/scripts/create-weblogic-domain-credentials/create-weblogic-credentials.sh \
@@ -22,14 +22,14 @@ weight: 6
     with the value specified by the `-d` flag.  For example, the command above would create a secret named
     `sample-domain1-weblogic-credentials`.
 
-1.	Create a new image with a domain home, plus create a domain resource that the operator will use to deploy the image, by running the [create-domain](http://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/scripts/create-weblogic-domain/domain-home-in-image/create-domain.sh) script.
+1.	Create a new image with a domain home, plus create a domain resource that the operator will use to deploy the image, by running the [create-domain](http://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/kubernetes/samples/scripts/create-weblogic-domain/domain-home-in-image/create-domain.sh) script.
 
     The script's behavior is controlled by an inputs file plus command-line options. The script downloads the [WebLogic Image Tool](https://oracle.github.io/weblogic-image-tool/) and [WebLogic Deploy Tool](https://oracle.github.io/weblogic-deploy-tooling/) and uses these tools to create a new image with a domain home. The script also creates a domain resource YAML file that references the image, and, if the `-e` option is specified, deploys the domain resource to Kubernetes. For a detailed understanding of the steps that the `create-domain.sh` script performs for you, see the bulleted items under [Use the script to create a domain]({{< relref "/samples/domains/domain-home-in-image/#use-the-script-to-create-a-domain" >}})
 
     {{% notice note %}} The `create-domain.sh` script and its inputs file are for demonstration purposes _only_; its contents and the domain resource file that it generates for you might change without notice. In production, we strongly recommend that you use the WebLogic Image Tool and WebLogic Deploy Tooling (when applicable), and directly work with domain resource files instead.
     {{% /notice%}}
 
-    First, copy the sample [create-domain-inputs.yaml](http://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/scripts/create-weblogic-domain/domain-home-in-image/create-domain-inputs.yaml) file and update your copy with:  
+    First, copy the sample [create-domain-inputs.yaml](http://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/kubernetes/samples/scripts/create-weblogic-domain/domain-home-in-image/create-domain-inputs.yaml) file and update your copy with:  
        * `domainUID`: `sample-domain1`
        * `image`: Leave empty unless you need to tag the new image that the script builds to a different name.
           For example if you are using a remote cluster that will need to pull the image from a container registry,
@@ -74,7 +74,7 @@ weight: 6
     $ kubectl get services -n sample-domain1-ns
     ```
 
-1.	Create an ingress for the domain, in the domain namespace, by using the [sample](http://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/charts/ingress-per-domain/README.md) Helm chart:
+1.	Create an ingress for the domain, in the domain namespace, by using the [sample](http://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/kubernetes/samples/charts/ingress-per-domain/README.md) Helm chart:
 
     ```shell
     $ helm install sample-domain1-ingress kubernetes/samples/charts/ingress-per-domain \

documentation/3.4/content/quickstart/install.md

@@ -5,7 +5,7 @@ draft: false
 weight: 4
 ---
 
-#### Use Helm to install the operator and [Traefik](http://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/charts/traefik/README.md) ingress controller.
+#### Use Helm to install the operator and [Traefik](http://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/kubernetes/samples/charts/traefik/README.md) ingress controller.
 
 First, set up Helm:
 
@@ -21,7 +21,7 @@ Create a namespace for the ingress controller.
 $ kubectl create namespace traefik
 ```
 
-Use the [values.yaml](http://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/charts/traefik/values.yaml) file in the sample but set `kubernetes.namespaces` specifically.
+Use the [values.yaml](http://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/kubernetes/samples/charts/traefik/values.yaml) file in the sample but set `kubernetes.namespaces` specifically.
 
 
 ```shell