Add logging to explain pod recycling

Author: russgold

operator/src/main/java/oracle/kubernetes/operator/helpers/PodStepContext.java

@@ -434,6 +434,7 @@ public NextAction apply(Packet packet) {
         logPodExists();
         return doNext(packet);
       } else {
+        LOGGER.info(MessageKeys.CYCLING_POD, currentPod, getPodModel());
         return doNext(replaceCurrentPod(getNext()), packet);
       }
     }

operator/src/main/java/oracle/kubernetes/operator/logging/MessageKeys.java

@@ -145,4 +145,5 @@ private MessageKeys() {}
   public static final String CANNOT_PARSE_INTROSPECTOR_RESULT = "WLSKO-0142";
   public static final String CANNOT_PARSE_INTROSPECTOR_FILE = "WLSKO-0143";
   public static final String CANNOT_START_DOMAIN_AFTER_MAX_RETRIES = "WLSKO-0144";
+  public static final String CYCLING_POD = "WLSKO-0145";
 }

operator/src/main/resources/Operator.properties

@@ -142,4 +142,5 @@ WLSKO-0140=Job {0} is completed with status: {1}
 WLSKO-0141=Failed to parse WebLogic Domain topology due to exception: {0}
 WLSKO-0142=Failed to parse results from domain introspector for domain {0} due to exception: {1}
 WLSKO-0143=Failed to parse file {0} from domain introspector for domain {1} due to exception: {2}
-WLSKO-0144=Unable to start domain with domainUID {0} in namespace {1} after {2} attempts due to exception: {3}
+WLSKO-0144=Unable to start domain with domainUID {0} in namespace {1} after {2} attempts due to exception: {3}
+WLSKO-0145=Replacing pod {0} with {1}