kubeblocks-addon-redis

To maintain Redis provisioning workflows in Kubernetes for legacy references, use a backward-compatible shim to route older requests while preserving the primary engine path. This ensures older references keep functioning without disruption.

The best way to migrate Redis deployment on KubeBlocks is to route new provisioning requests to the kubeblocks-engine-redis path while using the shim to handle legacy references. This separation ensures a smooth transition across versions.

Yes, the KubeBlocks Redis shim supports deployment in standalone, replication, and cluster topologies. It maintains backward compatibility for legacy environments requiring these Redis deployment configurations during cluster bootstrap.

You need a compatibility shim for Redis provisioning on Kubernetes to preserve older workflows when updating versions. It prevents unintended actions by routing legacy requests safely while pointing new tasks to the primary engine.

Use the Redis shim when maintaining compatibility for older references and environments during cluster bootstrap. For new provisioning tasks, you should prefer the kubeblocks-engine-redis path to access the primary features.

The limitation of using a Redis compatibility shim is that it only preserves legacy workflows and does not execute new provisioning actions. It requires routing new requests to the primary engine to avoid unintended operations and ensure full feature access.