kubeblocks-op-lifecycle

To safely stop and start KubeBlocks database clusters, automate Day-2 lifecycle actions using guardrails that validate operations against the ops capability matrix before execution. This minimizes downtime and manual intervention for existing clusters.

Day-2 lifecycle management for KubeBlocks clusters involves automating stop, start, and restart operations. It ensures safety by applying explicit checks against the ops capability matrix to confirm support before executing any action.

You should not restart a KubeBlocks cluster without checking the ops capability matrix. Lifecycle automation relies on explicit support confirmation from the matrix to ensure safe execution and route to observability when issues arise.

The best way to handle legacy lifecycle references in KubeBlocks is to use automated lifecycle workflows that preserve compatibility with legacy references while guiding modern engine-entry flows for safe Day-2 operations.

You need explicit support confirmation before stopping a KubeBlocks cluster to prevent unsafe operations. The lifecycle workflow checks the ops capability matrix to validate the action and routes to troubleshooting if issues are detected.