kubeblocks-create-cluster

Legacy kubeblocks cluster creation requests are handled by routing them to the generic engine path via a preflight gate, preserving compatibility for older saved prompts without breaking newer workflows.

A compatibility shim for older KubeBlocks create paths is a routing layer that intercepts legacy create-time requests and forwards them to the current generic engine, ensuring historical workflows continue to function.

No, you do not need the legacy create path for new KubeBlocks cluster deployments; it serves only as a fallback for historical workflows, and new requests should invoke the generic engine directly.

Your saved KubeBlocks prompt routes to the generic engine because the legacy create path applies a preflight gate that delegates actual cluster creation logic to kubeblocks-engine-generic to satisfy fallback behavior.

Yes, you can use kubeblocks-engine-generic for all cluster creation tasks, as the legacy create path simply forwards requests there and does not serve as the recommended primary create route for new requests.

The limitation of using a legacy create-path shim for KubeBlocks is that it only routes requests and delegates logic; it does not serve as the recommended primary create route and should only act as a safe fallback.