Skip to content

feat: support Valkey Cluster under various common conditions - #175

Closed
ankitpatisfdc wants to merge 26 commits into
valkey-io:mainfrom
ankitpatisfdc:feature/valkey-cluster-mode-next
Closed

feat: support Valkey Cluster under various common conditions#175
ankitpatisfdc wants to merge 26 commits into
valkey-io:mainfrom
ankitpatisfdc:feature/valkey-cluster-mode-next

Conversation

@ankitpatisfdc

Copy link
Copy Markdown

Inspired by the feedback on my earlier PR, this PR introduces a functional test suite using kind, and uses it to iterate on multiple features with LLM agents using logs from kind deployments as feedback.

This is a separate PR because

  1. the status of LLM-assisted contributions to valkey-helm isn’t clear from existing literature within the repository, and
  2. the volume of changes is huge.

From recent commits to main, it’s clear the maintainers have decided on an operator instead of a Helm chart for cluster support. However, as of now, there is still value in having fleshed-out and tested cluster capability within the chart.

Please note that the contributions are LLM-assisted, but thoroughly tested through unit tests, functional tests, and actual production deployments to GKE.

YMMV on other providers, but I remain committed to supporting the major cloud and K8s providers and their quirks, if any are brought to my attention.

@ankitpatisfdc
ankitpatisfdc force-pushed the feature/valkey-cluster-mode-next branch from e45ca4e to 598a082 Compare May 24, 2026 09:30
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
@ankitpatisfdc
ankitpatisfdc force-pushed the feature/valkey-cluster-mode-next branch from 598a082 to e4c7f7e Compare July 12, 2026 17:40
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
Signed-off-by: Ankit Pati <ankit.pati@salesforce.com>
@Bloodraven21

Copy link
Copy Markdown
Collaborator

hey sorry but the valkey cluster would be only supported by the valkey resources helm chart

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants