Skip to content

[feat](helm) scheduling fields for all doris-disaggregated components - #528

Open
SLoeuillet wants to merge 1 commit into
apache:masterfrom
SLoeuillet:feat/disaggregated-chart-scheduling
Open

SLoeuillet wants to merge 1 commit into
apache:masterfrom
SLoeuillet:feat/disaggregated-chart-scheduling

Conversation

@SLoeuillet

Copy link
Copy Markdown

What problem does this PR solve?

doris-disaggregated renders only msSpec.nodeSelector. The FE and the compute groups get no scheduling fields at all, so the chart can't place a cluster on tainted or dedicated nodes, though the CRD accepts nodeSelector, tolerations and affinity on all three sections.

This renders all three fields for msSpec, feSpec and computeSpec (every compute group), with empty defaults in values.yaml. It uses the shape the doris chart already uses for tolerations and affinity.

Related PR: #455 (nodeSelector only, FE and compute only). This one is a superset.

Release note

doris-disaggregated chart: nodeSelector, tolerations and affinity for the MetaService, FE and compute groups.

Check List (For Author)

  • Test
    • Manual test:
      • default values: helm template output is byte-identical to master;
      • with all three fields set on all three specs: they land on metaService, feSpec and every computeGroups[], and the CR validates (kubeconform -strict) against config/crd/bases/disaggregated.cluster.doris.com_dorisdisaggregatedclusters.yaml; a wrong-shaped tolerations is rejected.
  • Behavior changed:
    • No. Existing values render the same CR.
  • Does this need documentation?
    • No.

🤖 Generated with Claude Code

The chart passed only nodeSelector, and only for the MetaService. The CRD
accepts nodeSelector, tolerations and affinity on metaService, feSpec and
each compute group; render all three for all three, with empty defaults.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant