Chapter 3. Installing and configuring automation controller on Red Hat OpenShift Container Platform web console

Procedure

1. Ensure Form view is selected. It should be selected by default.
2. Enter the name of the new controller.
3. Optional: Add any labels necessary.
4. Click Advanced configuration.
5. Enter Hostname of the instance. The hostname is optional. The default hostname will be generated based upon the deployment name you have selected.
6. Enter the Admin account username.
7. Enter the Admin email address.
8. Under the Admin password secret drop-down menu, select the secret.
9. Under Database configuration secret drop-down menu, select the secret.
10. Under Old Database configuration secret drop-down menu, select the secret.
11. Under Secret key secret drop-down menu, select the secret.
12. Under Broadcast Websocket Secret drop-down menu, select the secret.
13. Enter any Service Account Annotations necessary.

Procedure

1. Under Image Pull Policy, click on the radio button to select

   • Always
   • Never
   • IfNotPresent

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

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

3. 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.

4. 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.

5. 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.

6. 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.

7. 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.

8. 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.

9. 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.
10. Under Replicas, enter the number of instance replicas.
11. Under Remove used secrets on instance removal, select true or false. The default is false.
12. Under Preload instance with data upon creation, select true or false. The default is true.

Procedure

1. If you do not have a ldap_cacert_secret, you can create one with the following command:

   $ oc create secret generic <resourcename>-custom-certs \
       --from-file=ldap-ca.crt=<PATH/TO/YOUR/CA/PEM/FILE>  \ 1

   1

   Modify this to point to where your CA cert is stored.

   This will create a secret that looks like this:

   $ oc get secret/mycerts -o yaml
   apiVersion: v1
   data:
     ldap-ca.crt: <mysecret> 1
   kind: Secret
   metadata:
     name: mycerts
     namespace: awx
   type: Opaque

   1

   Automation controller looks for the data field ldap-ca.crt in the specified secret when using the ldap_cacert_secret.

2. Under LDAP Certificate Authority Trust Bundle click the drop-down menu and select your ldap_cacert_secret.
3. Under LDAP Password Secret, click the drop-down menu and select a secret.
4. Under EE Images Pull Credentials Secret, click the drop-down menu and select a secret.
5. Under Bundle Cacert Secret, click the drop-down menu and select a secret.

6. Under Service Type, click the drop-down menu and select

   • ClusterIP
   • LoadBalancer
   • NodePort

Procedure

1. Click Advanced configuration.
2. Under Ingress type, click the drop-down menu and select Route.
3. Under Route DNS host, enter a common host name that the route answers to.
4. Under Route TLS termination mechanism, click the drop-down menu and select Edge or Passthrough. For most instances Edge should be selected.
5. Under Route TLS credential secret, click the drop-down menu and select a secret from the list.
6. Under Enable persistence for /var/lib/projects directory select either true or false by moving the slider.

Procedure

1. Click Advanced Configuration.
2. Under Ingress type, click the drop-down menu and select Ingress.
3. Under Ingress annotations, enter any annotations to add to the ingress.
4. Under Ingress TLS secret, click the drop-down menu and select a secret from the list.