Generated by gh-aw-docs-staleness-sweep for elastic/docs-content on 2026-W24.
Path /deploy-manage/deploy/cloud-on-k8s · 94 total in scope · subtree corpus 94 pages.
Thresholds: stale_content_months=24, stale_image_min_gap_months=6.
Findings (6)
- file: deploy-manage/deploy/cloud-on-k8s/create-custom-images.md
line: 56
category: broken-external-link
severity: high
evidence: "(cloud.google.com/redacted) returned 404 (lychee);
Google Container Registry has been deprecated and replaced by Artifact Registry"
suggested_fix: |
replace link with current Artifact Registry documentation, e.g.
(cloud.google.com/redacted)
- file: deploy-manage/deploy/cloud-on-k8s/_snippets/es-config.md
line: 11
category: unsupported-version-mention
severity: medium
evidence: "lines 11 and 18 both contain comment 'On Elasticsearch versions before 7.9.0,
replace the node.roles configuration'; ECK 3.3+ supports only Elasticsearch 8+/9+,
and ECK 3.0-3.2 requires 7.17+ — pre-7.9 is below every supported range.
Support matrix: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s"
suggested_fix: |
remove both pre-7.9.0 node.roles fallback comments; the alternative configuration
they describe is irrelevant for all currently supported Stack versions (8+)
- file: deploy-manage/deploy/cloud-on-k8s/deploy-elastic-maps-server.md
line: 25
category: unsupported-version-mention
severity: medium
evidence: "line 25 explains a requirement for Maps Server prior to 7.14; line 33
contains a YAML example with 'version: 7.13'. ECK 3.3+ supports Elastic Maps
Server 8+/9+ only; 7.13 is below even the ECK 3.0-3.2 minimum of 7.17+.
Support matrix: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s"
suggested_fix: |
remove or archive the pre-7.14 elasticsearchRef requirement block and the
version: 7.13 YAML example; update minimum supported version context to 8+
- file: deploy-manage/deploy/cloud-on-k8s/k8s-openshift-anyuid-workaround.md
line: 13
category: unsupported-version-mention
severity: medium
evidence: "references APM Server behaviour change at version 7.9 and documents an
anyuid workaround for users on APM < 7.9; ECK 3.3+ supports APM Server 8+/9+
only — the entire pre-7.9 workaround targets versions below every supported range.
Support matrix: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s"
suggested_fix: |
remove or archive the pre-7.9 anyuid workaround section; it is irrelevant for
all currently supported Stack versions
- file: deploy-manage/deploy/cloud-on-k8s/manage-compute-resources.md
line: 57
category: unsupported-version-mention
severity: medium
evidence: "line 57 introduces the 7.11 heap-size boundary; line 59 gives an
instruction 'For Elasticsearch before 7.11, set ES_JAVA_OPTS'. ECK 3.3+ supports
only Elasticsearch 8+, so the pre-7.11 branch targets no supported version.
Support matrix: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s"
suggested_fix: |
remove the 'For Elasticsearch before 7.11' paragraph; automatic heap sizing
is always in effect for all supported versions (8+), so only the override
note is needed
- file: deploy-manage/deploy/cloud-on-k8s/standalone-elastic-agent.md
line: 20
category: unsupported-version-mention
severity: medium
evidence: "states 'Running standalone Elastic Agent on ECK is compatible only with
Stack versions 7.10+'; ECK 3.3+ supports standalone Elastic Agent 8+/9+ only —
the 7.10+ minimum is outdated and could mislead users.
Support matrix: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s"
suggested_fix: |
update the minimum version statement from 7.10+ to 8+ to match the current
ECK 3.3+ support matrix
Done when
- Stale content has been refreshed, archived, or annotated as historical.
- Stale screenshots are re-captured.
- Broken external links are replaced with current sources.
- Unsupported-version mentions are removed or moved to upgrade docs.
- A PR addressing this issue is merged.
Notes
- No
stale-content or stale-screenshot findings: all 94 in-scope pages were committed within the 24-month threshold and none carry image references.
- OpenShift docs links (403 responses) and GitHub source-repo links containing unresolved
{{version.eck}} template variables were omitted — 403s are likely bot-blocking false positives, and template-variable URLs are artifacts of lychee running on unrendered source files rather than actual link rot.
Generated by Docs staleness sweep agent · 506.7 AIC · ⌖ 13.2 AIC · ⊞ 26.4K · ◷
Generated by
gh-aw-docs-staleness-sweepforelastic/docs-contenton 2026-W24.Path /deploy-manage/deploy/cloud-on-k8s · 94 total in scope · subtree corpus 94 pages.
Thresholds: stale_content_months=24, stale_image_min_gap_months=6.
Findings (6)
Done when
Notes
stale-contentorstale-screenshotfindings: all 94 in-scope pages were committed within the 24-month threshold and none carry image references.{{version.eck}}template variables were omitted — 403s are likely bot-blocking false positives, and template-variable URLs are artifacts of lychee running on unrendered source files rather than actual link rot.