kubeblocks-engine-redis

Provision Redis clusters on KubeBlocks with topology, version, and storage configurations.

3|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/apecloud/kubeblocks-skills --skill kubeblocks-engine-redis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kubeblocks-engine-redis
Source: https://github.com/apecloud/kubeblocks-skills/tree/main/skills/kubeblocks-engine-redis
Command: npx skills add https://github.com/apecloud/kubeblocks-skills --skill kubeblocks-engine-redis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provision Redis on KubeBlocks with correct topology, version, and storage decisions to avoid misconfigurations and long iteration cycles.

Core Features & Use Cases

  • Default topology options: standalone, replication, and sharding
  • Version strategy aligned with current supported lines and shard consistency
  • Preflight interpretation and runtime truth via engine-create-matrix
  • Observability and next-hop routing for post-create operations
  • Compatibility path maintained with legacy kubeblocks-addon-redis as reference only

Quick Start

Provide the desired Redis topology and version, then apply the generated cluster manifest.

Frequently Asked Questions about kubeblocks-engine-redis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I provision a Redis cluster on KubeBlocks with replication or sharding?▼

Yes, KubeBlocks supports standalone, replication, and sharding Redis topologies. You select your desired topology and version during provisioning, and the system applies the correct configuration to generate a ready-to-use cluster manifest without manual setup.

What is the best way to configure Redis storage and versions when deploying on KubeBlocks?▼

The best way to configure Redis storage and versions is by using the engine-create-matrix as the runtime truth. It aligns your version strategy with currently supported lines and ensures shard consistency, preventing misconfigurations during cluster provisioning.

Do I need to run preflight checks before creating a Redis cluster on KubeBlocks?▼

Yes, preflight checks are required before creating a Redis cluster on KubeBlocks. The provisioning process enforces preflight readiness to validate your environment, ensuring the requested topology and storage configurations will deploy successfully without iteration errors.

Can I route to dedicated Redis operation paths after my KubeBlocks cluster is created?▼

Yes, after your Redis cluster is created, the system provides observability and next-hop routing to dedicated Redis operation paths. This guides you directly to the appropriate post-create operations based on the initial topology and version you provisioned.

Why does my Redis provisioning on KubeBlocks reference the legacy kubeblocks-addon?▼

Your Redis provisioning may reference the legacy kubeblocks-addon as a compatibility path maintained for reference only. The current provisioning process uses the engine-create-matrix as the primary truth to determine correct topology and storage decisions.