Skip to content

[TASK] Document stable labels for pod anti-affinity #6932

Description

@bkenez

Description

The Helm chart already supports upgrade-stable Web Modeler and Camunda Hub pod anti-affinity selectors by pairing a user-owned podLabels entry with the same selector under affinity. This pattern is not documented in the canonical Camunda documentation.

Issue #5876 describes the resulting maintenance problem: users inspect a first deployment and hard-code chart-managed labels that can change during upgrades.

Motivation / Use Case

Documenting the existing composition removes the install-inspect-hardcode workflow without adding a new values API, templating affinity values, or coupling users to internal chart helpers.

Acceptance Criteria

  • The current Helm pod-scheduling page documents the pattern with camundaHub.restapi and identifies camundaHub.websockets as equivalent.
  • The 8.9 and 8.8 versioned pod-scheduling pages document the corresponding webModeler.* paths.
  • The 8.7 production guide documents the same pattern under reliability guidance.
  • The guidance covers namespace scope, topology labels, preferred versus required anti-affinity, and scheduler cost.
  • The documentation links to the 8.9-to-8.10 Web Modeler-to-Camunda Hub migration guidance.
  • The guidance states that the same podLabels and affinity pairing applies to every affinity-capable component (SUPPORT-25387 targeted Connectors; SUPPORT-24532 asked for all components).
  • The guidance warns against selecting on chart-managed labels such as app.kubernetes.io/component, whose values have changed between chart versions, and notes that overriding the Orchestration Cluster (8.7: Zeebe) affinity replaces the default hard podAntiAffinity rule.

Additional Context

This is documentation for existing non-breaking behavior. No chart template, default, or rendered manifest change is required.

References

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationkind/docslikelihood/midObserved occasionallyseverity/midMarks a bug as having a noticeable impact but with a known workaroundsupportMarks an issue as related to a customer support request (don't edit the lable)triage:completed

    Type

    No type

    Fields

    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