wrapping up last plugins

Author: jsboak

docs/.vuepress/public/assets/img/k8s-cluster-logs-output.png

@@ -4,36 +4,37 @@
 
 ## Overview
 
-This plugin allows you to view the logs of an object within a Kubernetes cluster. It is designed to work in conjunction with the AWS EKS, GCP GKE, and Azure AKS [Resource Model Source plugins](/manual/projects/resource-model-sources/)
+This plugin retrieves logs from a specific object within a Kubernetes cluster. Since this is a node-step plugin, multiple Kubernetes clusters or namespaces can be targeted within a single Job.
+
+The types of objects that can be viewed logs from within a Kubernetes cluster include:
+
+- **Pods**
 
 ## Configuration
 
-### Required Fields
+### Prerequisites
+
+Before configuring the Kubernetes Object Logs plugin, the target clusters must be added to the Runbook Automation instance and the authentication method must be configured. This is done by following the steps outlined in the [Kubernetes Plugins Overview](/manual/plugins/kubernetes-plugins-overview.md).
+
+### Add Kubernetes Object Logs Step
 
-* **Name**: The name of the object to view logs from, such as Pod name or Deployment name.
-* **Namespace**: The namespace where the object resides. Default is `default`.
+When building a Job, add the **Kubernetes / Clusters / Object Logs** node step:
 
-### Optional Fields
+![Kubernetes Object Logs](/assets/img/k8s-cluster-object-logs.png)<br>
 
+Configure the following fields:
+
+* **Name**: The name of the object to view logs from, such as Pod name.
 * **Container**: Specify a particular container to view logs from within the object.
 * **Number of Log Lines**: The number of log lines to retrieve. Default is 50.
 * **Time-span (seconds)**: A relative time in seconds before the current time from which to show logs.
 * **Follow Logs**: If selected, the plugin will follow the log output. Note that the Job may continue to run until manually stopped.
 
-## Usage
-
-1. Provide the name of the object you want to view logs from.
-2. Specify the namespace where the object is located.
-3. Optionally, specify a particular container, number of log lines, time-span, or choose to follow logs.
-
-## Authentication
-
-Kubernetes Clusters plugins operate on a per-cluster basis and authenticate in one of two ways, as configured in the [Resource Model Plugin](/manual/projects/resource-model-sources/) used to fetch the nodes. This configuration is controlled by the `Use Pod Service Account for Node Steps` option:
+### Invocation Output
 
-1. When disabled, the plugin uses the cloud provider credentials set in the resource model to retrieve the
-   kube-config for the targeted cluster.
+The output of the step will be the logs from the object in the Kubernetes cluster:
 
-2. When enabled, the [Enterprise Runner](/administration/runner/) must be placed in the cluster and uses its pod's K8s service account for authentication.
+![Kubernetes Object Logs Output](/assets/img/k8s-cluster-logs-output.png)<br>
 
 ## Notes
 

docs/.vuepress/public/assets/img/k8s-cluster-object-logs.png

@@ -4,38 +4,24 @@
 
 ## Overview
 
-This plugin allows you to execute a command in a pod within a Kubernetes cluster. It is designed to work in conjunction with the AWS EKS, GCP GKE, and Azure AKS [Resource Model Source plugins](/manual/projects/resource-model-sources/).
-## Configuration
-
-### Required Fields
-
-* **Pod Name**: The name of the pod to execute the command in.
-* **Namespace**: The namespace where the pod resides. Default is `default`.
-* **Command**: The command to execute in the pod.
+This plugin executes a command in a specified pod within a Kubernetes cluster. Since this is a node-step plugin, multiple Kubernetes clusters or namespaces can be targeted within a single Job.
 
-### Optional Fields
-
-* **Container**: Specify a particular container within the pod to execute the command in.
-* **Shell**: Specific shell to use for executing the command in the container. Default is `/bin/sh`.
-
-## Usage
+## Configuration
 
-1. Provide the name of the pod you want to execute the command in.
-2. Specify the namespace where the pod is located.
-3. Enter the command you want to execute.
-4. Optionally, specify a particular container and/or shell to use.
+### Prerequisites
 
-## Authentication
+Before configuring the Kubernetes Object Logs plugin, the target clusters must be added to the Runbook Automation instance and the authentication method must be configured. This is done by following the steps outlined in the [Kubernetes Plugins Overview](/manual/plugins/kubernetes-plugins-overview.md).
 
-Kubernetes Clusters plugins operate on a per-cluster basis and authenticate in one of two ways, as configured in the [Resource Model Plugin](/manual/projects/resource-model-sources/) used to fetch the nodes. This configuration is controlled by the `Use Pod Service Account for Node Steps` option:
+### Add Kubernetes Run Command Step
 
-1. When disabled, the plugin uses the cloud provider credentials set in the resource model to retrieve the
-   kube-config for the targeted cluster.
+When building a Job, add the **Kubernetes / Clusters / Run Command** node step:
 
-2. When enabled, the [Enterprise Runner](/administration/runner/) must be placed in the cluster and uses its pod's K8s service account for authentication.
+![Kubernetes Run Command](/assets/img/k8s-cluster-run-command.png)<br>
 
-## Notes
+Configure the following fields:
 
-- Make sure the command you're executing is available in the specified container.
-- If no specific container is specified, the command will be executed in the first container of the pod.
-- The shell option allows you to choose a different shell if the default `/bin/sh` is not available or if you need to use a different shell for specific commands.
+* **Pod Name**: The name of the pod to execute the command in.
+* **Namespace**: The namespace where the pod resides.
+* **Command**: The command to execute in the pod.
+* **Container**: (Optional) Specify a particular container within the pod to execute the command in.
+* **Shell**: Specific shell to use for executing the command in the container. Default is `/bin/sh`.

docs/.vuepress/public/assets/img/k8s-cluster-run-command.png

@@ -4,41 +4,34 @@
 
 ## Overview
 
-This plugin executes a script using a predefined container image within a Kubernetes cluster. It deploys a Kubernetes Job to run the script in a container, then deletes the Job after execution. This plugin is designed to work in conjunction with the AWS EKS, GCP GKE, and Azure AKS [Resource Model Source plugins](/manual/projects/resource-model-sources/).
+This plugin executes a script using a predefined container image within a Kubernetes cluster. It deploys a Kubernetes Job to run the script in a container, then deletes the Job after execution. Since this is a node-step plugin, multiple Kubernetes clusters or namespaces can be targeted within a single Job.
 
 ## Configuration
 
-### Required Fields
+### Prerequisites
 
-* **Script**: The script to execute in the container.
-* **Invocation Command**: The command to execute the script in the container. Default is `sh -c`.
-* **Container Image**: The container image to use for script execution. Default is `amazon/aws-cli`.
-* **Namespace**: The namespace where the Kubernetes Job will be deployed. Default is `default`.
-
-### Optional Fields
-
-* **Environment Variables**: Environment variables to pass to the container (YAML syntax).
-* **Image Pull Policy**: The image pull policy for the container. Options are "Always", "IfNotPresent", or "Never". Default is "Always".
+Before configuring the Kubernetes Run Script plugin, the target clusters must be added to the Runbook Automation instance and the authentication method must be configured. This is done by following the steps outlined in the [Kubernetes Plugins Overview](/manual/plugins/kubernetes-plugins-overview.md).
 
-## Usage
+### Add Kubernetes Run Script Step
 
-1. Enter the script you want to execute.
-2. Specify the invocation command (if different from default).
-3. Choose the container image to use.
-4. Specify the namespace for the Job deployment.
-5. Optionally, add environment variables and set the image pull policy.
+When building a Job, add the **Kubernetes / Clusters / Run Script** node step:
 
-## Authentication
+![Kubernetes Run Script](/assets/img/k8s-cluster-run-script.png)<br>
 
-Kubernetes Clusters plugins operate on a per-cluster basis and authenticate in one of two ways, as configured in the [Resource Model Plugin](/manual/projects/resource-model-sources/) used to fetch the nodes. This configuration is controlled by the `Use Pod Service Account for Node Steps` option:
+Configure the following fields:
 
-1. When disabled, the plugin uses the cloud provider credentials set in the resource model to retrieve the
-   kube-config for the targeted cluster.
-
-2. When enabled, the [Enterprise Runner](/administration/runner/) must be placed in the cluster and uses its pod's K8s service account for authentication.
+* **Script**: The script to execute in the container.
+* **Invocation Command**: The command to execute the script in the container. Default is `sh -c`.
+* **Container Image**: The container image to use for script execution. Default is `amazon/aws-cli`.
+* **Namespace**: The namespace where the Kubernetes Job will be deployed. Default is `default`.
+* **Environment Variables**: Environment variables to pass to the container (YAML syntax).
+* **Image Pull Policy**: The image pull policy for the container. Options include: 
+  * `Always`
+  * `IfNotPresent`
+  * `Never`
 
 ## Notes
 
-- The Job is automatically deleted after script execution.
+- The pod that was used to execute the script is automatically deleted after script execution.
 - Environment variables support the 'valueFrom' field for referencing secrets and other sources. See [Kubernetes Docs](https://kubernetes.io/docs/tasks/inject-data-application/define-environment-variable-container/) for detailed syntax and examples.
-- Predefined container images include options like `amazon/aws-cli`, `bitnami/kubectl`, `mcr.microsoft.com/azure-cli`, `google/cloud-sdk`, and `dtzar/helm-kubectl`, but custom images can also be specified.
+- Predefined container images include options like `amazon/aws-cli`, `bitnami/kubectl`, `mcr.microsoft.com/azure-cli`, `google/cloud-sdk`, and `dtzar/helm-kubectl`, but other images may be used.

docs/.vuepress/public/assets/img/k8s-cluster-run-script.png

@@ -4,37 +4,23 @@
 
 ## Overview
 
-This plugin updates a specified object of a selected kind within a Kubernetes cluster. It is designed to work in conjunction with the AWS EKS, GCP GKE, and Azure AKS [Resource Model Source plugins](/manual/projects/resource-model-sources/).
+This plugin updates a specified object of a selected kind within a Kubernetes cluster. Since this is a node-step plugin, multiple Kubernetes clusters or namespaces can be targeted within a single Job.
 
 ## Configuration
 
-### Required Fields
+### Prerequisites
 
-* **Object Name**: The name of the object to be updated.
-* **YAML Definition**: The YAML definition of the object to be updated.
-* **Namespace**: The namespace where the object resides. Default is `default`.
-
-### Optional Fields
-
-* **Object Type**: Select the type of object to update (e.g., Pods, Deployments, Services). Default is "Pods".
-
-## Usage
+Before configuring the Kubernetes Update Object plugin, the target clusters must be added to the Runbook Automation instance and the authentication method must be configured. This is done by following the steps outlined in the [Kubernetes Plugins Overview](/manual/plugins/kubernetes-plugins-overview.md).
 
-1. Provide the name of the object you want to update.
-2. Select the desired object type from the dropdown menu.
-3. Enter the updated YAML definition for the object.
-4. Specify the namespace where the object is located.
+### Add Kubernetes Update Object Step
 
-## Authentication
+When building a Job, add the **Kubernetes / Clusters / Update Object** node step:
 
-Kubernetes Clusters plugins operate on a per-cluster basis and authenticate in one of two ways, as configured in the [Resource Model Plugin](/manual/projects/resource-model-sources/) used to fetch the nodes. This configuration is controlled by the `Use Pod Service Account for Node Steps` option:
+![Kubernetes Update Object](/assets/img/k8s-cluster-update-object.png)<br>
 
-1. When disabled, the plugin uses the cloud provider credentials set in the resource model to retrieve the
-   kube-config for the targeted cluster.
+Configure the following fields:
 
-2. When enabled, the [Enterprise Runner](/administration/runner/) must be placed in the cluster and uses its pod's K8s service account for authentication.
-
-## Notes
-
-- The plugin uses a field manager named "runbook-automation/apply-patch" for tracking changes.
-- Ensure that the YAML definition provided is complete and correct for the object you're updating.
+* **Object Name**: The name of the object to be updated.
+* **YAML Definition**: The YAML definition of the object to be updated.
+* **Namespace**: The namespace where the object resides. Default is `default`.
+* **Object Type**: Select the type of object to update (e.g., Pods, Deployments, Services). Default is "Pods".