doc updates

Author: rosemarymarano

documentation/staging/content/navigate/image.md

@@ -30,7 +30,8 @@ Auxiliary images are available for the "Model in Image" [domain location]({{< re
 - `Primary Image` - The image containing the Oracle Fusion Middleware software. It is used as the basis of all containers that run WebLogic Servers for the domain.
 - `Auxiliary Image` - The image that supplies the WebLogic Deploy Tooling software and the model files. At runtime, the auxiliary image's content is merged with the primary image's content.
 
-One primary image can be reused for hundreds of domains whereas an auxiliary image is domain-specific. When using auxiliary images,
+The primary image is the one used for running the domain and the auxiliary contains the data that defines the domain. One primary image can be
+reused for hundreds of domains whereas an auxiliary image is domain-specific. When using auxiliary images,
 the primary image contains the OS, JDK, and FMW software installations; the auxiliary image supplies the specifics for a single domain.
 
 Use the `Design View` page to create a new or use an existing (the default) `Primary Image` and,
@@ -113,6 +114,11 @@ other installers' version number fields, the best practice it to use the actual
 latest capabilities, many of which are exposed by this application.  As such, using the latest version is strongly
 recommended.
 
+{{% notice note %}} For "Model in Image" or "Domain in Image" [domain locations]({{< relref "/navigate/project-settings#choosing-a-domain-location" >}}),
+when building your primary or auxiliary image, we highly recommend using WDT 2.0 to take advantage of enhanced capabilities that reduce the chance of deploy-time errors created due to a bad model.    
+{{% /notice %}}
+
+
 #### Patch Oracle Home
 **NOTE**: This pane is relevant for `Primary Images` only. Oracle strongly recommends patching all Oracle Fusion Middleware installations with the latest Patch Set Updates (PSUs)
 and other recommended patches to ensure that the latest security fixes are applied.  This pane configures the WebLogic

documentation/staging/content/navigate/kubernetes/k8s-ingress-controller.md

@@ -115,6 +115,7 @@ by using the `Update Ingress Routes` button on the `Ingress Controller` page or
 the `Go` > `Update Ingress Routes to Domain` menu item.
 
 ### Uninstall Ingress Controller
-`Uninstall Ingress Controller` uses the `helm uninstall` command to remove all the ingress resources and uninstall the ingress controller.
-You access this action by using the `Uninstall Ingress Controller` button on the
+`Uninstall Ingress Controller` uses the `helm uninstall` command to remove all the ingress resources
+and uninstall the ingress controller. In addition, you can choose whether to also delete the corresponding namespace.
+You access these actions by using the `Uninstall Ingress Controller` button on the
 `Ingress Controller` page or the `Go` > `Uninstall Ingress Controller` menu item.

documentation/staging/content/navigate/kubernetes/k8s-weblogic-domain.md

@@ -247,6 +247,7 @@ To view the current status of the last domain deployment, use the `Get Domain St
 status, as provided by the WebLogic Kubernetes Operator.
 
 ### Undeploy Domain
-`Undeploy Domain` removes the Kubernetes custom resource for the WebLogic domain and its dependent objects in Kubernetes.
-You access this action by using the `Undeploy Domain` button on the
+`Undeploy Domain` removes the Kubernetes custom resource for the WebLogic domain and its
+dependent objects in Kubernetes. In addition, you can choose whether to also delete the corresponding namespace.
+You access these actions by using the `Undeploy Domain` button on the
 `WebLogic Domain` page or the `Go` > `Undeploy WebLogic Domain to Kubernetes` menu item.

documentation/staging/content/navigate/kubernetes/k8s-wko.md

@@ -193,7 +193,8 @@ or the value of any field in the WebLogic Kubernetes Operator section.
 ### Uninstall Operator
 
 `Uninstall Operator` uses the `helm uninstall` command to remove the WebLogic Kubernetes Operator and its associated
-resources from the Kubernetes cluster. You access this action by using the `Uninstall Operator` button on the
+resources from the Kubernetes cluster. In addition, you can choose whether to also delete the corresponding namespace.
+You access these actions by using the `Uninstall Operator` button on the
 `WebLogic Operator` page or the `Go` > `Uninstall WebLogic Kubernetes Operator` menu item.
 
 Note that if you uninstall an operator, then any domains that it is managing will continue running; however,

documentation/staging/content/release notes/_index.md

@@ -5,6 +5,14 @@ weight = 5
 pre = "<b> </b>"
 +++
 
+### Recent Changes
+
+- For "Model in Image" domains, added the ability to configure and push an auxiliary image.
+- Added these capabilities:
+   - Update and uninstall the WebLogic Kubernetes Operator
+   - Uninstall the ingress controller
+   - Undeploy the WebLogic domain
+
 ### Known Issues
 
 - When running the WKT UI application on Windows, the image builder tool (docker or podman) also must be directly executable in Windows.  For example, there is currently no support for running the WKT UI application in Windows and running podman under the Windows Subsystem for Linux (WSL2).  However, running Docker Desktop for Windows with a WSL2 backend _is_ fully supported because the `docker` command is executable directly in Windows (without having to call WSL2). If you need to use podman on Windows, then refer to the podman blog entries at https://podman.io/blogs/2021/09/06/podman-on-macs.html and https://podman.io/blogs/2020/09/02/running_windows_or_mac.html for more information about downloading, installing, and configuring the Windows Remote Client.