Use Runbook Automation when Enterprise Only

Author: fdevans

docs/manual/projects/resource-model-sources/aws-eks.md

@@ -3,13 +3,13 @@
 ::: enterprise
 :::
 
-The AWS EKS (Elastic Kubernetes Service) Resource Model Source allows you to import your EKS clusters as nodes within Rundeck. This enables you to manage and execute jobs on your Kubernetes clusters directly from Rundeck.
+The AWS EKS (Elastic Kubernetes Service) Resource Model Source allows you to import your EKS clusters as nodes within Runbook Automation. This enables you to manage and execute jobs on your Kubernetes clusters directly from Runbook Automation.
 
 ### Configuration
 
 To configure the AWS EKS Resource Model Source:
 
-1. In your Rundeck project, go to "Project Settings" > "Edit Nodes".
+1. In your project, go to "Project Settings" > "Edit Nodes".
 2. Click "Add a new Node Source".
 3. Select "AWS EKS Clusters" from the list of available node sources.
 4. Configure the following settings:
@@ -39,9 +39,9 @@ Each EKS cluster will be represented as a node with the following attributes:
 
 If you encounter issues:
 
-1. Check the Rundeck logs for any error messages.
+1. Check the logs for any error messages.
 2. Verify your AWS credentials and permissions.
 3. Ensure your EKS cluster is running and accessible.
-4. Check network connectivity between Rundeck and your AWS resources.
+4. Check network connectivity between Runbook Automation and your AWS resources.
 
 For more detailed information, refer to the [AWS EKS documentation](https://docs.aws.amazon.com/eks/latest/userguide/what-is-eks.html)

docs/manual/projects/resource-model-sources/azure-aks.md

@@ -3,13 +3,13 @@
 ::: enterprise
 :::
 
-The Azure AKS (Azure Kubernetes Service) Resource Model Source allows you to import your AKS clusters as nodes within Rundeck. This plugin provides node source functionality for managing and executing jobs on your Azure Kubernetes clusters directly from Rundeck.
+The Azure AKS (Azure Kubernetes Service) Resource Model Source allows you to import your AKS clusters as nodes within Runbook Automation. This plugin provides node source functionality for managing and executing jobs on your Azure Kubernetes clusters directly from Runbook Automation.
 
 ### Configuration
 
 To configure the Azure AKS Resource Model Source:
 
-1. In your Rundeck project, go to "Project Settings" > "Edit Nodes".
+1. In your project, go to "Project Settings" > "Edit Nodes".
 2. Click "Add a new Node Source".
 3. Select "Azure Kubernetes Clusters" from the list of available node sources.
 4. Configure the following settings:

docs/manual/projects/resource-model-sources/gcp-gke.md

@@ -3,13 +3,13 @@
 ::: enterprise
 :::
 
-The GCP GKE (Google Kubernetes Engine) Resource Model Source allows you to import your GKE clusters as nodes within Rundeck. This plugin provides node source functionality for managing and executing jobs on your Google Cloud Platform Kubernetes clusters directly from Rundeck.
+The GCP GKE (Google Kubernetes Engine) Resource Model Source allows you to import your GKE clusters as nodes within Runbook Automation. This plugin provides node source functionality for managing and executing jobs on your Google Cloud Platform Kubernetes clusters directly from Runbook Automation.
 
 ### Configuration
 
 To configure the GCP GKE Resource Model Source:
 
-1. In your Rundeck project, go to "Project Settings" > "Edit Nodes".
+1. In your project, go to "Project Settings" > "Edit Nodes".
 2. Click "Add a new Node Source".
 3. Select "GCP Kubernetes Engine Clusters" from the list of available node sources.
 4. Configure the following settings:
@@ -49,18 +49,18 @@ Each GKE cluster will be represented as a node with the following attributes:
 The plugin supports two authentication modes:
 
 1. **GCP API Authentication**: Default mode when `Use Pod Service Account` is set to `false`. Uses GCP credentials for authentication.
-2. **Pod Service Account**: When set to `true`, uses the Kubernetes service account of the pod for authentication. Ideal when Rundeck is running within the same cluster.
+2. **Pod Service Account**: When set to `true`, uses the Kubernetes service account of the pod for authentication. Ideal when Runbook Automation is running within the same cluster.
 
 ### Troubleshooting
 
 If you encounter issues:
 
-1. Check the Rundeck logs for any error messages.
+1. Check the Runbook Automation logs for any error messages.
 2. Verify your GCP credentials and permissions:
 - Ensure the service account has the necessary GKE permissions
 - Verify the credentials file is properly stored in Key Storage
 3. Ensure your GKE cluster is running and accessible.
-4. Check network connectivity between Rundeck and your GCP resources.
+4. Check network connectivity between Runbook Automation and your GCP resources.
 5. Verify the correct Project ID and Region/Zone settings.
 
 ### Additional Resources