Skip to content

Latest commit

 

History

History
55 lines (40 loc) · 2.28 KB

File metadata and controls

55 lines (40 loc) · 2.28 KB

Configuring the ingress type for your {HubName} operator

The {OperatorPlatformNameShort} installation form allows you to further configure your {HubName} operator ingress under Advanced configuration.

Procedure
  1. Log in to {OCP}.

  2. Navigate to menu:Operators[Installed Operators].

  3. Select your {OperatorPlatformNameShort} deployment.

  4. Select the Automation Hub tab.

  5. For new instances, click btn:[Create AutomationHub].

    1. For existing instances, you can edit the YAML view by clicking the {MoreActionsIcon} icon and then btn:[Edit AutomationHub].

  6. Click btn:[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.

Verification

After you have configured your {HubName} operator, click btn:[Create] at the bottom of the form view. {OCP} creates the pods. This may take a few minutes.

You can view the progress by navigating to menu:Workloads[Pods] and locating the newly created instance.

Verify that the following operator pods provided by the {PlatformNameShort} Operator installation from {HubName} are running:

Operator manager controllers {ControllerNameStart} {HubNameStart}

The operator manager controllers for each of the 3 operators, include the following:

  • automation-controller-operator-controller-manager

  • automation-hub-operator-controller-manager

  • resource-operator-controller-manager

After deploying {ControllerName}, you will see the addition of these pods:

  • controller

  • controller-postgres

After deploying {HubName}, you will see the addition of these pods:

  • hub-api

  • hub-content

  • hub-postgres

  • hub-redis

  • hub-worker

Note

A missing pod can indicate the need for a pull secret. Pull secrets are required for protected or private image registries. See Using image pull secrets for more information. You can diagnose this issue further by running oc describe pod <pod-name> to see if there is an ImagePullBackOff error on that pod.