kubeblocks-op-horizontal-scale

Horizontal scaling of a KubeBlocks database cluster adjusts replica or shard counts for existing clusters. It validates the scaling request against the ops capability matrix before applying changes and performing post-change health checks.

Yes, adding read replicas and shards to an existing KubeBlocks DB cluster is supported. The operation verifies support in the ops capability matrix, routes monitoring to the observability router, and coordinates rollback if health checks fail.

If a KubeBlocks horizontal scale operation fails, the system coordinates a rollback to a clear boundary and runs health checks. It also issues diagnostics through the troubleshoot component to identify the root cause.

KubeBlocks horizontal scaling applies across supported engines and configurations. The Skill validates each scaling request against the ops capability matrix to confirm whether the target engine supports the requested replica or shard changes.

Day-2 horizontal scaling is needed when adjusting replica or shard counts for existing KubeBlocks-managed database clusters after initial deployment. It handles operational scaling scenarios by verifying matrix support and monitoring health readiness.