4.1.1 Installing the NGINX Ingress Controller

OKE allows you to use several open source ingress controllers available on Kubernetes. In this document, we will test the nginx-ingress-controller, which is used the most and is described as an example in the OKE document.

• Official documentation

  • https://docs.oracle.com/en-us/iaas/Content/ContEng/Tasks/contengsettingupingresscontroller.htm
  • https://kubernetes.github.io/ingress-nginx/deploy/#oracle-cloud-infrastructure

• installed version

  • As of the OKE document, the NGINX Ingress Controller for Kubernetes document is based on the latest version, v1.1.3. This document is based on the latest version, v1.1.3, which supports Kubernetes 1.23, 1.22, 1.21, 1.20, and 1.19.
  • Supported version of NGINX Ingress Controller
    • https://github.com/kubernetes/ingress-nginx#support-versions-table

• installed version

  • As of February 2023, OKE supports Kubernetes 1.23, 1.24, and 1.25.

  • As of February 2023, Supported version of NGINX Ingress Controller

    • https://github.com/kubernetes/ingress-nginx#support-versions-table

      Ingress-NGINX version	k8s supported version	Alpine Version	Nginx Version
      v1.6.4	1.26, 1.25, 1.24, 1.23	3.17.0	1.21.6
      v1.5.1	1.25, 1.24, 1.23	3.16.2	1.21.6
      v1.4.0	1.25, 1.24, 1.23, 1.22	3.16.2	1.19.10†
      v1.3.1	1.24, 1.23, 1.22, 1.21, 1.20	3.16.2	1.19.10†

  • Kubernetes 1.23, 1.24, 1.25 모두를 지원하는 버전 중 가장 최신 버전인 v1.6.4로 설치하겠습니다.

  • v1.4.0, v1.5.1, v1.6.4 support Kubernetes 1.23, 1.24, and 1.25. The latest version will be installed.

Install NGINX Ingress Controller

Install Ingress Controller

1. Connect to Cloud Shell or work environment where kubectl can be used.

2. Install NGINX Cloud Deployment with the following command

   kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.6.4/deploy/static/provider/cloud/deploy.yaml
   

3. Check the installation

   You can see that it is installed in the ingress-nginx namespace as shown below.

   oke_admin@cloudshell:~ (ap-seoul-1)$ kubectl get all -n ingress-nginx
   NAME                                            READY   STATUS      RESTARTS   AGE
   pod/ingress-nginx-admission-create-x74zf        0/1     Completed   0          65s
   pod/ingress-nginx-admission-patch-f8x5k         0/1     Completed   0          65s
   pod/ingress-nginx-controller-69db7f75b4-vb84p   1/1     Running     0          65s
   
   NAME                                         TYPE           CLUSTER-IP     EXTERNAL-IP       PORT(S)                      AGE
   service/ingress-nginx-controller             LoadBalancer   10.96.212.64   132.226.225.240   80:31975/TCP,443:31756/TCP   65s
   service/ingress-nginx-controller-admission   ClusterIP      10.96.95.133   <none>            443/TCP                      65s
   
   NAME                                       READY   UP-TO-DATE   AVAILABLE   AGE
   deployment.apps/ingress-nginx-controller   1/1     1            1           65s
   
   NAME                                                  DESIRED   CURRENT   READY   AGE
   replicaset.apps/ingress-nginx-controller-69db7f75b4   1         1         1       65s
   
   NAME                                       COMPLETIONS   DURATION   AGE
   job.batch/ingress-nginx-admission-create   1/1           2s         65s
   job.batch/ingress-nginx-admission-patch    1/1           2s         65s
   

Check Load Balancer IP

1. Check EXTERNAL-IP, which is the load balancer IP of the Ingress Controller service.

   oke_admin@cloudshell:~ (ap-seoul-1)$ kubectl get svc -n ingress-nginx
   NAME                                 TYPE           CLUSTER-IP     EXTERNAL-IP       PORT(S)                      AGE
   ingress-nginx-controller             LoadBalancer   10.96.212.64   132.226.225.240   80:31975/TCP,443:31756/TCP   5m31s