AWX Complete Installation on Kubernetes (Ansible Tower): Prerequisites and Basic Configuration
In this video, you'll discover how to install and perform your very first actions on AWX, the free and open-source successor to Ansible Tower. AWX is the community version of Red Hat Ansible Automation Platform (AAP) and allows you to add a web interface, centralized credential management, task scheduling, and role-based access control to your Ansible automation engine.
I'll show you how to set up this powerful tool in a Kubernetes infrastructure. Get ready to dive into installing this complex system!
👉 Download the complete installation procedure (a quick reference guide in text format): https://drive.google.com/file/d/1w7oC...
__________________
Summary - Key Points & Timestamps
Here is the installation process and basic configurations (allow several tens of minutes for setup):
00:00 Introduction
Presentation of AWX, its role compared to Ansible, and its positioning in the enterprise world (equivalent to CentOS for RHEL).
02:22 Prerequisites and Technical Context
Understanding the installation via the Kubernetes Operator.
Requires a basic understanding of Kubernetes and debugging commands (kubectl get pods, kubectl describe).
System requirements: persistent storage (working NFS share) and resources (8 GB RAM minimum, 16 GB recommended, 2 to 4 CPU cores).
05:48 Step 1 - Installing the AWX Operator
Two-step installation: Operator then the AWX instance itself.
Clone the operator's Git repository and create the awx namespace.
Installation via `make deploy` or a manual approach using `kustomization.yaml` to control the version.
Points to consider regarding Docker image tags on quay.io.
08:54 Manual Approach
If the `make deploy` command doesn't work, or if you prefer a manual approach for better version control.
13:39 Step 2 - Configuring Storage (StorageClass)
Importance of a StorageClass for the PostgreSQL database.
Using Helm to install the nfs-subdir-external-provisioner and create the default StorageClass (nfs-awx-storage).
16:37 Step 3 - Deploying the AWX Instance
Creating the AWX Custom Resource in the awx-instance.yaml file.
Configuring the service type as NodePort for easy access in a test environment.
The operator automatically provisions an internal PostgreSQL and Redis instance.
19:49 Step 4 - Verifying the Deployment
Monitoring the creation of the pods (kubectl get pods -n awx -w).
Verifying that the web, task, and postgres pods are in a Running state (deployment may take some time).
22:02 Step 5 - Accessing the AWX Web Interface
Retrieving the initial admin user password via a Kubernetes secret.
Determining the NodePort assigned by Kubernetes (kubectl get svc -n awx).
Connecting to the interface via http://YOUR_NODE_IP_ADDRESS:PORT.
26:03 Conclusion and First Steps
Overview of the next logical steps in the interface: creating Projects (for Git Playbooks), Inventories, Credentials (for Git and SSH), Users/Teams, and finally Job Templates.
__________________
Best practice tip: create a new administrator account and keep the original admin account as a backup.
Remember that you can install it on a small cluster, such as a microkube, for testing and proof-of-concept projects.
__________________
Resources and Links:
Containers Playlist (Kubernetes, Docker): • Gestion Multi-Cluster : La Méthode SÛRE po...
Linux Playlist: • Lister, afficher, utiliser les fichiers ma...
Ansible/Puppet Playlist (Automation): • Puppet : Créer des Facts Personnalisés (Cu...
🔗 My YouTube Channel (LJP-Infos): / ljpinfos
🔗 Subscribe to the channel: https://www.youtube.com/c/LJPInfos?su...
💖 Support the channel (Tipeee): https://fr.tipeee.com/ljp-infos