Ingress NGINX

Ingress NGINX is an Ingress controller for NGINX that balances the load between the WebSocket, gRPC, TCP, or UDP applications. Ingress NGINX is installed in a Yandex Managed Service for Kubernetes cluster and is set up using the Kubernetes ConfigMap and Ingress objects, including the annotations.

1. Configure the application:

   • Namespace: Select a namespace for Ingress NGINX or create a new one.

   • Application name: Specify the app name.

   • Number of controller replicas: Set the number of Ingress controller replicas to improve fault tolerance. If only one replica is used, then, in case of its failure, the applications deployed using the Ingress controller will be unavailable.

     The default value is 1.

   • Controller IP address: Specify a reserved IP address. You can reserve it using Yandex Virtual Private Cloud.

     If you do not fill in the field, the Ingress controller will be assigned a dynamic IP address.

   • Traffic management policy: Select a policy for external traffic management. It matches the externalTrafficPolicy parameter in the Kubernetes specifications. The possible values are:

     • Cluster: Traffic is routed to different Kubernetes nodes (default). As the result, traffic is distributed evenly; however, such an approach has some disadvantages:

       • The package may come to one node’s proxy and get rerouted to another node. Such behavior leads to delays in performing operations and sending packages.
       • The pod that receives the package sees the IP address of the proxying node rather than the one of the client. As the result, the original IP address of the client is not preserved.

     • Local: Traffic is proxied and distributed between pods on the same node. The traffic is routed to the node via the port specified in the Kubernetes Service object of the LoadBalancer or NodePort type.

       The traffic comes to a specific node, so it is distributed unevenly between nodes; however, the client IP address is preserved.

     For more information about policies for external traffic management, see the Kubernetes documentation.

2. Click Install.

3. Wait for the application to change its status to Deployed.

• Routing traffic between applications.
• Managing access to applications over HTTP, HTTPS, or gRPC.

Yandex Cloud technical support is available 24/7. The types of requests you can submit and the appropriate response time depend on your pricing plan. You can switch to the paid support plan in the management console. You can learn more about the technical support terms here.