Chapter 7. Configuring an Ingress Controller for manual DNS Management

Procedure

1. Create a custom resource (CR) file named sample-ingress.yaml containing the following:

   apiVersion: operator.openshift.io/v1
   kind: IngressController
   metadata:
     namespace: openshift-ingress-operator
     name: <name> 

   1

   
   spec:
     domain: <domain> 

   2

   
     endpointPublishingStrategy:
       type: LoadBalancerService
       loadBalancer:
         scope: External 

   3

   
         dnsManagementPolicy: Unmanaged 

   4

   Copy to Clipboard Toggle word wrap

   1

   Specify the <name> with a name for the IngressController object.

   2

   Specify the domain based on the DNS record that was created as a prerequisite.

   3

   Specify the scope as External to expose the load balancer externally.

   4

   dnsManagementPolicy indicates if the Ingress Controller is managing the lifecycle of the wildcard DNS record associated with the load balancer. The valid values are Managed and Unmanaged. The default value is Managed.

2. Save the file to apply the changes.

   oc apply -f <name>.yaml 

   1

   Copy to Clipboard Toggle word wrap

Procedure

1. Modify the chosen IngressController to set dnsManagementPolicy:

   SCOPE=$(oc -n openshift-ingress-operator get ingresscontroller <name> -o=jsonpath="{.status.endpointPublishingStrategy.loadBalancer.scope}")
   
   oc -n openshift-ingress-operator patch ingresscontrollers/<name> --type=merge --patch='{"spec":{"endpointPublishingStrategy":{"type":"LoadBalancerService","loadBalancer":{"dnsManagementPolicy":"Unmanaged", "scope":"${SCOPE}"}}}}'

   Copy to Clipboard Toggle word wrap
2. Optional: You can delete the associated DNS record in the cloud provider.