nginx ingress controller

We have hosted the application nginx ingress controller in order to run this application in our online workstations with Wine or directly.

Quick description about nginx ingress controller:

ingress-nginx is an Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer. It is built around the Kubernetes Ingress resource, using a ConfigMap to store the NGINX configuration. The goal of this Ingress controller is the assembly of a configuration file (nginx.conf). The main implication of this requirement is the need to reload NGINX after any change in the configuration file. Though it is important to note that we don't reload Nginx on changes that impact only an upstream configuration (i.e Endpoints change when you deploy your app). We use lua-nginx-module to achieve this. Check below to learn more about how it's done. Usually, a Kubernetes Controller utilizes the synchronization loop pattern to check if the desired state in the controller is updated or a change is required. To this purpose, we need to build a model using different objects from the cluster, in particular (in no special order) Ingresses, Services, Endpoints, Secrets, and Configmaps.

Features:

• Create a list of NGINX Servers
• Create a list of NGINX Upstreams
• Annotations are applied to all the paths in the Ingress
• Multiple Ingresses can define different annotations
• The goal of this Ingress controller is the assembly of a configuration file
• Order Ingress rules by CreationTimestamp field, i.e., old rules first

Programming Language: Go.
Categories: