Ingress NGINX - Code Overview ¶
This document provides an overview of Ingress NGINX code.
Core Golang code ¶
This part of the code is responsible for the main logic of Ingress NGINX. It contains all the logics that parses Ingress Objects, annotations, watches Endpoints and turn them into usable nginx.conf configuration.
Core Sync Logics: ¶
Ingress-nginx has an internal model of the ingresses, secrets and endpoints in a given cluster. It maintains two copies of that:
- One copy is the currently running configuration model
- Second copy is the one generated in response to some changes in the cluster
The sync logic diffs the two models and if there's a change it tries to converge the running configuration to the new one.
There are static and dynamic configuration changes.
All endpoints and certificate changes are handled dynamically by posting the payload to an internal NGINX endpoint that is handled by Lua.
The following parts of the code can be found:
main package is responsible for starting ingress-nginx program, which can be found in cmd/nginx directory.
Is the package of the code responsible for adding
version subcommand, and can be found in version directory.
Internal code ¶
This part of the code contains the internal logics that compose Ingress NGINX Controller, and it's split into:
Admission Controller ¶
Contains the code of Kubernetes Admission Controller which validates the syntax of ingress objects before accepting it.
This code can be found in internal/admission/controller directory.
File functions ¶
Contains auxiliary codes that deal with files, such as generating the SHA1 checksum of a file, or creating required directories.
This code can be found in internal/file directory.
Ingress functions ¶
Contains all the logics from Ingress-Nginx Controller, with some examples being:
- Expected Golang structures that will be used in templates and other parts of the code - internal/ingress/types.go.
- supported annotations and its parsing logics - internal/ingress/annotations.
- reconciliation loops and logics - internal/ingress/controller
- defaults - define the default struct - internal/ingress/defaults.
- Error interface and types implementation - internal/ingress/errors
- Metrics collectors for Prometheus exporting - internal/ingress/metric.
- Resolver - Extracts information from a controller - internal/ingress/resolver.
- Ingress Object status publisher - internal/ingress/status.
And other parts of the code that will be written in this document in a future.
K8s functions ¶
Contains helper functions for parsing Kubernetes objects.
This part of the code can be found in internal/k8s directory.
Networking functions ¶
Contains helper functions for networking, such as IPv4 and IPv6 parsing, SSL certificate parsing, etc.
This part of the code can be found in internal/net directory.
NGINX functions ¶
Contains helper function to deal with NGINX, such as verify if it's running and reading it's configuration file parts.
This part of the code can be found in internal/nginx directory.
Tasks / Queue ¶
Contains the functions responsible for the sync queue part of the controller.
This part of the code can be found in internal/task directory.
Other parts of internal ¶
Other parts of internal code might not be covered here, like runtime and watch but they can be added in a future.
E2E Test ¶
The e2e tests code is in test directory.
Other programs ¶
waitshutdown and cover the hack scripts.
kubectl plugin ¶
It contains kubectl plugin for inspecting your ingress-nginx deployments. This part of code can be found in cmd/plugin directory Detail functions flow and available flow can be found in kubectl-plugin
Deploy files ¶
This directory contains the
yaml deploy files used as examples or references in the docs to deploy Ingress NGINX and other components.
Those files are in deploy directory.
Helm Chart ¶
Used to generate the Helm chart published.
Code is in charts/ingress-nginx.
The documentation used to generate the website https://kubernetes.github.io/ingress-nginx/
Container Images ¶
Container images used to run ingress-nginx, or to build the final image.
Base Images ¶
Dockerfiles and scripts used to build base images that are used in other parts of the repo. They are present in images repo. Some examples: * nginx - The base NGINX image ingress-nginx uses is not a vanilla NGINX. It bundles many libraries together and it is a job in itself to maintain that and keep things up-to-date. * custom-error-pages - Used on the custom error page examples.
There are other images inside this directory.
Ingress Controller Image ¶
The image used to build the final ingress controller, used in deploy scripts and Helm charts.
This is NGINX with some Lua enhancement. We do dynamic certificate, endpoints handling, canary traffic split, custom load balancing etc at this component. One can also add new functionalities using Lua plugin system.
The files are in rootfs directory and contains:
- The Dockerfile
- nginx config
Ingress NGINX Lua Scripts ¶
Ingress NGINX uses Lua Scripts to enable features like hot reloading, rate limiting and monitoring. Some are written using the OpenResty helper.
The directory containing Lua scripts is rootfs/etc/nginx/lua.
Nginx Go template file ¶
One of the functions of Ingress NGINX is to turn Ingress objects into nginx.conf file.
To do so, the final step is to apply those configurations in nginx.tmpl turning it into a final nginx.conf file.