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

Expose CustomAntiAffinity for opensearch #2365

Open
1 task
robinAwallace opened this issue Dec 5, 2024 · 0 comments · May be fixed by #2366
Open
1 task

Expose CustomAntiAffinity for opensearch #2365

robinAwallace opened this issue Dec 5, 2024 · 0 comments · May be fixed by #2366
Labels
kind/feature New feature or request

Comments

@robinAwallace
Copy link
Contributor

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

  • It is possible to add custom anti affinity rules.
@robinAwallace robinAwallace added the kind/feature New feature or request label Dec 5, 2024
@kartikaysaxena kartikaysaxena linked a pull request Dec 6, 2024 that will close this issue
34 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant