NGINX ingress controller

Use the NGINX ingress controller when you deploy the CDM.

Remember, the CDM is a reference implementation and not for production use. When you create a project plan, you’ll need to determine which ingress controller to use in production.

After you’ve finished deploying the CDM, you can use the CDM as a sandbox to explore deployment with a different ingress controller.

To deploy an NGINX ingress controller in an EKS cluster:

Verify that you initialized your cluster by performing the steps in Kubernetes cluster creation.

If you did not set up your cluster using this technique, the cluster might be missing some required configuration.

Deploy the NGINX ingress controller in your cluster:

$ /path/to/forgeops/bin/ingress-controller-deploy.sh --eks
Deploying Ingress Controller to EKS...
namespace/nginx created
Detected cluster of type: cdm-small
Setting ingress pod count to 2
"ingress-nginx" has been added to your repositories
Release "ingress-nginx" does not exist. Installing it now.
NAME: ingress-nginx
...

Check the status of the pods in the nginx namespace until all the pods are ready:

$ kubectl get pods --namespace nginx
NAME                                       READY   STATUS    RESTARTS   AGE
ingress-nginx-controller-bb566bf7b-c9kmk   1/1     Running   0          2m45s
ingress-nginx-controller-bb566bf7b-l6dz6   1/1     Running   0          2m45s

Obtain the DNS name (shown under the EXTERNAL-IP column) of the load balancer:

$ kubectl get services --namespace nginx
NAME                                 TYPE           CLUSTER-IP     EXTERNAL-IP                                    PORT(S)                      AGE
ingress-nginx-controller             LoadBalancer   10.100.43.88   ac5f2939...ca4.elb.us-east-1.amazonaws.com   80:30005/TCP,443:30770/TCP   62s
ingress-nginx-controller-admission   ClusterIP      10.100.2.215   <none>                                         443/TCP                      62s

Wait for a couple of minutes for the load balancer to be assigned the external IP address. Then, get the external IP addresses of the load balancer. For example:
```
$ host ac5f2939...42d085.elb.us-east-1.amazonaws.com
ac5f2939...42d085.elb.us-east-1.amazonaws.com has address 3.210.123.210
```
The host command returns several IP addresses. You can use any of the IP addresses when you modify your local hosts file in the next step for evaluation purposes. You must create an appropriate entry in your DNS servers for production deployments.
Configure hostname resolution for the ingress controller:
1. Choose an FQDN (referred to as the deployment FQDN) that you’ll use when you deploy the ForgeRock Identity Platform, and when you access its GUIs and REST APIs.
  
  Examples in this documentation use cdm.example.com as the deployment FQDN. You are not required to use cdm.example.com; you can specify any FQDN you like.
2. If DNS does not resolve your deployment FQDN, add an entry similar to the following to the /etc/hosts file:
  ingress-ip-address cdm.example.com
  For ingress-ip-address, specify the ingress controller’s external IP address.

ForgeOps

NGINX ingress controller

Next step