-
Couldn't load subscription status.
- Fork 169
ECK: Document recovery from failed volume upsize #3459
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
ECK: Document recovery from failed volume upsize #3459
Conversation
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds documentation to help users recover from failed Elasticsearch volume expansion operations in ECK (Elastic Cloud on Kubernetes). The change addresses user issues where volume expansion failures can leave deployments in an unrecoverable state.
- Adds a new troubleshooting section for volume expansion failures
- Documents the recommended recovery approach using nodeSet renaming
- Provides specific error message and solution context
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Co-authored-by: Copilot <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
🔍 Preview links for changed docs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! 🚢
Just two super nit-picky comments. :-)
Signed-off-by: Michael Montgomery <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The blanket statement about Azure Disks is no longer true. Azure Disk CSI Driver now supports resizing attached disk from v1.11.
We can keep it as an example but should qualify the statement.
Co-authored-by: Peter Brachwitz <[email protected]>
Fixes elastic#3185 by adding a new about how to integrate the GSCC integration's data with Elastic Security workflows. Nick, please review if I've said the correct index names / places the data appears. --------- Co-authored-by: Mike Birnstiehl <[email protected]>
Co-authored-by: florent-leborgne <[email protected]>
Co-authored-by: Liam Thompson <[email protected]>
Linked to: elastic#3277 This PR only works on the Agent builder docs: Updates screenshots for 9.2 nav Does minor cleanup
Creates the Serverless changelog for Oct 13, 2025. Closes elastic#3378 --------- Co-authored-by: Janeen Mikell Roberts <[email protected]>
This PR updates the [Rotate SSL/TLS CA certificates](https://www.elastic.co/docs/reference/fleet/certificates-rotation) page with a new section ('Limitations') to clarify current product behaviors. This addition addresses open questions raised in [How to replace expired or soon to expire CA in Fleet (Elastic Agent & Fleet Server)](elastic/ingest-docs#167) and provides explicit documentation of known limitations.
👋 howdy, This important snippet was moved down only [under self-managed](https://www.elastic.co/docs/manage-data/lifecycle/data-tiers#configure-data-tiers-on-premise) but also applies to admins in ECK+ECE. (Only ECH manages it for users but it also still does technically apply to them.) <img width="764" height="302" alt="image" src="https://github.com/user-attachments/assets/3f8b66dc-f957-4fc1-be7a-1af7270f78da" /> --------- Co-authored-by: Vlada Chirmicci <[email protected]>
This PR adds a new troubleshooting page covering connectivity issues between OpenTelemetry SDKs, the Collector, and Elastic endpoints. The page includes: * Common error symptoms * Differentiation of root causes (firewall, endpoint errors, proxy misconfiguration, SDK vs Collector failures) * Step-by-step resolution checks (DNS, reachability, port testing, TLS validation) * Links to related existing pages (proxy settings, debug logging) This content is intended to help users diagnose networking problems even when proxy settings appear correct but ports or firewalls block traffic. Resolves elastic#2351
Resolves elastic#2590. This PR: * Removes the **Navigation menu** section. Explaining how to use the navigation menu felt like overkill – the UI should be intuitive enough not to need docs. Also, updating this section to account for the 9.2 changes while keeping it accurate for pre-9.2 versions would have made the section complex by adding more versioning tags, without necessarily adding much user value. * Makes the wording around management and project settings sections more general, so it applies to all 9.x versions. Since some items are moving from **Stack Management** to a new **Data management** section, maintaining precise lists of menu items for both 9.2 and pre-9.2 versions and serverless would have introduced more versioning/tagging complexity. This also reduces maintenance complexity for future version updates. * Reorders sections to reflect the order of pages in the 9.2 UI. * Adds missing sections for attack discovery and notes. * Updates any mention of items that have moved from **Stack Management** to **Data management**. * Updates any screenshots that show the navigation menu. Preview: [Elastic Security UI](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/3405/solutions/security/get-started/elastic-security-ui)
Closes elastic#3272 Updates references to pages that are moving from Stack Management to Data Management in 9.2 in the `manage-data` directory of this repo following the guidance in elastic#2566. --------- Co-authored-by: David Kilfoyle <[email protected]>
Contributes to the non-generated API docs component of elastic/docs-content-internal#434 - Creates a new section explaining Spaces behavior - Links to that section from each `curl` example using a reusable snippet --------- Co-authored-by: florent-leborgne <[email protected]>
This aligns the names to line up with the names listed for ECH. https://www.elastic.co/docs/reference/cloud/cloud-hosted/regions#ec_amazon_web_services_aws_regions
Simple typo I noticed fixup. Co-authored-by: Colleen McGinnis <[email protected]>
Not really sure what's the best way to fix this. This paragraph says "customers obtain..." but the rest of the doc has a difference voice: "you..."
+ Adds the otel mode configuration issue to the known issue list with the workaround - #10822 --------- Co-authored-by: Fabrizio Ferri-Benedetti <[email protected]>
…ic#3655) Minor editing fix.
elastic#3658) Reverts elastic#3569 because the latest serverless update has happened
Corrected a typo under the section Windows.zip: removed a ` next to %ES_HOME% Co-authored-by: David Kilfoyle <[email protected]>
Co-authored-by: Liam Thompson <[email protected]>
This PR closes elastic#3659 and documents limitations when working with arrays.
## Description This doc PR is to address [this internal ticket](elastic/support-tech-lead#1660). Change detail: [this comment](elastic/support-tech-lead#1660 (comment)). ## Preview before PR merge - [deploy-manage/deploy/cloud-enterprise/change-endpoint-urls.md](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/3513/deploy-manage/deploy/cloud-enterprise/change-endpoint-urls) - [deploy-manage/deploy/cloud-enterprise/ece-wildcard-dns.md](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/3513/deploy-manage/deploy/cloud-enterprise/ece-wildcard-dns) - [deploy-manage/deploy/cloud-enterprise/enable-custom-endpoint-aliases.md](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/3513/deploy-manage/deploy/cloud-enterprise/enable-custom-endpoint-aliases) - [deploy-manage/security/secure-your-elastic-cloud-enterprise-installation/manage-security-certificates.md](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/3513/deploy-manage/security/secure-your-elastic-cloud-enterprise-installation/manage-security-certificates) ## Preview after PR merge * https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/ece-wildcard-dns * https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/change-endpoint-urls * https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/enable-custom-endpoint-aliases * https://www.elastic.co/docs/deploy-manage/security/secure-your-elastic-cloud-enterprise-installation/manage-security-certificates --------- Co-authored-by: Edu González de la Herrán <[email protected]>
…nnection details" page (elastic#3687) This PR updates an outdated screenshot and a step in the Create an API key section for Serverless projects on the Find your connection details page. Related issue: elastic#3163
|
sigh. I merged main to try and fix a build issue, then realized I had accepted a suggestion here, which meant the subsequent push failed, so I did a |
In elastic/cloud-on-k8s#4467 it's noted that some users are dealing with volume expansion failure issues, and documenting how to recover from this situation would be helpful. This is the attempt to update that documentation.
After merge