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

Update documentation to clarify ES node.processors section. #5941

Merged

Conversation

naemono
Copy link
Contributor

@naemono naemono commented Aug 10, 2022

resolves #5940

Update the public documentation to clarify that the operator does not directly manage the Elasticsearch node.processors setting.

@naemono naemono added the >docs Documentation label Aug 10, 2022
@thbkrkr thbkrkr self-assigned this Aug 11, 2022
@thbkrkr thbkrkr added the v2.5.0 label Aug 12, 2022
…-resources.asciidoc

Co-authored-by: Thibault Richard <thbkrkr@users.noreply.github.com>
@naemono naemono merged commit 073a68a into elastic:main Sep 7, 2022
@naemono naemono deleted the 5940-clarify-node-processors-es-setting branch September 7, 2022 16:05
fantapsody pushed a commit to fantapsody/cloud-on-k8s that referenced this pull request Feb 7, 2023
…5941)

* Update documentation to clarify ES node.processors section.

* Update docs/orchestrating-elastic-stack-applications/managing-compute-resources.asciidoc

Co-authored-by: Thibault Richard <thbkrkr@users.noreply.github.com>

Co-authored-by: Thibault Richard <thbkrkr@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>docs Documentation v2.5.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clarify that the operator does not automatically set Elasticsearch's node.processors setting.
2 participants