[EPIC] Roll out the 8.10 removal of global Elasticsearch and OpenSearch values across consumers

[bkenez]

Description

The global.elasticsearch and global.opensearch value trees are removed from the 8.10 chart before GA (#6766). The removal adds root-level keyRemoved constraints, so any consumer that still sets these keys fails helm install/helm upgrade as soon as it picks up a chart version past 15.0.0-alpha4.

Known consumers and documentation that must migrate to the component-scoped keys (optimize.database.*, orchestration.data.secondaryStorage.*) are tracked as sub-issues of this issue.

Motivation / Use Case

Landing the chart-side removal without migrating the consumers breaks their next chart dependency bump. Tracking all rollout work as sub-issues in this repository keeps the removal auditable from one place.

Acceptance Criteria

• All sub-issues of this issue are closed.

References

• Removal task: [TASK] Remove deprecated global Elasticsearch and OpenSearch values from 8.10 before GA #6766
• Removal PR: refactor: remove deprecated global elasticsearch and opensearch values from 8.10 chart #6914
• Deprecation ADR: https://github.com/camunda/camunda-platform-helm/blob/main/docs/adr/0084-deprecate-global-elasticsearch-opensearch-configuration-in.md

[distro-ci]

🧭 Triage Assessment

Field	Value
Work type	TASK
Kind	chore
Severity	🔴 High
Likelihood	🔶 Mid
Confidence	0.96

📝 Rationale

This issue is within SM Platform Distribution scope because the team boundaries assign ownership of Helm Charts, camunda/camunda-platform-helm, Self-Managed documentation, automated deployments, and Helm configuration support to Distribution. It is a TASK rather than a BUG or FEATURE_REQUEST: it coordinates a discrete, planned migration across known consumers after an intentional 8.10 deprecation removal, with a concrete completion criterion that all sub-issues are closed. It is not TOIL because the work has a defined scope, dependency, and endpoint. The appropriate kind is chore because the triage guidance defines chore as maintenance, cleanup, tech debt, refactoring, dependency upgrades, and housekeeping; this rollout migrates consumers from deprecated keys and prevents compatibility failures. Severity is high because an un-migrated consumer fails helm install or helm upgrade after the chart dependency moves past 15.0.0-alpha4, creating cross-component and delivery-critical upgrade impact. Likelihood is mid because the failure is deterministic for each affected consumer, but only consumers that still set the removed keys are impacted and only when they perform the relevant chart dependency bump. The migration itself was intentionally planned after a deprecation window, with component-scoped replacements documented in the ADR and removal PR. No exact duplicate was found. Related issues are #5172, the original deprecation; #5175, a broader deprecated-key cleanup that explicitly excluded full global Elasticsearch/OpenSearch tree removal; #4839, an analogous deprecated-parameter removal task; and #6766, the chart-side removal implementation tracked by this rollout epic.

🔍 Similar Issues

#6766, #5172, #5175, #4839

---

🤖 This issue was automatically triaged by an AI-based system.
✋ If you believe this assessment is incorrect, update the labels or add the triage:manual label for human review.