Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
All solutions
    • All solutions for Managed Service for Kubernetes
    • Fixing the "timed out waiting for the condition" error when mounting a PVC
    • Resolving the "timed out waiting for the condition" error when mounting a volume with a large number of files
    • Hosts of the Managed Service for Kubernetes node groups stay in the Reconciling status for a long time
    • Constant restarts of the kube-dns-autoscaler pod
    • Number of nodes in the group fails to decrease
    • Resolving the "Multi-Attach error for volume" error
    • Resolving the "DEADLINE_EXCEEDED" error
    • Adding and updating Linux SSH keys on Managed Services for Kubernetes node group hosts
    • Assigning static external IP addresses for Managed Service for Kubernetes cluster nodes
    • Granting internet access to Kubernetes nodes
    • How to change the network or subnet for an MDB cluster
    • How to create an internal Ingress controller

In this article:

  • Scenario description
  • Solution
  1. Managed Kubernetes
  2. How to create an internal Ingress controller

How to create an internal Ingress controller

Written by
Yandex Cloud
Updated at November 27, 2023
  • Scenario description
  • Solution

Scenario descriptionScenario description

You need to create an internal Ingress controller.

SolutionSolution

Note

The feature of using internal controllers is in Preview: please contact support to enable it.

To ensure Ingress creates an internal controller, set up a number of parameters in the values.yaml file and use it when installing the controller via Helm Chart:

  1. Set the internal.enabled parameter value to true;
  2. Add the following annotations to the service:
yandex.cloud/load-balancer-type: internal
yandex.cloud/subnet-id: <ID of subnet from which the internal IP will be issued>
  1. Disable external controller by setting the external.enabled parameter to false.

After creating the load balancer via Helm Chart, health checks will be automatically added.

Was the article helpful?

Previous
How to change the network or subnet for an MDB cluster
Next
All solutions for Managed Service for Kubernetes
Yandex project
© 2025 Yandex.Cloud LLC