Skip to main content
Starting in version 18.0, the AWX Operator is the preferred and recommended way to install AWX. The operator provides automated deployment, configuration, and lifecycle management for AWX on Kubernetes and OpenShift platforms.
The AWX Operator is designed for production deployments and provides enterprise-grade reliability, scalability, and high availability.

Overview

The AWX Operator is a Kubernetes operator that manages the complete lifecycle of AWX deployments. It handles:
  • Automated Deployment: Deploys all AWX components as Kubernetes resources
  • Configuration Management: Manages AWX configuration through Kubernetes Custom Resources
  • Upgrades: Automates AWX upgrades with minimal downtime
  • Scaling: Supports horizontal scaling of AWX components
  • High Availability: Enables multi-replica deployments for reliability
  • Backup & Restore: Provides mechanisms for data backup and recovery

Prerequisites

Before installing the AWX Operator, ensure you have:
A running Kubernetes (1.21+) or OpenShift cluster with:
  • Sufficient resources for AWX components (minimum 4GB RAM, 2 CPU cores)
  • A storage class for persistent volumes
  • Network access to container registries
  • LoadBalancer or Ingress capability for external access
The Kubernetes command-line tool (kubectl) or OpenShift CLI (oc) installed and configured to access your cluster.
Administrator-level permissions on the cluster to:
  • Create namespaces
  • Install Custom Resource Definitions (CRDs)
  • Create RBAC roles and bindings
  • Deploy the operator
Kustomize for customizing Kubernetes manifests. Kustomize is built into kubectl version 1.14 and later.

Installation Methods

The AWX Operator can be installed using multiple methods. Choose the one that best fits your environment:

Deploying AWX

Once the operator is installed, you can deploy an AWX instance:
1

Create AWX custom resource

Create a file named awx-instance.yaml with your AWX configuration:
awx-instance.yaml
Customize the AWX deployment by adding additional spec fields. See the AWX Operator documentation for all available options.
2

Deploy AWX

Apply the custom resource:
The operator will begin deploying AWX components.
3

Monitor the deployment

Watch the deployment progress:
The deployment typically takes 5-10 minutes. You’ll see pods for:
  • PostgreSQL database
  • AWX web interface
  • AWX task executor
  • Redis cache
4

Retrieve admin password

Once deployment is complete, retrieve the admin password:
The default admin username is admin.

Accessing AWX

After deployment, access the AWX web interface:
If you configured service_type: LoadBalancer:
Access AWX at http://<EXTERNAL-IP> in your browser.

Configuration Options

The AWX Operator supports extensive configuration through the AWX custom resource spec:
Configure CPU and memory limits:
Configure persistent storage:
Use an external PostgreSQL database:
Create the secret:
Use custom AWX or Redis images:
Configure multiple replicas for high availability:

Upgrading AWX

To upgrade AWX to a new version:
1

Update operator

First, upgrade the AWX Operator to a compatible version by updating your kustomization or Helm chart.
2

Update AWX version

Modify your AWX custom resource to specify the new version:
3

Apply changes

Apply the updated configuration:
The operator will perform a rolling upgrade with minimal downtime.
4

Monitor upgrade

Watch the upgrade process:
Always review the release notes before upgrading to understand breaking changes and migration requirements.

Backup and Restore

The AWX Operator provides built-in backup and restore capabilities:

Creating a Backup

awxbackup.yaml
Apply the backup:

Restoring from Backup

awxrestore.yaml
Apply the restore:

Troubleshooting

Check operator logs:
Common issues:
  • Insufficient RBAC permissions
  • Resource constraints
  • CRD installation failures
Check resource availability:
Common causes:
  • Insufficient cluster resources
  • Storage provisioning issues
  • Image pull failures
Verify PostgreSQL pod and service:
Check database credentials in secrets:
Verify service and ingress configuration:
Check AWX pod logs:

Additional Resources

For the most up-to-date installation instructions and configuration options, always refer to the official AWX Operator documentation.