Managed Kubernetes Applications

Last update: June 10 2026

In a Managed Kubernetes cluster, you can use applications that extend Kubernetes functionality — for example, applications that help manage traffic or collect and process logs.

You can install and delete applications using Helm and the Control panel. Currently, through the Control panel, you can:

• install and delete the Envoy Gateway application;
• delete the NGINX Ingress Controller application.

Envoy Gateway application

Envoy Gateway is a solution for managing inbound and outbound traffic in Kubernetes, built on Gateway API resources and the Envoy proxy server.

Envoy Gateway tasks:

• HTTP, HTTPS, and TCP traffic routing;
• load balancing;
• SSL and TLS connection termination;
• advanced traffic management — for example, support for canary and blue-green deployments.

Find out more in the Load balancing with Gateway API section.

Install Envoy Gateway

Control panel

To run the application, a load balancer of the Basic redundant type and a public IP address will be created. The load balancer type cannot be changed after creation. If you want to change the load balancer type or its parameters, install the application using a Helm chart.

1. Ensure that a quota for at least one public IP address is allocated in the pool.
2. In the Control panel, on the top menu, click Products and select Managed Kubernetes.
3. Open the cluster page → Applications tab.
4. In the Available for installation block, click Envoy Gateway.
5. Check the price of the load balancer and the public IP address.
6. Click Install. A new Basic redundant load balancer with a public IP address will be created. The load balancer will appear in the Control panel: on the top menu, click Products and select Cloud servers → Load balancers section → tab Load balancers.

Helm

You can install Envoy Gateway:

• without configuring parameters — the default parameter values specified in the Helm chart are used. You can view the default values using the helm inspect values oci://docker.io/envoyproxy/gateway-helm; command;
• or with parameter configuration — you configure parameters in a file and use it for installation.

Without parameter configuration

1. Connect to the cluster.

2. Install the Helm package manager Helm.

3. Install Envoy Gateway:

   helm upgrade --install eg --create-namespace oci://docker.io/envoyproxy/gateway-helm --version v1.6.3 -n envoy-gateway-system

4. Ensure that Envoy Gateway is installed:

   kubectl get pods -n envoy-gateway-system

   Information about Envoy Gateway will appear in the response:

   NAME                              READY   STATUS    RESTARTS   AGE
   envoy-gateway-8545855df8-vjqtf    1/1     Running   0          35s

With parameter configuration

1. Connect to the cluster.

2. Install the Helm package manager Helm.

3. Get the default values for the envoyproxy/gateway-helm Helm chart and save them to the envoy-gateway-values.yaml file:

   helm inspect values oci://docker.io/envoyproxy/gateway-helm --version v1.6.3 > envoy-gateway-values.yaml

4. In the envoy-gateway-values.yaml file, configure the necessary parameters and save the changes.

5. Install Envoy Gateway:

   helm upgrade --install eg --create-namespace oci://docker.io/envoyproxy/gateway-helm --version v1.6.3 -n envoy-gateway-system --values envoy-gateway-values.yaml

6. Ensure that Envoy Gateway is installed:

   kubectl get pods

   Information about Envoy Gateway will appear in the response. For example:

   NAME                              READY   STATUS    RESTARTS   AGE
   envoy-gateway-8545855df8-vjqtf    1/1     Running   0          35s

Delete Envoy Gateway

Control panel

1. In the Control panel, on the top menu, click Products and select Managed Kubernetes.
2. Open the cluster page → Applications tab.
3. In the Installed applications block, in the application row, click .
4. Enter the cluster name to confirm deletion.
5. Click Delete.

Helm

1. Connect to the cluster.

2. Delete the application:

   helm uninstall eg

NGINX Ingress Controller application

NGINX Ingress Controller is an Ingress controller for NGINX that routes incoming traffic at the application level (L7). The Ingress Controller uses rules from Ingress for routing. Read more about NGINX Ingress Controller in the About section of the NGINX Ingress Controller documentation.

Support for NGINX Ingress Controller has been discontinued, but it continues to work. To reduce vulnerability risks, we recommend switching to Gateway API, for example, to Envoy Gateway. Read more in the example of migrating from NGINX Ingress to Envoy Gateway.

After migration, you can delete NGINX Ingress Controller.

Delete NGINX Ingress Controller

Control panel

1. In the Control panel, on the top menu, click Products and select Managed Kubernetes.
2. Open the cluster page → Applications tab.
3. In the Installed applications block, in the application row, click .
4. Enter the cluster name to confirm deletion.
5. Click Delete. The public IP address and load balancer will be deleted along with the application.

Helm

1. Connect to the cluster.

2. Delete the application:

   helm uninstall nginx

   The public IP address and load balancer will be deleted along with the application.