kubeblocks-switchover

To perform a safe switchover, you promote a secondary replica and demote the current primary using documented pre-checks, dry-run validation, and verification steps. This ensures high availability across supported engines like MySQL, PostgreSQL, Redis, and MongoDB.

Primary/secondary switchover is supported for MySQL, PostgreSQL, Redis, and MongoDB replication setups. The workflow includes engine-specific steps for promoting a secondary and demoting the current primary during maintenance or controlled rollouts.

Yes, you can validate a replication switchover before applying it by using the dry-run validation process. This checks cluster health and verifies steps before you promote a secondary and demote the current primary.

The recommended path for production database switchover is using the kubeblocks-op-switchover approach. This legacy switchover workflow serves as a reference documenting steps for promoting a secondary and demoting a primary across supported engines.

If your database switchover is failing, troubleshoot it by following the documented rollback and troubleshooting guidance. Ensure pre-checks and cluster health checks pass before attempting to promote a secondary and demote the primary.

Yes, an OpsRequest is used to initiate a switchover for high availability. It triggers the workflow to promote a secondary and demote the current primary across supported engines while enforcing safe practices like dry-run validation.