Self-Managed Helm: cross-minor-version upgrade coverage (test & docs)

[eamonnmoloney]

Summary

Tracking issue for cross-minor-version upgrade coverage (test + docs) in Camunda 8 Self-Managed Helm. Split out from the broader coverage tracker #6308, which only touched upgrades obliquely.

Scope: upgrading the chart across minor versions (e.g. 8.8→8.9, 8.9→8.10) — the upgrade-minor CI matrix, migration behavior, and the corresponding upgrade guides. Each subtask notes in-flight PRs and their status; several are drafts, so they are not counted as closing the gap until landed and green.

---

Upgrade-path scenarios (CI / E2E)

• Legacy upgrade path (hub-legacy) — in flight: test(8.10): enable hub legacy upgrade scenario #6305 (enable hub legacy upgrade scenario), ci(8.10): enable hub-legacy and hub-mixed upgrade-minor CI scenarios #6187 (enable hub-legacy + hub-mixed upgrade-minor CI scenarios).
• Mixed upgrade path (hub-mixed) — in flight: test(8.10): enable hub mixed upgrade scenario #6306 (enable hub mixed upgrade scenario), ci(8.10): enable hub-legacy and hub-mixed upgrade-minor CI scenarios #6187.
• Modular upgrade path — in flight: fix(ci): add missing migrator feature to modular-upgrade-minor scenarios in 8.9 and 8.10 #6106 (add missing migrator feature to modular-upgrade-minor scenarios, 8.9 & 8.10).
• Pinned-images upgrade — in flight: test(8.10): add hub-pinned-images upgrade scenario #6188 (hub-pinned-images upgrade scenario).

Component-disabled / topology upgrades

• Console-disabled / Web Modeler-only upgrade — in flight: test(8.10): add hub-webmodeler-only scenario for console-disabled upgrade #6190 (hub-webmodeler-only scenario for console-disabled upgrade).
• External-DB upgrade (external PostgreSQL across upgrade) — relates to test(8.10): add hub-external-db scenario for external PostgreSQL validation #6189; fix(ci): add PostgreSQL StatefulSet cleanup to upgrade-minor pre-setup for 8.9 and 8.10 #6105 (PostgreSQL StatefulSet cleanup in upgrade-minor pre-setup).

Secondary-storage upgrades

• OpenSearch upgrade-minor scenarios — in flight: fix(ci): repair OpenSearch upgrade-minor scenarios for 8.9 and 8.10 #6107 (repair OpenSearch upgrade-minor for 8.9 & 8.10), fix(ci): remove $FLOW suffix from OpenSearch index prefixes in upgrade scenarios #6104 (remove $FLOW suffix from OpenSearch index prefixes in upgrade scenarios).
• Elasticsearch upgrade path — no dedicated PR identified; confirm coverage.

TLS / ingress changes across upgrade

• Zeebe TLS migration on upgrade — in flight: test(8.8): cover Zeebe TLS migration upgrade #6281 (cover Zeebe TLS migration upgrade, 8.8).
• Ingress host-reference fix on upgrade — in flight: ci: remove dead env entries from playwright IT jobs and fix upgrade ingress host ref #5467 (fix upgrade ingress host ref).
• Zeebe StatefulSet rollout on minor upgrade — in flight: ci: set Zeebe StatefulSet maxUnavailable to 100% on minor upgrades for 8.7-8.10 #5933 (set maxUnavailable: 100% on minor upgrades, 8.7–8.10).

8.9 → 8.10 specific

• Bitnami / bundled-Keycloak removal upgrade (external-only after upgrade) — in flight: docs(8.10): document bitnami removal and add removal ADR #6278 (removal ADR) · docs camunda-docs#8976, camunda-docs#8873 (8.9→8.10 upgrade guide + camundaHub).
• Web Modeler PVC rename on upgrade — in flight: fix: align deployment PVC claimName casing to webmodeler-data in 8.9 and 8.10 #5887 (align PVC claimName casing in 8.9 & 8.10) · docs camunda-docs#8752 (PVC name fix upgrade warning), camunda-docs#8877 (unused PVC deletion notice).
• Removed values keys 8.8→8.9 — docs camunda-docs#8916 (document additional removed keys in 8.8→8.9 upgrade), camunda-docs#5765-equivalent (fix: remove redundant operate/tasklist multitenancy keys in 8.9 and 8.10 #5765: remove redundant operate/tasklist multitenancy keys).
• extraConfiguration map→list format change (8.8→8.9) — no test PR; confirm an upgrade scenario exercises the format migration.

E2E migration behavior

• Post-upgrade functional validation — existing c8-cross-component-e2e-tests/tests/SM-8.10/migration-path-user-flows.spec.ts (gated on IS_MIGRATION); covers navigation + process preservation, not data-integrity counts, schema migration, or rollback. Gap: integrity/rollback validation.
• Weekly upgrade workflow — c8-cross-component-e2e-tests#2305 (skip organization deletion in weekly upgrade workflow).

Docs — upgrade guides

• 8.9→8.10 Helm upgrade guide — in flight: camunda-docs#8873, camunda-docs#8976.
• Patch-upgrade clarifications — in flight: camunda-docs#8854.
• 8.9 migration manual links — in flight: camunda-docs#8920.
• 8.8 update/upgrade adjustments — in flight: camunda-docs#8679.

---

Related: #6308 (overall 8.10 test & docs coverage gaps). PR↔scenario mapping is title/body-derived from open PRs as of 2026-06-03; draft/disabled status noted inline.

[distro-ci]

🧭 Triage Assessment

Field	Value
Work type	TASK
Kind	chore
Severity	🔴 High
Likelihood	🔥 High
Confidence	0.94

📝 Rationale

This is within SM Platform Distribution scope because the team-boundaries doc assigns Helm Charts, the camunda/camunda-platform-helm repository, Self-Managed documentation, integration/deployment readiness for periphery such as OIDC providers and secondary storage, and automated scenario testing/deployments to this team, and the issue is explicitly about Helm cross-minor upgrade coverage and upgrade guides. Under the task/non-feature triage guide, this is TASK rather than BUG because kind/bug is reserved for incorrect existing behavior, while kind/chore covers maintenance, toil, cleanup, tech debt, and housekeeping; this issue is an umbrella tracker for missing CI/E2E coverage and upgrade documentation, not a report of one broken runtime behavior. kind=chore fits better than internal or docs because the requested work is not documentation-only and also includes the upgrade-minor CI matrix and migration-behavior validation, while it is partly customer-facing through upgrade guides. Severity is high by the task-triage heuristic because the guide defines high impact as cross-component, delivery-critical, or customer-impacting improvement, and this issue spans multiple upgrade paths across 8.8→8.9 and 8.9→8.10, migration validation gaps, and missing upgrade-guide coverage for released Self-Managed Helm versions. Likelihood is high because the gap is systematic and recurring: the issue enumerates many unchecked scenarios, notes that several referenced PRs are still drafts and do not yet close the gap, and related repo issues already track broader or adjacent coverage/matrix gaps rather than a one-off incident. I do not see a strict duplicate: #6308 explicitly says cross-minor upgrade coverage is tracked separately in #6309, while #5300, #6172, and #6192 are broader or narrower related coverage issues in the same repo. The issue has enough information for non-feature triage because it states the current limitation, affected upgrade areas, and what improves if the work lands.

🔍 Similar Issues

#6308, #5300, #6172, #6192

---

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