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

k8s e.g.: Enable high availablility by NOT collocating pods on the same node #741

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Miyurz
Copy link
Contributor

@Miyurz Miyurz commented Dec 9, 2019

With this change, we ensure that the replica pods of the same
deployment do not get assigned to the same node. Fot this, we have
employed k8s anti-affinity rule.

With this change, we ensure that the replica pods of the same
deployment do not get assigned to the same node. Fot this, we have
employed k8s anti-affinity rule.
@LORdV0LD3m0rt
Copy link

@sgotti Can you please review ?

@Miyurz Miyurz changed the title k8s e.g.: Enable high availablility by NOT collocating pods on same node k8s e.g.: Enable high availablility by NOT collocating pods on the same node Dec 9, 2019
Copy link
Member

@sgotti sgotti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Miyurz Thanks for your PR.

Since this is just a k8s example I'd like to avoid making it more complex as needed. Additionally if people wants to test it on minikube or another single node k8s cluster this change will make it impossible to test.

So we can add this but make it commented out with a heading comment that describes it.

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.

3 participants