November#

November 2#

Instances and volumes can now be exported without stopping VMs. Import is now up to 3x faster and export 2x faster thanks to a comprehensive optimization. Furthermore, these operations have been modified as follows:
- during import, you can specify a name for a template being created;
- during export, newly created files are saved in a separate directory in the selected bucket in the object storage. The directory name includes a prefix you specify and an export task ID.
The Kubernetes Clusters service supports Kubernetes 1.22.3.
When creating a Kubernetes cluster, you can assign subnets to host pods and services. Subnet addresses can be viewed in the Information tab on the cluster page.

The API methods for import/export have been modified to remove outdated parameters from response messages and to change IDs of some tasks. For more information about the response format, see the documentation.

The Get Settings button on the VPN connection page is only active when the connection is Available.
When you go back to the previous step in the Kubernetes cluster creation wizard, the selected subnet is remembered.
When creating a Kubernetes cluster, the specified name is now checked for uniqueness.
When deleting multiple resources at the same time, confirm and cancel buttons are available, regardless of the selected scale of the web page.
When uploading multiple objects into a bucket, confirm and cancel buttons are available, regardless of the selected scale of the web page.
The Volume size parameter in the Information tab on the volume page now has a tooltip saying “Volume size cannot be decreased”.
Databases and Kubernetes clusters are deleted along with the project.

When creating a high-availability Kubernetes cluster, subnets are checked to see if they belong to different availability zones.

User data can now be changed after the Kubernetes cluster has been created. In particular, this allows for automatic execution of new scripts when you launch additional nodes to scale the cluster.

Spaces are ignored when searching for resources in tables.
The values of RAM and CCUs in the instance table in the Tariff subsection of Billing section is rounded to the nearest tenth.
The database cluster page remains available even if you delete a VM with a cluster node. This allows you to delete a cluster that is in a non-consistent state.