Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bitnami/redis] replica anti-affinity #17222

Open
jcpunk opened this issue Jun 20, 2023 · 1 comment
Open

[bitnami/redis] replica anti-affinity #17222

jcpunk opened this issue Jun 20, 2023 · 1 comment
Labels
feature-request on-hold Issues or Pull Requests with this label will never be considered stale redis

Comments

@jcpunk
Copy link
Contributor

jcpunk commented Jun 20, 2023

Name and Version

bitnami/redis 17.11.6

What is the problem this feature will solve?

By default kubernetes may simply decide to put the redis master/slave hosts on a single worker. This can hide the fact that, while you've got multiple systems for HA, they are all on a single node.

What is the feature you are proposing to solve the problem?

Set a default pod anti-affinity for the redis master/slaves to spread out the pods that can be ignored if no other scheduling paths are viable.

What alternatives have you considered?

manually passing in the affinity to the chart as extra values.

@github-actions github-actions bot added the triage Triage is needed label Jun 20, 2023
@javsalgar javsalgar changed the title [redis] replica anti-affinity [bitnami/redis] replica anti-affinity Jun 21, 2023
@github-actions github-actions bot added in-progress and removed triage Triage is needed labels Jun 21, 2023
@bitnami-bot bitnami-bot assigned CeliaGMqrz and unassigned javsalgar Jun 21, 2023
@CeliaGMqrz
Copy link
Contributor

Hi @jcpunk,

Sorry for the delay, thanks for reporting this issue.

This is currently on our radar. We have an internal task in the backlog to review all applications with multiple roles. Unfortunately, we're a small team and our capacity is not too high. I will move this issue to ON-HOLD until we have updates about the related task.

As a workaround, you could combine the chart values commonLabels and affinity to configure a different affinity type.

@github-actions github-actions bot added on-hold Issues or Pull Requests with this label will never be considered stale and removed in-progress labels Jun 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request on-hold Issues or Pull Requests with this label will never be considered stale redis
Projects
None yet
Development

No branches or pull requests

3 participants