We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
/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
1.13, 1.12
If we have a single zone, pods should be tried to be spread on different nodes for the same deployment/statefulset
There is no anti-affinity that takes into account the node names
Set system with HA enable and 3 replicas, see there is no soft/hard antiaffinity with topologyKey: "kubernetes.io/hostname"
topologyKey: "kubernetes.io/hostname"
RELEASE NOTE:
The text was updated successfully, but these errors were encountered:
/assign
Sorry, something went wrong.
filintod
Successfully merging a pull request may close this issue.
In what area(s)?
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:
The text was updated successfully, but these errors were encountered: