Merge pull request #714 from oracle/develop-server-lifecle-site-doc-pod-obsolete-fix

Develop server lifecle site doc pod obsolete fix

Author: rjeberhard

model/src/main/java/oracle/kubernetes/weblogic/domain/v2/ServerPod.java

@@ -104,7 +104,7 @@ class ServerPod {
   private List<V1VolumeMount> volumeMounts = new ArrayList<>();
 
   /**
-   * The labels to be attached to pods.
+   * The labels to be attached to pods. The label names must not start with 'weblogic.'.
    *
    * @since 2.0
    */
@@ -120,7 +120,7 @@ class ServerPod {
   private Map<String, String> podAnnotations = new HashMap<>();
 
   /**
-   * The labels to be attached to Service.
+   * The labels to be attached to Service. The label names must not start with 'weblogic.'.
    *
    * @since 2.0
    */

site/server-lifecycle.md

@@ -131,7 +131,7 @@ The `restartVersion` property on the domain resource lets you force the operator
 The operator runtime does rolling restarts of clustered servers so that service is maintained.
 
 ### Properties that cause servers to be restarted
-The operator will restart servers when any of the follow properties on the domain resource that affect the server, are changed:
+The operator will restart servers when any of the follow properties on the domain resource that affect the server are changed:
 * `annotations`
 * `containerSecurityContext`
 * `domainHome`
@@ -145,16 +145,15 @@ The operator will restart servers when any of the follow properties on the domai
 * `logHomeEnabled`
 * `logHome`
 * `livenessProbe`
+* `nodeSelector`
 * `podSecurityContext`
 * `readinessProbe`
+* `resources`
 * `restartVersion`
 * `serverStartState`
 * `volumes`
 * `volumeMounts`
 
-**Note**: The operator does not restart affected servers when `nodeSelector` or `resources` is changed on the domain resource.
-In these cases, you can use `restartVersion` to force the operator to restart the servers.
-
 ### Rolling restarts
 
 Clustered servers that need to be restarted are gradually restarted (for example, `rolling restarted`) so that the cluster is not taken out of service and in-flight work can be migrated to other servers in the cluster.