Ingress NGINX

Preparatory steps

Review the system requirements of the add-on to make sure you have enough resources to install it.
(Optional) Perform manual scaling of worker node groups or set up automatic scaling.

Installing add-on

Several installation options are available for the add-on.

Standard installation

Installation on dedicated worker nodes

Quick installation

Install the add-on:
Management console
Terraform
Go to VK Cloud management console.

Select project, where the cluster will be placed.

Go to Containers → Kubernetes clusters.

Click on the name of the required cluster.

Go to Addons tab.

If there are already installed add-ons in the cluster, click on the Add addon button.

Click the Install addon button on the ingress-nginx add-on card.

Edit if necessary:

application name;

the name of the namespace where the add-on will be installed;

add-on settings code.

Click the Install addon button.

The installation of the add-on in the cluster will begin. This process can take a long time.

Install Terraform and configure the environment if it is not already done.

Create a Terraform configuration file with data about the add-on being installed in the vkcs_kubernetes_addon block:

Get list of add-ons available for installation.

Get the add-on settings from the configuration_values parameter using the data source vcs_kubernetes_addon.

(Optional) To dynamically change the add-on parameters (for example, via CI), add the add-on settings to a separate yaml file. Use the templatefile function to add the required values.

Example of specifying an add-on

Check the Terraform configuration file for correctness:

terraform validate

Check out the planned changes:

terraform plan

Apply the changes:

terraform apply
Get the IP address of the load balancer.

Editing add-on settings code during installation

Changing the load balancer type for the Ingress controller

When installing an add-on with default parameters, a load balancer with a floating IP address is created, and the Ingress controller will be accessible from the Internet.

To prevent the Ingress controller from being accessible from the Internet, specify an annotation according to which an internal load balancer will be created:


---service:  annotations:    {      "loadbalancer.openstack.org/proxy-protocol": "true",      "service.beta.kubernetes.io/openstack-internal-load-balancer": "true",    }

After editing the add-on code continue installing the add-on.

Prohibition of deleting an Ingress controller node by the Autoscaler module

The Autoscaler module automatically scales the cluster: it adds nodes when the load increases, and removes when it decreases. To prevent a module from deleting the node on which the add-on is running, you need to specify a ban on deletion in the pod annotation:


controller:  podAnnotations:    cluster-autoscaler.kubernetes.io/safe-to-evict: "false"

After editing the add-on code continue installing the add-on.

Getting the IP address of the load balancer

Kubernetes Dashboard

kubectl

Connect to the cluster using Kubernetes Dashboard.
In the drop-down list next to the left of the search bar, select a namespace ingress-nginx.
Go to Service → Services.
Find in the list of services ingress-nginx-controller type LoadBalancer.

The External Endpoints column will display the floating IP address assigned to the load balancer.

Was this article helpful?

Table of Contents
Preparatory steps
Installing add-on
Editing add-on settings code during installation
Getting the IP address of the load balancer
Was this article helpful?