nicole
289769a601
Automatic Documentation Deployment / Sync Docs to https://kb.bunny-lab.io (push) Successful in 8s
2.5 KiB
2.5 KiB
tags
| tags | |||
|---|---|---|---|
|
AWX
Purpose
Follow AWX from its Kubernetes deployment through source control, inventory, credentials, and job execution. Check the environment context on older Minikube and credential examples before combining them with the operator deployment.
Includes
- Controller deployment and upgrades
- Projects, inventories, credentials, and templates
- Gitea and Windows authentication integration
Build the Controller
- Rancher RKE2 — Prepare the cluster required by the AWX Operator procedure.
- AWX Operator — Deploy the controller into the documented cluster.
- Minikube Example — Consult the separate deployment approach and its recorded assumptions.
Connect the Automation Objects
A project supplies repository content. An inventory identifies targets and variables. Credentials provide authentication, and a job template combines these objects with a playbook.
- Connect AWX to Gitea — Create the source credential, project, and inventory source together.
- Projects and Source Control — Understand the project role without maintaining a second copy of its connection settings.
- Inventory Structure — Understand host groups and variables before changing the lab inventory.
- Credential Examples — Review the recorded environment and authentication limitations.
- Job Templates — Connect the project, inventory, playbook, and credentials.
- Lab Inventory — Locate the recorded hosts and inventory groups.
Run Against Windows Targets
- Prepare Windows Targets — Configure the remote-management endpoint used by the automation examples.
- Configure AWX Kerberos — Follow the execution-environment and FQDN requirements recorded for this implementation.
- Custom WinRM Credential — Find the credential input and injector definitions.
- Playbook Catalog — Find existing repository playbooks and the catalog completeness notes.