Minor lc doc updates (#2295)

Tom Barnes · rjeberhard · web-flow · commit 79b8a3b5ed13 · 2021-04-06T10:27:47.000-04:00
* minor life-cycle doc updates

* Backport doc changes

Co-authored-by: Ryan Eberhard &lt;ryan.eberhard@oracle.com&gt;
diff --git a/documentation/3.2/content/userguide/managing-domains/domain-lifecycle/introspection.md b/documentation/3.2/content/userguide/managing-domains/domain-lifecycle/introspection.md
@@ -6,6 +6,15 @@ weight: 5
 description: "This document describes domain introspection in the Oracle WebLogic Server in Kubernetes environment."
 ---
 
+#### Contents
+
+- [Overview](#overview)
+- [When introspection occurs automatically](#when-introspection-occurs-automatically)
+- [Initiating introspection](#initiating-introspection)
+- [Failed introspection](#failed-introspection)
+- [Introspection use cases](#introspection-use-cases)
+
+#### Overview
 
 This document describes domain introspection, when it occurs automatically, and how and when to initiate additional introspections of the domain configuration in the Oracle WebLogic Server in Kubernetes environment.
 
@@ -76,9 +85,11 @@ when `spec.logHome` is configured and `spec.logHomeEnabled` is true.
 
 ### Introspection use cases
 
-#### Adding clusters or Managed Servers to the WebLogic domain configuration
+The following sections describe typical use cases for rerunning the introspector.
+
+#### Adding clusters or Managed Servers to a Domain in PV configuration
 
-When you have an existing WebLogic domain home on a persistent volume ("Domain in PV") and you currently have WebLogic Server instances running, it is now possible to define new WebLogic clusters or Managed Servers in the domain configuration and start these new instances without affecting the life cycle of any WebLogic Server instances that are already running.
+When you have an existing WebLogic domain home on a persistent volume (Domain in PV) and you currently have WebLogic Server instances running, it is now possible to define new WebLogic clusters or Managed Servers in the domain configuration and start these new instances without affecting the life cycle of any WebLogic Server instances that are already running.
 
 Prior to operator 3.0.0, this was not possible because there was no mechanism to initiate introspection other than a full domain shut down and restart and so the operator was unaware of the new clusters or Managed Servers. Now, after updating the domain configuration, you can initiate introspection by changing the `introspectVersion`.
 
@@ -123,3 +134,7 @@ Alternately, you can set `overrideDistributionStrategy` to ON_RESTART, which mea
 
 {{% notice note %}} Changes to configuration overrides distributed to running WebLogic Server instances can only take effect if the corresponding WebLogic configuration MBean attribute is "dynamic". For instance, the Data Source "passwordEncrypted" attribute is dynamic while the "Url" attribute is non-dynamic.
 {{% /notice %}}
+
+#### Distributing changes to running Model in Image domains
+
+The operator supports rerunning the introspector in order to propagate [model updates]({{<relref "/userguide/managing-domains/model-in-image/runtime-updates.md">}}) to a running Model in Image domain.
diff --git a/documentation/3.2/content/userguide/managing-domains/model-in-image/runtime-updates.md b/documentation/3.2/content/userguide/managing-domains/model-in-image/runtime-updates.md
@@ -756,7 +756,7 @@ _Here are some of the expected WebLogic pod labels after an online update succes
      * Each WebLogic Server pod's `weblogic.introspectVersion` label will match `domain.spec.introspectVersion` after it is rolled.
      * The domain status `Available` condition will have a `Status` of `True` after the roll completes.
    * Actions required:
-     * If you want the non-dynamic changes to take effect, then restart the pod(s) with the `weblogic.configChangesPendingRestart=true` label (such as by initiating a domain roll).
+     * None. All changes will complete after the operator initiated domain roll completes.
      * See [Online update handling of non-dynamic WebLogic configuration changes](#online-update-handling-of-non-dynamic-weblogic-configuration-changes).
 
 1. _Changing any of the domain resource [fields that cause servers to be restarted]({{< relref "/userguide/managing-domains/domain-lifecycle/startup/_index.md#fields-that-cause-servers-to-be-restarted" >}}) in addition to `domain.spec.introspectVersion`, `spec.configuration.secrets`, `spec.configuration.model.onlineUpdate`, or `spec.configuration.model.configMap`._
@@ -872,7 +872,7 @@ apply offline configuration changes to a running domain is by altering the Domai
 `spec.restartVersion`. Similarly, an [online update](#online-updates) is initiated by altering
 the Domain `spec.introspectVersion`. Here are some common ways to alter either of these fields:
 
- - You can alter `restartVersion` interactively using `kubectl edit -n MY_NAMESPACE domain MY_DOMAINUID`.
+ - You can alter `restartVersion` or `introspectVersion` interactively using `kubectl edit -n MY_NAMESPACE domain MY_DOMAINUID`.
 
  - If you have your domain's resource file, then you can alter this file and call `kubectl apply -f` on the file.
 
@@ -919,8 +919,9 @@ the Domain `spec.introspectVersion`. Here are some common ways to alter either o
    ```
 
  - You can use a WebLogic Server Kubernetes Operator sample script that invokes
-   the same commands that are described in the previous bulleted item. See
-   `patch-restart-version.sh` and `patch-introspect-version.sh` in
-   the
-   `kubernetes/samples/scripts/create-weblogic-domain/model-in-image/utils/`
-   Model in Image sample directory.
+   the same commands that are described in the previous bulleted item.
+   - See `patch-restart-version.sh` and `patch-introspect-version.sh` in
+     the `kubernetes/samples/scripts/create-weblogic-domain/model-in-image/utils/`
+     directory.
+   - Or, see the more advanced `introspectDomain.sh` and `rollDomain.sh` among
+     the [Domain lifecycle sample scripts]({{< relref "/samples/simple/domains/lifecycle/_index.md">}}).
diff --git a/documentation/3.2/content/userguide/managing-operators/installation/_index.md b/documentation/3.2/content/userguide/managing-operators/installation/_index.md
@@ -14,7 +14,7 @@ and uninstall the operator.
  - [Install the operator Helm chart](#install-the-operator-helm-chart)
  - [Alternatively, install the operator Helm chart from the GitHub chart repository](#alternatively-install-the-operator-helm-chart-from-the-github-chart-repository)
  - [Upgrade the operator](#upgrade-the-operator)
- - [Remove the operator](#remove-the-operator)
+ - [Uninstall the operator](#uninstall-the-operator)
 
 #### Install the operator Helm chart
 
diff --git a/documentation/staging/content/userguide/managing-domains/domain-lifecycle/introspection.md b/documentation/staging/content/userguide/managing-domains/domain-lifecycle/introspection.md
@@ -6,6 +6,15 @@ weight: 5
 description: "This document describes domain introspection in the Oracle WebLogic Server in Kubernetes environment."
 ---
 
+#### Contents
+
+- [Overview](#overview)
+- [When introspection occurs automatically](#when-introspection-occurs-automatically)
+- [Initiating introspection](#initiating-introspection)
+- [Failed introspection](#failed-introspection)
+- [Introspection use cases](#introspection-use-cases)
+
+#### Overview
 
 This document describes domain introspection, when it occurs automatically, and how and when to initiate additional introspections of the domain configuration in the Oracle WebLogic Server in Kubernetes environment.
 
@@ -76,9 +85,11 @@ when `spec.logHome` is configured and `spec.logHomeEnabled` is true.
 
 ### Introspection use cases
 
-#### Adding clusters or Managed Servers to the WebLogic domain configuration
+The following sections describe typical use cases for rerunning the introspector.
+
+#### Adding clusters or Managed Servers to a Domain in PV configuration
 
-When you have an existing WebLogic domain home on a persistent volume ("Domain in PV") and you currently have WebLogic Server instances running, it is now possible to define new WebLogic clusters or Managed Servers in the domain configuration and start these new instances without affecting the life cycle of any WebLogic Server instances that are already running.
+When you have an existing WebLogic domain home on a persistent volume (Domain in PV) and you currently have WebLogic Server instances running, it is now possible to define new WebLogic clusters or Managed Servers in the domain configuration and start these new instances without affecting the life cycle of any WebLogic Server instances that are already running.
 
 Prior to operator 3.0.0, this was not possible because there was no mechanism to initiate introspection other than a full domain shut down and restart and so the operator was unaware of the new clusters or Managed Servers. Now, after updating the domain configuration, you can initiate introspection by changing the `introspectVersion`.
 
@@ -123,3 +134,7 @@ Alternately, you can set `overrideDistributionStrategy` to ON_RESTART, which mea
 
 {{% notice note %}} Changes to configuration overrides distributed to running WebLogic Server instances can only take effect if the corresponding WebLogic configuration MBean attribute is "dynamic". For instance, the Data Source "passwordEncrypted" attribute is dynamic while the "Url" attribute is non-dynamic.
 {{% /notice %}}
+
+#### Distributing changes to running Model in Image domains
+
+The operator supports rerunning the introspector in order to propagate [model updates]({{<relref "/userguide/managing-domains/model-in-image/runtime-updates.md">}}) to a running Model in Image domain.
diff --git a/documentation/staging/content/userguide/managing-domains/model-in-image/runtime-updates.md b/documentation/staging/content/userguide/managing-domains/model-in-image/runtime-updates.md
@@ -756,7 +756,7 @@ _Here are some of the expected WebLogic pod labels after an online update succes
      * Each WebLogic Server pod's `weblogic.introspectVersion` label will match `domain.spec.introspectVersion` after it is rolled.
      * The domain status `Available` condition will have a `Status` of `True` after the roll completes.
    * Actions required:
-     * If you want the non-dynamic changes to take effect, then restart the pod(s) with the `weblogic.configChangesPendingRestart=true` label (such as by initiating a domain roll).
+     * None. All changes will complete after the operator initiated domain roll completes.
      * See [Online update handling of non-dynamic WebLogic configuration changes](#online-update-handling-of-non-dynamic-weblogic-configuration-changes).
 
 1. _Changing any of the domain resource [fields that cause servers to be restarted]({{< relref "/userguide/managing-domains/domain-lifecycle/startup/_index.md#fields-that-cause-servers-to-be-restarted" >}}) in addition to `domain.spec.introspectVersion`, `spec.configuration.secrets`, `spec.configuration.model.onlineUpdate`, or `spec.configuration.model.configMap`._
@@ -872,7 +872,7 @@ apply offline configuration changes to a running domain is by altering the Domai
 `spec.restartVersion`. Similarly, an [online update](#online-updates) is initiated by altering
 the Domain `spec.introspectVersion`. Here are some common ways to alter either of these fields:
 
- - You can alter `restartVersion` interactively using `kubectl edit -n MY_NAMESPACE domain MY_DOMAINUID`.
+ - You can alter `restartVersion` or `introspectVersion` interactively using `kubectl edit -n MY_NAMESPACE domain MY_DOMAINUID`.
 
  - If you have your domain's resource file, then you can alter this file and call `kubectl apply -f` on the file.
 
@@ -919,8 +919,9 @@ the Domain `spec.introspectVersion`. Here are some common ways to alter either o
    ```
 
  - You can use a WebLogic Server Kubernetes Operator sample script that invokes
-   the same commands that are described in the previous bulleted item. See
-   `patch-restart-version.sh` and `patch-introspect-version.sh` in
-   the
-   `kubernetes/samples/scripts/create-weblogic-domain/model-in-image/utils/`
-   Model in Image sample directory.
+   the same commands that are described in the previous bulleted item.
+   - See `patch-restart-version.sh` and `patch-introspect-version.sh` in
+     the `kubernetes/samples/scripts/create-weblogic-domain/model-in-image/utils/`
+     directory.
+   - Or, see the more advanced `introspectDomain.sh` and `rollDomain.sh` among
+     the [Domain lifecycle sample scripts]({{< relref "/samples/simple/domains/lifecycle/_index.md">}}).
diff --git a/documentation/staging/content/userguide/managing-operators/installation/_index.md b/documentation/staging/content/userguide/managing-operators/installation/_index.md
@@ -14,7 +14,7 @@ and uninstall the operator.
  - [Install the operator Helm chart](#install-the-operator-helm-chart)
  - [Alternatively, install the operator Helm chart from the GitHub chart repository](#alternatively-install-the-operator-helm-chart-from-the-github-chart-repository)
  - [Upgrade the operator](#upgrade-the-operator)
- - [Remove the operator](#remove-the-operator)
+ - [Uninstall the operator](#uninstall-the-operator)
 
 #### Install the operator Helm chart
 
