Install the Ansible Automation Platform Operator through OperatorHub
Use this procedure to guide you through deploying the Red Hat Ansible Automation Platform Operator through the Operators section on Red Hat OpenShift Container Platform, selecting the appropriate update channel and installation mode, and then verifying the successful deployment.
Install the Red Hat Ansible Automation Platform Operator on Red Hat OpenShift Container Platform Copy linkLink copied!
When installing your Ansible Automation Platform Operator you have a choice of a namespace-scoped operator or a cluster-scoped operator. This depends on the update channel you choose, stable-2.x or cluster-scoped-2.x.
Before you begin Copy linkLink copied!
- You have installed the Red Hat Ansible Automation Platform catalog in OperatorHub.
- You have created a
StorageClassobject for your platform and a persistent volume claim (PVC) withReadWriteManyaccess mode. See Dynamic provisioning for details. See Configure static storage for Ansible Automation Platform for manual setup. - To run Red Hat OpenShift Container Platform clusters on Amazon Web Services (AWS) with
ReadWriteManyaccess mode, you must add NFS or other storage.- For information about the AWS Elastic Block Store (EBS) or to use the
aws-ebsstorage class, see Persistent storage using AWS Elastic Block Store. - To use multi-attach
ReadWriteManyaccess mode for AWS EBS, see Attaching a volume to multiple instances with Amazon EBS Multi-Attach.
- For information about the AWS Elastic Block Store (EBS) or to use the
About this task Copy linkLink copied!
A namespace-scoped operator is confined to one namespace, offering tighter security. A cluster-scoped operator spans multiple namespaces, which grants broader permissions.
If you are managing multiple Ansible Automation Platform instances with the same Ansible Automation Platform Operator version, use the cluster-scoped operator, which uses a single operator to manage all Ansible Automation Platform custom resources in your cluster.
If you need multiple operator versions in the same cluster, you must use the namespace-scoped operator. The operator and the deployment share the same namespace. This can also be helpful when debugging because the operator logs pertain to custom resources in that namespace only.
For information about the Ansible Automation Platform Operator system requirements and infrastructure topology see Operator topologies in Tested deployment models.
For help with installing a namespace or cluster-scoped operator see the following procedure.
You cannot deploy Ansible Automation Platform in the default namespace on your OpenShift Cluster. The aap namespace is recommended. You can use a custom namespace, but it should run only Ansible Automation Platform.
Procedure Copy linkLink copied!
Results Copy linkLink copied!
The installation process begins. When installation finishes, a modal appears notifying you that the Ansible Automation Platform Operator is installed in the specified namespace.
- Click to view your newly installed Ansible Automation Platform Operator and verify the following operator custom resources are present:
| Automation controller | Automation hub | Event-Driven Ansible (EDA) | Red Hat Ansible Lightspeed |
|---|---|---|---|
|
|
|
|
- Verify that the Ansible Automation Platform operator displays a Succeeded status.