[TASK] Update camunda-docs 8.10 pages for the removed global Elasticsearch and OpenSearch values

[bkenez]

Description

Camunda chart 15.x removes the deprecated global.elasticsearch.* and global.opensearch.* value trees. Any 8.10 values file that sets either tree now fails helm install and helm upgrade through a root-level keyRemoved constraint.

The unversioned (next, 8.10) documentation must use the component-scoped replacements:

• orchestration.data.secondaryStorage.elasticsearch.* or orchestration.data.secondaryStorage.opensearch.* for the Orchestration Cluster
• optimize.database.elasticsearch.* or optimize.database.opensearch.* for Optimize and its legacy exporter

The following pages require migration:

• docs/self-managed/components/orchestration-cluster/core-settings/configuration/partials/_secondary-storage.md
• docs/self-managed/concepts/secondary-storage/configuring-secondary-storage.md
• docs/self-managed/deployment/helm/cloud-providers/amazon/amazon-eks/eks-helm.md
• docs/self-managed/deployment/helm/configure/authentication-and-authorization/microsoft-entra.md
• docs/self-managed/deployment/helm/configure/database/elasticsearch/configure-elasticsearch-prefix-indices.md
• docs/self-managed/deployment/helm/configure/secret-management.md
• docs/self-managed/deployment/helm/configure/tls.md
• docs/self-managed/deployment/helm/install/production/index.md
• docs/self-managed/upgrade/helm/890-to-8100.md
• docs/self-managed/upgrade/prepare-for-upgrade.md

The upgrade documentation must describe removal of the complete trees, not only individual TLS keys. It must also correct the statements that the keys remain supported in 8.10 and that users can enable the removed bundled Elasticsearch subchart.

Versioned 8.7-8.9 documentation remains unchanged because the global values are still supported on those chart lines.

Acceptance criteria

• Replace active global.elasticsearch.* and global.opensearch.* configuration in every listed unversioned page with the correct component-scoped values.
• Ensure self-contained Orchestration examples explicitly select orchestration.data.secondaryStorage.type.
• Configure both Orchestration and Optimize when an example enables both consumers.
• Document the complete 8.9-to-8.10 migration mapping, including URL, authentication, TLS, AWS, prefix, JKS password, and cluster-name behavior.
• Remove instructions that enable the Elasticsearch subchart removed from chart 15.x.
• Leave versioned 8.7-8.9 documentation unchanged.
• Pass camunda-docs formatting and PR validation.

References

• Parent epic: [EPIC] Roll out the 8.10 removal of global Elasticsearch and OpenSearch values across consumers #6916
• Chart removal task: [TASK] Remove deprecated global Elasticsearch and OpenSearch values from 8.10 before GA #6766
• Chart removal PR: refactor: remove deprecated global elasticsearch and opensearch values from 8.10 chart #6914
• Documentation PR: docs(self-managed): migrate Helm datastore config off removed global elasticsearch and opensearch keys camunda-docs#9653

[distro-ci]

🧭 Triage Assessment

Field	Value
Work type	TASK
Kind	docs
Severity	🔴 High
Likelihood	🔶 Mid
Confidence	0.97

📝 Rationale

This is within SM Platform Distribution scope because the team boundaries assign ownership of Helm Charts, Self-Managed documentation, and Helm configuration issues to Distribution. It is a bounded documentation task, not a bug: the requested change updates public documentation rather than changing incorrect runtime behavior. The docs-only kind is appropriate because the issue targets specific upgrade, configuration, TLS, and installation pages; comparable documentation follow-ups are classified as TASK with kind=docs. It is not TOIL because it has a defined set of files and migration guidance, and it is not a feature request. Severity is high for task triage because the affected 8.10 pages instruct users to configure values that the chart rejects, potentially blocking Helm installs or upgrades, and the change spans multiple customer-facing documentation flows. The chart removal introduces root-level rejection and migration guidance requirements. Likelihood is mid: the failure is likely for users following the affected 8.10 documentation while configuring Elasticsearch or OpenSearch, but it does not affect every deployment, 8.7-8.9 versioned documentation is unaffected, and 8.10 is not yet generally released. No blocking information is missing because the issue identifies the affected pages, incorrect guidance, intended migration targets, parent issue, and removal task. The closest related issues are the parent rollout epic #6916, chart removal task #6766, broader cross-minor upgrade coverage #6309, and original deprecation issue #5172; none is an exact duplicate.

🔍 Similar Issues

#6916, #6766, #6309, #5172

---

🤖 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.