lingress

lingress = The lean ingress controller.

In contrast to the most other ingress controllers for Kubernetes, this one does not come with extreme many different features and tries to be extreme dynamic. It tries to be as lean as possible.

Topics

1. Main principles
2. Requirements
3. Setup ➡️
4. Configuration ➡️
5. Headers ➡️
6. Examples ➡️
7. Contributing ➡️
8. Code of Conduct ➡️
9. License ➡️

Main principles

1. Minimal configuration: Just one single configuration and this as short as possible; without repeating common stuff for all ingress configurations (like ensure CORS). The majority of the ingress controllers coming nowadays with other many several configurations and/or you have to define different settings for http and https.
   
   

2. Centralize standards: Settings like CORS or HSTS usually settings you want to have for your whole application. For the majority of the ingress controllers, these settings are made per ingress configuration. lingress provides the feature to centralize these settings and even force them.
   
   

3. HTTPS by default: As lingress makes no difference between http and https by default, it also forces (which is nowadays industry standards) the clients to https (if the clients comes from http).
   
   

4. Industry standards by default: Instead of always activating some industry standards or even need plugins to add them lingress, supports the important ones out of the box. See headers sections for examples.

Requirements

1. Kubernetes cluster with API v1.22.0+ (or API compatible such as k3s or OpenShift Kubernetes Engine)
2. Helm v3.0.0+

More topics

• Setup
• Configuration
• Examples
• Headers