How is external access organized in Managed Kubernetes?

You can configure external access to Kubernetes clusters using load balancers. They are created automatically and configured using Services of the LoadBalancer type. The load balancer will be assigned a public IP address.

You can create an Ingress controller — this will also create a load balancer.

The second way to provide external access is to create a Service of the NodePort type and connect a public IP address to one node (on the Ports tab of the server page). The connection will be made to this IP address.

3 TB of free external traffic is provided for all the projects. If you exceed this amount, the traffic will be paid for separately. Prices are provided on our website.

How do I access the Ingress controller in Managed Kubernetes?

When installing a Managed Kubernetes cluster, the Ingress Controller is not installed automatically. You can choose the Ingress controller that meets your requirements and install it.

What will be the external IP address when using Ingress? Can I make it static?

You can create a public IP address in the Control panel, and after creating an Ingress controller in the manifest for LoadBalancer, specify the created IP in the loadBalancerIP field. In this case, it will be connected to the load balancer.

All objects of this Ingress controller will use the same public IP.

Please note that a public address is a full-fledged static external IP address that is available until it is deleted.

Is it possible to fix the external IP address when creating an Ingress controller in Managed Kubernetes?

When a load balancer is deleted, the external IP address assigned to it is also automatically deleted.

If you don’t want the selected address to be deleted, use the following annotation in the manifest:

loadbalancer.openstack.org/keep-floatingip: "true"

Are there any limits on the number of open ports on a load balancer created by a Service with the LoadBalancer type?

There are no limits on the number of ports.

The limit on the number of connections is 1 000 000.

The number of requests per second (RPS) is approximately 19 500.