Document emptyDir impact on ECK Desired Nodes and ResourcesAwareManagement - #7851
Merged
Conversation
…ement Explain that a non-PVC elasticsearch-data volume prevents Desired Nodes publishing for the whole cluster, not only in mixed PVC/emptyDir setups. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
Contributor
🔍 Preview links for changed docs |
Contributor
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
pkoutsovasilis
approved these changes
Aug 7, 2026
…I link Define the condition in place, note possible suboptimal topology-aware decisions, and avoid linking to removed Elasticsearch Desired Nodes docs. Co-authored-by: Cursor <cursoragent@cursor.com>
barkbay
commented
Aug 7, 2026
Co-authored-by: Cursor <cursoragent@cursor.com>
pebrc
approved these changes
Aug 7, 2026
pebrc
left a comment
pebrc
left a comment
Contributor
There was a problem hiding this comment.
LGTM, my 🤖 has a few edit suggestions that overall seem sensible to me. See them as non-blocking.
Co-authored-by: Peter Brachwitz <peter.brachwitz@gmail.com>
Co-authored-by: Peter Brachwitz <peter.brachwitz@gmail.com>
Contributor
Author
|
@elastic/admin-docs, 👋 , approved by ECK team, enabling auto-merge on this one. |
barkbay
enabled auto-merge (squash)
August 10, 2026 07:22
shainaraskas
approved these changes
Aug 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents an additional implication of using
emptyDir(or another non-PVC volume) for Elasticsearchelasticsearch-dataon ECK: besides data loss risk, ECK cannot compute storage for the Desired Nodes API, soResourcesAwareManagementbecomesFalseand Desired Nodes is cleared when Elasticsearch is reachable.Operators can misread
ResourcesAwareManagement=Falseas ECK stopping resource reconciliation. The current emptyDir section only warns about data loss.Related: elastic/cloud-on-k8s#9669 (condition docs), and the follow-up discussion on deriving Desired Nodes storage from
ephemeral-storage/emptyDir.sizeLimit.Generative AI disclosure