Adding an additional ingress controller to an ARO cluster

Prerequisites

• an Azure Red Hat OpenShift cluster
• a DNS zone that you can easily modify

Get Started

1. Create some environment variables

2. Create a certificate for the ingress controller

3. Create a secret for the certificate

4. Create an ingress controller

   NOTE: By default the ingress controller is created with external scope. This means that the corresponding Azure Load Balancer will have a public frontend IP. If you wish to deploy a privately visible ingress controller add the following lines to the spec:

   spec:
     ...
     endpointPublishingStrategy:
       loadBalancer:
         scope: Internal
       type: LoadBalancerService
     ...
   

5. Wait a few moments then get the EXTERNAL-IP of the new ingress controller

   In case of an Externally (publicly) scoped ingress controller the output should look like:

   In case of an Internal (private) one:

6. Optionally verify in the Azure portal or using CLI that the Load Balancer Service has gotten the new Frontend IP and two Load Balancing Rules - one for port 80 and another one for port 443. In case of an Internally scoped Ingress Controller the changes are to be observed within the Load Balancer that has the -internal suffix.

7. Create a wildcard DNS record pointing at the EXTERNAL-IP

8. Test that the Ingress is working

   NOTE: For the Internal ingress controller, make sure that the test host has the necessary reachability to the VPC/subnet as well as the DNS resolver.

9. Create a new project to deploy an application to

10. Create a new application

11. Expose

12. Verify it works