nextcloud / nextcloud/helm

Feature: Redis Cluster and Valkey Cluster as optional subcharts

Open
#671 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go Template
Stars
534
Forks
314
Avg merge
42m
Merged PRs (30d)
1

Description

Description of the change

Since Redis Cluster is supported upstream we should also support it in this chart and do as much templated configuration as possible. We should start by adding Redis Cluster as a subchart (and valkey cluster as the alternative with more features and a better license).

We should also have a test for it, and a test for redis proper honestly.

Benefits

Easily to support testing issues with redis cluster/valkey cluster if we already have a way to deploy it via the chart easily. Supports users scaling their infra better.

Possible drawbacks

Another thing to support and write tests for.

Additional information

Relates to #543

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing Helm chart structure and subchart configuration. Add optional Redis Cluster and Valkey Cluster deployment support, with templated configuration, and add tests covering both clustered deployments and regular Redis.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes, redis
Domain
databases, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.