RusHydro moves its first workloads to the centralised Botsman container platform

Botsman Platform, part of Astra Group, has reported completion of a pilot deployment at RusHydro Group. A management cluster and a production cluster are now in operation, while new workloads use a GitOps delivery approach.

Moving beyond isolated container hosts

Before the project, containers ran on individual virtual machines without a unified orchestrator. According to the announcement, this increased operating overhead and made monitoring standards, load distribution, application handover, automatic restart, and scaling harder to manage.

The team first moved a test environment for corporate distance learning and then several smaller projects. A new corporate portal was developed directly on the target platform with GitOps. This sequence reduces risk compared with using a critical system as the first migration candidate.

Integrations around the platform

The environment integrates container-image scanning, backups, monitoring, and corporate identity. A shared S3-compatible object store is planned.

Production readiness depends on failure behaviour, not merely the presence of an integration. Teams should know whether an already trusted image can start when the scanner is unavailable, how persistent volumes are restored, who owns service identities, and which control-plane events reach the central audit trail.

Measures after the pilot

• deployment frequency and duration;
• failed-release and rollback rates;
• pod and end-to-end application recovery time;
• image-scanning coverage before admission;
• namespace and data recovery from backup;
• drift between Git and actual cluster state;
• management-plane load and availability.

The source is a vendor account of the deployment. It does not publish workload scale, target SLOs, or recovery-test results, so those properties cannot be inferred from the existence of two clusters.

Source: the official Astra Group announcement dated 21 September 2026.