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
Opensearch have the option to add custom anti affinity rules and we should expose it.
This would allow the option to ensure that two opensearch pods do not run on the same node in a zone.
The value that should be exposed: https://github.com/elastisys/compliantkubernetes-apps/blob/main/helmfile.d/upstream/opensearch-project/opensearch/values.yaml#L253-L256
No response
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Proposed feature
Opensearch have the option to add custom anti affinity rules and we should expose it.
This would allow the option to ensure that two opensearch pods do not run on the same node in a zone.
The value that should be exposed: https://github.com/elastisys/compliantkubernetes-apps/blob/main/helmfile.d/upstream/opensearch-project/opensearch/values.yaml#L253-L256
Proposed alternatives
No response
Additional context
No response
Definition of done
The text was updated successfully, but these errors were encountered: