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

[Enhancement]Opensearch #604

Open
aceeric opened this issue Oct 9, 2024 · 0 comments
Open

[Enhancement]Opensearch #604

aceeric opened this issue Oct 9, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@aceeric
Copy link

aceeric commented Oct 9, 2024

It seems historically that people have installed Opensearch with masters and data nodes separated. (E.g. https://artifacthub.io/packages/helm/bitnami/opensearch).

I'm trying to evaluate which chart to use. My inclination would be to use the "official" Opensearch chart - meaning this repository - but I'm puzzled by the decision to not take the approach of separating masters from data etc. when this seems historically to be the case. Perhaps your team has knowledge that indicates the approach taken is "proper", "preferable", etc. (Quoting to convey the intent of the question..)

Note the Amazon docs seem to prefer dedicated master nodes.

Any insight is appreciated. Thanks.

P.S. if you thought it would be valuable I would consider a PR though - the current bundled approach is pretty deeply wired into the templating...

@aceeric aceeric added enhancement New feature or request untriaged Issues that have not yet been triaged labels Oct 9, 2024
@gaiksaya gaiksaya removed the untriaged Issues that have not yet been triaged label Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants