Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Master podAntiAffinity example differs from client and data examples in helm/opendistro-es/values.yaml #776

Open
dale-c-anderson opened this issue Jul 9, 2021 · 0 comments
Labels
bug Something isn't working

Comments

@dale-c-anderson
Copy link

Describe the bug
I don't know enough about podAntiAffinity to be able to tell if this is actually a bug; it might just be a clarification issue.

All I know is that one of these things:

is not like the other. On my cluster I used the weighted-style for all 3, which had the desired effect of distributing one master,client, and data pod to each worker node.

Is the master example different on purpose? It appears so, as all 3 podAntiAffinity blocks were originally added by @ashwinkumar12345 in the same commit and then later changed to example code instead, I just don't know the reasonig for it.

The kubernetes docs shows a weighted podAntiAffinity example, and I know there are other ways to do it. I just don't know which is the best way.

If someone more knowledgeable than me can tell me one way or the other, I'd be happy to submit a PR.

@dale-c-anderson dale-c-anderson added the bug Something isn't working label Jul 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant