Plan your installation

Before you install automation orchestrator, review the deployment models and installation methods.

Deployment models

Automation orchestrator supports three deployment models. You choose the deployment model at installation time. You cannot change the deployment model after installation.

Ansible Automation Platform co-located deployment

Deploy automation orchestrator alongside an existing Ansible Automation Platform installation on the same OpenShift cluster. Review the system requirements for the minimum Ansible Automation Platform version. This model provides:

  • Push-button OpenID Connect (OIDC) connectivity between Automation gateway and automation orchestrator for single sign-on.
  • Shared infrastructure and simplified operations for organizations already running Ansible Automation Platform.
Independent deployment

Deploy automation orchestrator on its own cluster with its own dependent services. An Ansible Automation Platform deployment must still be available and network-reachable so that automation orchestrator can dispatch jobs to automation controller. This model is suitable for organizations that require separation between orchestration and execution infrastructure.

Air-gapped deployment

Deploy automation orchestrator in a disconnected environment with no outbound internet access. Before installation, you must mirror the required container images to an internal registry that your OpenShift cluster can reach. Air-gapped deployment supports both co-located and independent topologies.

Installation methods

Installing automation orchestrator is a two-phase process:

  1. Install the operator. The automation orchestrator operator manages the lifecycle of the application on your OpenShift cluster. You must install the operator before you can deploy automation orchestrator.
  2. Create an AutomationOrchestrator custom resource. After the operator is running, create a custom resource to deploy the application and its components.

You can install the operator by using any of the following methods:

OpenShift CLI

Use oc commands to create the Operator Lifecycle Manager (OLM) Subscription and install the operator manually. This is the supported installation method for production deployments. Choose this method for CLI-based provisioning workflows.

OpenShift web console

Install the operator from OperatorHub in the OpenShift web console. This is a supported installation method for production deployments. Choose this method for a graphical installation experience.

aapctl (Technology Preview)

Use the aapctl companion CLI to install the operator and configure the deployment in one step. aapctl generates all required Kubernetes resources from a single configuration file and supports GitOps workflows through manifest generation.

Important:

aapctl is a Technology Preview feature. Technology Preview features provide early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process. Technology Preview features are not fully supported under Red Hat production SLA and may not be functionally complete. Red Hat does not recommend using Technology Preview features in production. For more information, see Technology Preview Features Support Scope in the Additional resources section.