Chapter 3. Configuring Red Hat Ansible Automation Platform components on Red Hat Ansible Automation Platform Operator

Procedure

1. Log in to Red Hat OpenShift Container Platform.
2. Go to Operators Installed Operators.
3. Select your Ansible Automation Platform Operator deployment.
4. Select the Automation Controller tab.

5. For new instances, click Create AutomationController.

   1. For existing instances, you can edit the YAML view by clicking the ⋮ icon and then Edit AutomationController.

6. Click advanced Configuration. Under Image Pull Policy, click on the radio button to select

   • Always
   • Never
   • IfNotPresent

7. To display the option under Image Pull Secrets, click the arrow.

   1. Click + beside Add Image Pull Secret and enter a value.

8. To display fields under the Web container resource requirements drop-down list, click the arrow.

   1. Under Limits, and Requests, enter values for CPU cores, Memory, and Storage.

9. To display fields under the Task container resource requirements drop-down list, click the arrow.

   1. Under Limits, and Requests, enter values for CPU cores, Memory, and Storage.

10. To display fields under the EE Control Plane container resource requirements drop-down list, click the arrow.

    1. Under Limits, and Requests, enter values for CPU cores, Memory, and Storage.

11. To display fields under the PostgreSQL init container resource requirements (when using a managed service) drop-down list, click the arrow.

    1. Under Limits, and Requests, enter values for CPU cores, Memory, and Storage.

12. To display fields under the Redis container resource requirements drop-down list, click the arrow.

    1. Under Limits, and Requests, enter values for CPU cores, Memory, and Storage.

13. To display fields under the PostgreSQL container resource requirements (when using a managed instance)* drop-down list, click the arrow.

    1. Under Limits, and Requests, enter values for CPU cores, Memory, and Storage.

14. To display the PostgreSQL container storage requirements (when using a managed instance) drop-down list, click the arrow.

    1. Under Limits, and Requests, enter values for CPU cores, Memory, and Storage.
15. Under Replicas, enter the number of instance replicas.
16. Under Remove used secrets on instance removal, select true or false. The default is false.
17. Under Preload instance with data upon creation, select true or false. The default is true.

Procedure

1. Create a secret in your Ansible Automation Platform namespace for the bundle-ca.crt file (the filename must be bundle-ca.crt):

   $ oc create secret -n aap-namespace generic bundle-ca-secret --from-file=bundle-ca.crt

2. Add the bundle_cacert_secret to the Ansible Automation Platform customer resource:

   ...
   spec:
     bundle_cacert_secret: bundle-ca-secret
   ...

   Verification

   You can verify the expected certificate by running:

   oc exec -it deployment.apps/aap-gateway - openssl x509 -in /etc/pki/tls/certs/bundle-ca.crt -noout -text

Procedure

1. Log in to Red Hat OpenShift Container Platform.
2. Navigate to Operators Installed Operators.
3. Select your Ansible Automation Platform Operator deployment.
4. Select the Automation Controller tab.

5. For new instances, click Create AutomationController.

   1. For existing instances, you can edit the YAML view by clicking the ⋮ icon and then Edit AutomationController.
6. Click Advanced configuration.
7. Under Ingress type, click the drop-down menu and select Route.
8. Under Route DNS host, enter a common host name that the route answers to.
9. Under Route TLS termination mechanism, click the drop-down menu and select Edge or Passthrough. For most instances Edge should be selected.
10. Under Route TLS credential secret, click the drop-down menu and select a secret from the list.
11. Under Enable persistence for /var/lib/projects directory select either true or false by moving the slider.

Procedure

1. Log in to Red Hat OpenShift Container Platform.
2. Navigate to Operators Installed Operators.
3. Select your Ansible Automation Platform Operator deployment.
4. Select the Automation Controller tab.

5. For new instances, click Create AutomationController.

   1. For existing instances, you can edit the YAML view by clicking the ⋮ icon and then Edit AutomationController.
6. Click Advanced configuration.
7. Under Ingress type, click the drop-down menu and select Ingress.
8. Under Ingress annotations, enter any annotations to add to the ingress.
9. Under Ingress TLS secret, click the drop-down menu and select a secret from the list.

Procedure

1. Log in to Red Hat OpenShift Container Platform.
2. Navigate to Operators Installed Operators.
3. Select your Ansible Automation Platform Operator deployment.
4. Select the Automation Hub tab.

5. For new instances, click Create AutomationHub.

   1. For existing instances, you can edit the YAML view by clicking the ⋮ icon and then Edit AutomationHub.
6. Click Advanced configuration.
7. Under Ingress type, click the drop-down menu and select Route.
8. Under Route DNS host, enter a common host name that the route answers to.
9. Under Route TLS termination mechanism, click the drop-down menu and select Edge or Passthrough.
10. Under Route TLS credential secret, click the drop-down menu and select a secret from the list.

Procedure

1. Log in to Red Hat OpenShift Container Platform.
2. Navigate to Operators Installed Operators.
3. Select your Ansible Automation Platform Operator deployment.
4. Select the Automation Hub tab.

5. For new instances, click Create AutomationHub.

   1. For existing instances, you can edit the YAML view by clicking the ⋮ icon and then Edit AutomationHub.
6. Click Advanced Configuration.
7. Under Ingress type, click the drop-down menu and select Ingress.
8. Under Ingress annotations, enter any annotations to add to the ingress.
9. Under Ingress TLS secret, click the drop-down menu and select a secret from the list.

Procedure

1. Check if the extension is available on the PostgreSQL server (automation hub database).

   $ psql -d <automation hub database> -c "SELECT * FROM pg_available_extensions WHERE name='hstore'"

2. Where the default value for <automation hub database> is automationhub.

   Example output with hstore available:

   name  | default_version | installed_version |comment
   ------+-----------------+-------------------+---------------------------------------------------
    hstore | 1.7           |                   | data type for storing sets of (key, value) pairs
   (1 row)

   Example output with hstore not available:

    name | default_version | installed_version | comment
   ------+-----------------+-------------------+---------
   (0 rows)

3. On a RHEL based server, the hstore extension is included in the postgresql-contrib RPM package, which is not installed automatically when installing the PostgreSQL server RPM package.

   To install the RPM package, use the following command:

   dnf install postgresql-contrib

4. Load the hstore PostgreSQL extension into the automation hub database with the following command:

   $ psql -d <automation hub database> -c "CREATE EXTENSION hstore;"

   In the following output, the installed_version field lists the hstore extension used, indicating that hstore is enabled.

   name | default_version | installed_version | comment
   -----+-----------------+-------------------+------------------------------------------------------
   hstore  |     1.7      |       1.7         | data type for storing sets of (key, value) pairs
   (1 row)