16 posts tagged with "release"

This release keeps a resource that is being deleted visible, paginates the lists of instances and disks, and lists the subnets of a whole project in a single call. It also protects the system disk of a running VM, and refuses upfront a disk that the project's storage quota cannot hold. The additions remove nothing from the existing contract.

Behaviour change: a deleted resource no longer disappears from the API immediately. It stays readable with the status deleting until it is actually removed (see Changed).

The console accompanies API v1.6.4. A deleted resource stays displayed until its deletion is complete, and a VM's system disk is changed from a dedicated view. A VM stuck while starting can now be stopped, and the dashboard's topology map loads faster.

This release tells you why a resource is not ready, through the new statusDetail field, and gives the state of a Kubernetes cluster's control plane. Each service announces its default preset. It also fixes the addition of SSH keys on a Windows VM, which replaced its password, and the rotation of a bucket user's credentials. The additions remove nothing from the existing contract.

Behaviour change: rotating the password of a MariaDB or RabbitMQ user is now refused, because it was never applied (see Security).

The console accompanies API v1.6.3 with a Control plane card on a Kubernetes cluster's page, whose control plane size and number of replicas can now be changed. The pages of the five databases share a single layout, and several creation and edit forms are fixed.

This patch release brings back the VM Instances page, which could fail to display since v1.4.2.

This release improves the API's internal request tracking, which helps us analyse an incident or a support request faster. The API behaves exactly as before, and no action is required on your side.

This maintenance release updates the console's components to fix security vulnerabilities. It brings no visible change.

The API now applies rate limits per API key and per IP address. All its errors, authentication refusals included, follow the same format with requestId and code, and every response carries a request identifier. This version also fixes a security issue that requires no action on your part.

The API opens to automation tools with API keys, and gains a backup and restore service for PostgreSQL, MariaDB, VMs and disks, including point-in-time restore for PostgreSQL. Managed databases can be restarted, and a VM now returns its internal address and its public address separately. PATCH requests become true partial updates: a field left out of the body keeps its value.

Breaking change: access with a project kubeconfig on api.hikube.cloud is removed, and that address now serves the public API (see Migration at the end of this note).

The console accompanies API v1.6.0 with a new Backups screen: destinations, schedules, on-demand backups, archives and restores of VMs, disks, and PostgreSQL and MariaDB databases. The project settings manage its API keys, managed databases can be restarted from their page, and the VM and database pages separate internal addresses from external ones.