Skip to content

PR 5.4: Enable Cluster-capable clients #348

Description

@KurodaKayn

What to build

Make the application Redis clients Cluster-ready while preserving the ability to run in the current managed HA standalone mode. Client configuration should cover Cluster topology discovery, MOVED and ASK redirects, topology refresh, retry behavior, TLS, auth, and rollback to standalone mode.

Acceptance criteria

  • Redis client configuration can select standalone managed HA mode or Cluster mode without code changes.
  • Cluster mode handles MOVED and ASK redirects, topology refresh, retries, TLS, and auth according to the selected provider requirements.
  • Integration tests verify the app can read and write through Cluster-capable clients against a Cluster-compatible environment.
  • Standalone managed HA mode remains the rollback path and is still covered by tests or smoke checks.

Blocked by

Metadata

Metadata

Assignees

Labels

area:backendBackend API, domain services, persistence, or server behaviorarea:infraInfrastructure, deployment, Kubernetes, Docker, Redis, or operationsopsOperational work, runbooks, deployment safety, or production readinesspriority:p2Normal priority; useful but not urgenttestAutomated tests, test fixtures, coverage, or test infrastructuretopic:redisRedis keys, caching, sessions, persistence, or HA behavior

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions