Quotas and limits

Quotas are the restrictions applied to the project:

• for the use of virtual computing resources of the platform;
• to create objects in specific services.

For example, the available quotas are checked when a new virtual machine is created. If the quotas allow you to create another virtual machine, and there are enough resources (vCPU, memory and disk space) to create it, the virtual machine is successfully created.

Quotas are not shared between several projects of the same owner and are not inherited by one project from another. The list of quotas varies for different regions.

After activating the services, basic quotas become available to the project. They have default values that apply to all new projects in the region.

Quotas can be viewed in personal account (short list) and via the OpenStack CLI (extended list). There are implicit quotas that cannot be seen in any way, they manifest themselves as error messages when trying to create a new object. An example of an implicit quota is quota for the number of projects, which can be created by a single user.

Quotas are closely related to technical limits.

Technical limits are the limitations of the platform due to the features of the VK Cloud architecture.

Some of the limits are strict, they cannot be exceeded physically. For example, the limit on 4 GPUs per instance is related to the limitation of KVM technology, which does not allow connecting more than 4 video cards to one virtual machine.

Other limits are not related to physical limitations and are based on the operational requirements of the services. For example, network restrictions are introduced to ensure optimal network performance and stable operation.

There are no corresponding quotas for some technical limits.

Quotas can be increased within the technical limits by contacting technical support.

Non-rigid limits can be exceeded — either also through technical support, or independently. However, exceeding these limits can negatively affect the stability of work.

The following is a list of quotas and limits for the Moscow region.

The limit on the number of instances in the project can be exceeded if the corresponding quota is increased upon request to technical support.

Limits on the number of processors (vCPU and High-Freq vCPU) and RAM are associated with the limitations of standard hypervisors. If you need more vCPUs or High-Freq vCPUs, contact technical support and order a dedicated hypervisor with the necessary characteristics.

The limit on 4 GPUs per instance is related to the limitation of KVM technology, which does not allow connecting more than 4 video cards to one virtual machine.

There are no quotas for the Cloud Containers service. The use of this service is limited only by technical limits.

Non-rigid limits can be exceeded without contacting technical support. Recommendations for these and other parameters in official Kubernetes documentation. The limit on the number of nodes in a node group is not due to the requirements of Kubernetes, the limit is introduced at the VK Cloud level.

Quotas for the total volume of disks in the project take into account all types of disks, including High-IOPS SSDs. Quotas for the total volume of High-IOPS SSD disks take into account disks created in both availability zones. If you request through technical support an increase in the quota included in another quota, the quota of a higher level will be increased proportionally.

Quotas for the total number of disks in the project take into account all types of disks, including High-IOPS SSDs. Quotas for the total number of High-IOPS SSD disks take into account disks created in both availability zones. If you request through technical support an increase in the quota included in another quota, the quota of a higher level will be increased proportionally.

The limit on the number of disks per instance (28 pcs.) is associated with PCI bus limitations.

The limit on the size of one image (500 GB) is a hard limit for the Glance service. If you need to download a larger image, use the instruction.

The limit on the size of one SSD-HIGH-IOPS disk (5 TB) is due to operational requirements, it can be exceeded without contacting technical support. A disk created over the limit is no different in performance, but restoring or migrating such a disk will take considerable time and will involve risks.

The limit on the total volume of images (2 TB) can be exceeded by contacting technical support.

The limit on the number of disks snapshots (200 pcs.) can be exceeded by contacting technical support.

Quota for the number of file storage networks (NFS / CIFS file storage networks) is a quota for internal use.

The limits in this section are determined by the requirements of operation, they are used to ensure the stable operation of networks. It is not recommended to request quotas exceeding the corresponding limits via technical support.

Even if the quota for the total number of subnets in the project has been increased through technical support, it is not recommended to create more than 20 subnets in one network.

You can exceed the limit on the number of balancing rules per load balancer (10 pcs.) without contacting technical support. To do this, create rules using the OpenStack CLI. For stable operation, it is not recommended to use more than 30 rules per load balancer.

The quota Neutron balancers, which is displayed in VK Cloud personal account, is not used.

The limit on the backup size (320 TB) is due to the limit on the file size in the Object Storage service (S3), this service is used to store backups. This limit can be increased by contacting technical support.

There are no quotas for the Cloud Storage service. The use of these services is limited only by technical limits.

The rate limits can be increased by contacting technical support.