kubeblocks-op-switchover

A planned primary-secondary switchover for KubeBlocks-managed clusters is orchestrated by verifying engine support in the ops capability matrix and following a predefined workflow. This ensures safe role transition during promotion scenarios.

Switchover support depends on the specific database engine. You must confirm engine support against the KubeBlocks ops capability matrix before initiating the action to ensure the workflow is permitted.

A Day-2 switchover is a planned operational task that orchestrates a primary-secondary role transition for existing database clusters. It includes capability verification, health checks, and rollback boundaries to avoid unsafe states.

If a cluster is in a broken state, the switchover process routes diagnosis to troubleshooting mechanisms. It establishes rollback boundaries to prevent unsafe states and ensure safe operational transitions.

Yes, the switchover process routes monitoring to observability tools and includes explicit health checks. These checks verify step sequencing and safe role transition throughout the operational workflow.

This skill serves as the primary Day-2 switchover entry for KubeBlocks clusters. The legacy kubeblocks-switchover skill remains only as a compatibility shim for older operational workflows.