NGINX Ingress

What is NGINX Ingress?

NGINX Ingress is a Kubernetes Ingress Controller based on NGINX and NGINX Plus. It extends ingress resources with advanced features through annotations and ConfigMap customization.

Key Features:

• Load balancing for WebSocket, gRPC, TCP, and UDP  protocols
• Standard ingress features like routing and SSL termination
• Enhanced capabilities through ConfigMap and annotations
• NGINX Original documentation for target version here

Note: Use unique ingress class names (via ingressClassName) per deployment to map and manage ingress resources effectively.

Installing or Upgrading NGINX Ingress

Collab deployments are configured to use an NGINX: nginx-internal, which acts as the second NGINX in a chain (typically receiving requests from an outer NGINX for OC components).

This instalation installs NGINX: nginx-internal.

Step 1: Fetch the Configuration files

Download the file nginx-internal.values.yml. It contains configuration values to start NGINX: nginx-internal. It is already filled with the values recommended by Collab.

Open a CommandLine or PowerShel in the folder containing nginx-internal.values.yml.

Step 2: Add the NGINX Ingress Helm Repository

1. Add the repository:

   helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx 
   helm repo update ingress-nginx
   helm upgrade --install nginx-internal ingress-nginx/ingress-nginx --version 4.10.1 --create-namespace -n nginx-internal -f nginx-internal.values.yml
   

Step 3: Verify Installation

To check if the NGINX Ingress Controller is running, use the following command:

kubectl -n nginx-internal get pod

The output should show the controller pods as Running, similar to this:

NAME                                                      READY   STATUS    RESTARTS   AGE nginx-internal-ingress-nginx-controller-b78576fc9-49hwr   1/1     Running   0          140d nginx-internal-ingress-nginx-controller-b78576fc9-9qqlw   1/1     Running   0          140d

Usage

Set the Correct ingressClassName

• Ensure the ingressClassName in your ingress manifest matches the class name configured during deployment (e.g., nginx-internal).