-
Notifications
You must be signed in to change notification settings - Fork 86
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
Minor typo fix in mention of localities #1957
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
Thanks @johscheuer! I have a related question: I am creating a cluster using the However pods are still getting scheduled on same nodes, and I do not see any topology spread / pod anti-affinity being generated in the pod YAML definitions created by the operator. I also tried to find references to this configuration in the codebase of the operator, but I can't find anything related to the default as mentioned there 🤔 instead I see plenty of checks for the key Do you have any pointers for me to understand better how the fault domain feature works, or perhaps existing E2E tests covering this? |
Could you create an issue or a forum post for that? Tracking all the comments/question in unrelated PR's makes it harder for me to make sure I answered your questions. The best is to always produce a minimal reproducible example. |
Sure, I wanted to make sure that there is a problem first, by checking the relevant code. I will try to reproduce it and then open an issue. |
Figured a few things out, the issue is open here. Thanks! |
Description
This is a minor typo fix in the documentation (technical design).
Type of change