Use NGINX Ingress
This document outlines the process of implementing Nginx Ingress as an ingress solution.
Introduction
Besides CCE Ingress, Kubernetes Ingress can also be implemented using the Nginx Ingress of the Kubernetes community.
Nginx offers features such as reverse proxy and load balancing.
The Nginx Ingress Controller uses Nginx to implement reverse proxy functionality and configures forwarding rules by resolving ingress resources within the cluster.
Compared to CCE Ingress, Nginx Ingress provides more detailed and flexible rule configurations for greater adaptability.
Terminology
Nginx Ingress: Use the Nginx Ingress Controller to implement K8s ingress resources.
Nginx Ingress Controller Component: Nginx Ingress controller deployed in the CCE component management interface.
Nginx Ingress Controller Instance: The Nginx Ingress Controller component participates in both rule configuration and data forwarding. Multiple sets of components can be deployed in the cluster to achieve different traffic ingress configurations. Each set of components deployed in the cluster is referred to as an Nginx Ingress Controller instance.
Operation steps
CCE offers product capabilities. Begin by creating a nodegroup for deploying the Nginx Ingress Controller, then deploy the Nginx Ingress Controller component, and finally, create ingress resources.
Create node group
Currently, the Nginx Ingress Controller is deployed as a DaemonSet within nodegroups.
First, we need to create one nodegroup.

Install the Nginx Ingress Controller component
After creating the nodegroup, deploy the Nginx Ingress Controller component to it.

Create Nginx Ingress resources
Once that's done, create the ingress resource and wait for the resource synchronization to finish.

More parameter configuration of components
The CCE console only supports deployment parameters for some of the most critical components.
If you wish to configure more parameters, set them in the "Helm" section of the console.
The instance name of the Nginx Ingress Controller is prefixed with the ingress-class set during component deployment.

