Cloud.ru Advanced adds Kubernetes 1.35 and CCE certificate rotation

Cloud.ru updated Cloud Container Engine on its Advanced platform in August 2026. The official change log lists Kubernetes 1.35 support, automated upgrades from version 1.34, DataPlane V2 availability for CCE Turbo and certificate rotation during a cluster upgrade.

What the source confirms

Cloud.ru says a rotated certificate remains valid for five years. The update also remediates several Linux-kernel privilege-escalation vulnerabilities. Operations teams should therefore treat it as a coordinated change across the control plane, networking and worker-node baseline rather than an isolated version bump.

Kubernetes support does not prove that every workload is ready. Before upgrading, verify:

• ingress controller, CSI and CNI compatibility;
• supported operator and admission-controller versions;
• Pod Security and network policies;
• metrics, logs and traces after node replacement;
• application rollback when cluster-version rollback is unavailable.

Certificate rotation is an operational dependency

Cluster certificates are easy to overlook until expiry is close. Rotation inside a controlled upgrade reduces separate maintenance steps, but clients, kubeconfig files, service accounts and external integrations still need validation.

A five-year lifetime does not remove the need for monitoring. Platform owners should expose expiry, the last rotation event and any component that still trusts an old chain.

Pilot checklist

1. Build a test cluster matching production configuration.
2. Inventory every add-on and operator version.
3. Exercise the 1.34 to 1.35 upgrade with representative workloads.
4. Rotate the certificate and reconnect administrative clients.
5. Compare connectivity and latency before and after DataPlane V2.
6. Verify alerts, audit logs and configuration backups.
7. Test a controlled node failure and application recovery.

Remaining limitations

The change log describes available capabilities but provides no independent performance benchmark. Automated upgrade eligibility depends on configuration, add-ons and support conditions. Production adoption therefore needs a pilot and a documented recovery path.

See the guides to infrastructure observability and disaster recovery planning for the surrounding operational controls.

Source: the official Cloud.ru Advanced change log.