From 20ad7d80f7f54c78a23815b1a30a2a6c9ed25a8d Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Sun, 17 Nov 2024 22:19:07 -0700 Subject: [PATCH] Update Servers/Automation/Ansible/AWX/Deployment/AWX Operator.md --- Servers/Automation/Ansible/AWX/Deployment/AWX Operator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Servers/Automation/Ansible/AWX/Deployment/AWX Operator.md b/Servers/Automation/Ansible/AWX/Deployment/AWX Operator.md index d507a6c..f605511 100644 --- a/Servers/Automation/Ansible/AWX/Deployment/AWX Operator.md +++ b/Servers/Automation/Ansible/AWX/Deployment/AWX Operator.md @@ -5,7 +5,7 @@ Deploying a Rancher RKE2 Cluster-based Ansible AWX Operator server. This can sc This document assumes you are running **Ubuntu Server 22.04** or later with at least 16GB of memory, 8 CPU cores, and 64GB of storage. ## Deploy Rancher RKE2 Cluster -You will need to deploy a [Rancher RKE2 Cluster](https://docs.bunny-lab.io/Docker%20%26%20Kubernetes/Servers/Kubernetes%20Clusters/Rancher%20RKE2/) on an Ubuntu Server-based virtual machine. After this phase, you can focus on the Ansible AWX-specific deployment. A single ControlPlane node is all you need to set up AWX, additional infrastructure can be added after-the-fact. +You will need to deploy a [Rancher RKE2 Cluster](https://docs.bunny-lab.io/Servers/Containerization/Kubernetes/Deployment/Rancher%20RKE2/) on an Ubuntu Server-based virtual machine. After this phase, you can focus on the Ansible AWX-specific deployment. A single ControlPlane node is all you need to set up AWX, additional infrastructure can be added after-the-fact. !!! tip "Checkpoint/Snapshot Reminder" If this is a virtual machine, after deploying the RKE2 cluster and validating it functions, now would be the best time to take a checkpoint / snapshot of the VM before moving forward, in case you need to perform rollbacks of the server(s) if you accidentally misconfigure something during deployment.