Skip to content

8.10 Self-Managed: test & docs coverage gaps (docs ↔ chart ↔ E2E) #6308

@eamonnmoloney

Description

@eamonnmoloney

Summary

Tracking issue for test and documentation coverage gaps in Camunda 8.10 Self-Managed, found by cross-referencing the 8.10 docs (camunda-docs/docs/self-managed/), the 8.10 Helm chart (charts/camunda-platform-8.10), and the Self-Managed E2E suite (c8-cross-component-e2e-tests/tests/SM-8.10/).

Two gap classes:

  • Testing gaps — documented, user-facing behavior the SM-8.10 E2E matrix does not exercise.
  • Docs gaps — chart capabilities shipped in 8.10 that the docs don't cover (or under-document).

Each subtask notes any in-flight PR. Several referenced PRs are drafts, ship disabled, or are manual-only — they are not counted as closing the gap until landed and green. Sub-checkboxes track the test side and the docs side separately where both apply.


Testing gaps (docs promise it; SM-8.10 E2E doesn't prove it)


Docs gaps (chart can do it; 8.10 docs don't, or barely)

  • Kubernetes Gateway API setup — in flight: camunda-docs#8860 (rewrite Gateway API setup guide). Chart support also in test(8.10): add CI integration test scenarios for gateway namespace feature #6243.
  • global.tls.caBundle as the unified TLS-trust mechanism (per-component ...tls.secret now deprecated) — in flight: camunda-docs#8760 ([TLS E] TLS config guide), #8977.
  • Service-mesh / external routing toggles (global.ingress.external, global.gateway.external) — no PR.
  • OpenShift compatibility knob (global.compatibility.openshift.adaptSecurityContext) — no PR.
  • noSecondaryStorage engine-only mode — no docs PR (test: noSecondaryStorage should disable elasticsearch connection #5662 is test-only).
  • global.extraManifests — no PR.
  • global.createReleaseInfo — no PR.
  • requestBodySize / upload-size config — in flight: fix: align upload size with Zeebe message limits #6279 + camunda-docs#8975.
  • Multi-region Zeebe (global.multiregion.*) — in flight: camunda-docs#8981.
  • AWS-native auth via IRSA (secondary storage + document store + RDS IAM) — no PR.
  • Declarative identity.users[] / identity.clients[] / firstUser.* — no PR.
  • Orchestration profiles (orchestration.profiles.broker/admin/operate/tasklist) — no PR.
  • Identity-as-code authorization bootstrap (orchestration.security.initialization.*) — partial: camunda-docs#8571 (API permissions for machine clients), #8737 (global.rba.enabled).
  • Connector secrets via connectors.env[] + valueFrom.secretKeyRef — no PR.
  • Zeebe primary-storage / disk tuning (persistenceType, pvc*, data.disk.freeSpace.*, thread counts) — no PR.
  • Observability surface (prometheusServiceMonitor.*, per-component metrics ports/paths) — no PR.
  • Probe configuration (startup/readiness/liveness per component) — in flight: camunda-docs#8655 (liveness endpoint change).
  • Per-component image overrides / private-registry / air-gapped — no PR.
  • Scheduling/extensibility primitives (sidecars, initContainers, extraVolumes, nodeSelector, tolerations, affinity, serviceAccount automount) — no PR.
  • Connectors persistence (connectors.persistence.*) — no PR.
  • Optimize import alignment (optimize.partitionCount, optimize.migration.*) — no PR.
  • Bitnami/Keycloak removal → external-only — in flight: docs(8.10): document bitnami removal and add removal ADR #6278 (removal ADR), camunda-docs#8976 / #8873 (8.9→8.10 upgrade).

Cross-cutting

  • Confirm no 8.10 doc snippet still relies on global.secrets.autoGenerated (removed in 8.9+).
  • Bundled Keycloak removed in 8.10 → external-only, which raises the priority of the untested external-OIDC and external-PostgreSQL scenarios above.
  • Highest-overlap area (both test and docs gaps): external OIDC + external PostgreSQL + Gateway/Ingress TLS — the now-near-mandatory production shape.

Source analysis: 8.10-docs-vs-helm-gap-analysis.md. PR↔gap mapping is title/body-derived from open PRs as of 2026-06-03; draft/disabled status noted inline.


Cross-minor-version upgrade coverage is tracked separately in #6309.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/choreIndicates a maintenance chore (updating docs, etc)likelihood/highA recurring issueseverity/highMarks a bug as having a noticeable impact on the user with no known workaroundtriage:completed

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions