bunny-lab/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Containers/Kubernetes/Rancher RKE2/AWX Operator/Ansible Operator.md

Browse Source
This commit is contained in:
Nicole Rappe
2024-01-19 23:26:37 -07:00
parent c526cfde84
commit d9bfad4019
1 changed files with 1 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
Containers/Kubernetes/Rancher RKE2/AWX Operator/RKE2 Ansible AWX.md → Containers/Kubernetes/Rancher RKE2/AWX Operator/Ansible Operator.md
View File

@ -7,8 +7,7 @@ Deploying a Rancher RKE2 Cluster-based Ansible AWX Operator server. This can sc
![Ansible AWX WebUI](awx.png) ![Ansible AWX WebUI](awx.png)
## Deploy Rancher RKE2 Cluster ## Deploy Rancher RKE2 Cluster
You will need to follow the [Rancher RKE2 Cluster Deployment](https://docs.cyberstrawberry.net/Container%20Documentation/Kubernetes/Rancher%20RKE2/Rancher%20RKE2%20Cluster) You will need to deploy a [Rancher RKE2 Cluster](https://docs.bunny-lab.io/Containers/Kubernetes/Rancher%20RKE2/Rancher%20RKE2%20Cluster/) 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.
guide in order to initially set up the cluster itself. After this phase, you can focus on the Ansible AWX-specific aspects of the deployment. If you are only deploying AWX in a small environment, a single ControlPlane node is all you need to set up AWX.
:::tip :::tip
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. 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.