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.

Sign up for GitHub

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

Jump to bottom

HA spread of pods on single zone deployments not preferring different nodes #7665

Open
filintod opened this issue Apr 2, 2024 · 2 comments · May be fixed by #7666
Open

HA spread of pods on single zone deployments not preferring different nodes #7665

filintod opened this issue Apr 2, 2024 · 2 comments · May be fixed by #7666
Assignees
@filintod
Labels
kind/bug Something isn't working stale Issues and PRs without response

Comments

@filintod
Copy link
Contributor

filintod commented Apr 2, 2024

In what area(s)?

/area runtime
Chart deployment HA antiaffinity only if multiple zones available

/area operator
Chart deployment HA antiaffinity only if multiple zones available

/area placement
Chart deployment HA antiaffinity only if multiple zones available

What version of Dapr?

1.13, 1.12

Expected Behavior

If we have a single zone, pods should be tried to be spread on different nodes for the same deployment/statefulset

Actual Behavior

There is no anti-affinity that takes into account the node names

Steps to Reproduce the Problem

Set system with HA enable and 3 replicas, see there is no soft/hard antiaffinity with topologyKey: "kubernetes.io/hostname"

Release Note

RELEASE NOTE:
@filintod filintod added the kind/bug Something isn't working label Apr 2, 2024
@filintod filintod linked a pull request Apr 2, 2024 that will close this issue
Open
7 tasks
@filintod
Copy link
Contributor Author

filintod commented Apr 2, 2024

/assign

@dapr-bot
Copy link
Collaborator

dapr-bot commented Jun 1, 2024

This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot dapr-bot added the stale Issues and PRs without response label Jun 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@filintod filintod

Labels
kind/bug Something isn't working stale Issues and PRs without response
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Try spread pods in HA to different nodes on single zone deployments filintod/dapr
2 participants
@filintod @dapr-bot