With the NGINX Kubernetes Ingress controller, you get basic load balancing and SSL/TLS termination for all Kubernetes Ingress resources. Important: this Add-On is only compatible with Kubernetes versions <=1.18.0.
You can find more information on ingresses and the nginx ingress controller and all of it's configuration options at:
For information on how to install and uninstall an Add-On see MetaKube Add-Ons.
The following customization options are possible:
|CPU Requests||How many milli CPUs should be reserved||100m|
|Memory Requests||How much memory should be reserved||128Mi|
|CPU Limits||What is the maximum of used milli CPUs||200m|
|Memory Limits||What is the maximum of used memory||512Mi|
|Replicas||How many replicas should be running||2|
|Use Auto Scaling||Should a HorizontalPodAutoscaler be created||false|
|Min Replicas||The minimum amount of replicas in the AutoScaler||2|
|Max Replicas||The maximum amount of replicas in the AutoScaler||4|
|Default TLS certificate||Path to a secret in the form
There are two ways to configure the NGINX Ingress Controller configuration:
You can configure values for a specific Ingress by adding annotations to the Ingress object. See Annotations for more details.
You can change the default values for all Ingress objects by adding a ConfigMap called
syseleven-ingress-nginx-ingress-controller in the
syseleven-ingress namespace. See ConfigMap for more details.
Note that after initially creating the ConfigMap you have to restart all ingress controller pods once:
kubectl rollout restart deployment syseleven-ingress-nginx-ingress-controller -n syseleven-ingress