Skip to content

Added valkey sentinel#82

Open
mboncalo wants to merge 2 commits intovalkey-io:mainfrom
mboncalo:feature/valkey-sentinel
Open

Added valkey sentinel#82
mboncalo wants to merge 2 commits intovalkey-io:mainfrom
mboncalo:feature/valkey-sentinel

Conversation

@mboncalo
Copy link

No description provided.

Signed-off-by: Mihai Boncalo <mboncalo@gmail.com>
@mboncalo mboncalo force-pushed the feature/valkey-sentinel branch from 88d56b8 to dda0aa6 Compare November 19, 2025 06:47
Signed-off-by: Mihai Boncalo <mboncalo@gmail.com>
@varadiistvan
Copy link

Hi! This is not a hard request, more like a nice to have, but I feel like having Sentinel and the standalone deployment in the same chart offers some nice QOL, while not making the chart a lot more annoying to develop:

  • Version bumps and related changes are easier
  • It's easier as a user of the chart to migrate between these versions

I also feel like there's no large architecture level change between the two. If I'm wrong on this, please correct me!

For this, I'd like it to be considered (once again, not a binding request) to house them both in the same chart.

As for testing, I'll do some of it for our own use case.

@mboncalo
Copy link
Author

Hi All,
Sorry for pushing this to early, it's not my latest and lots of HA use cases are missing.
Please wait to push my latest version next week

@sgissi
Copy link
Collaborator

sgissi commented Dec 2, 2025

@mboncalo If you are willing, once #84 is merged, it would be great to have your implementation of Sentinel in this chart.

@Thakurvaibhav
Copy link

Is this being actively worked on?

It would be a very nice feature as we start rolling out valkey to 100s of our clusters.

@jayteaftw
Copy link

@mboncalo If you are willing, once #84 is merged, it would be great to have your implementation of Sentinel in this chart.

Since #84 is merge, will we being sentinel soon?

@Hazmi35
Copy link

Hazmi35 commented Feb 6, 2026

Is this superseded by #22? Are you still working on this?

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.

7 participants