feat(chart): nodeSelector/tolerations/affinity for api-rs, slackbotv2, postgres#2
Open
mo4islona wants to merge 1 commit into
Open
feat(chart): nodeSelector/tolerations/affinity for api-rs, slackbotv2, postgres#2mo4islona wants to merge 1 commit into
mo4islona wants to merge 1 commit into
Conversation
…, postgres
Add standard pod-scheduling knobs to the api-rs, slackbotv2 and postgres
workloads, mirroring the existing repoCache support. Lets operators pin the
control plane to dedicated nodes (e.g. a spot pool) without forking the chart.
Defaults are empty ({} / []) so rendered output is unchanged when unset.
values.schema.json and the chart version are updated to match.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds standard pod-scheduling knobs —
nodeSelector,tolerations,affinity— to the api-rs, slackbotv2 and postgres workloads in the Helm chart, mirroring the supportrepoCachealready has.Why
Lets operators pin the Centaur control plane to dedicated nodes (e.g. a cost-saving spot node pool) without forking the chart. Previously only
repoCachehonored these fields, so the rest of the stack could not be confined to a specific pool.Details
templates/apirs.yaml,templates/slackbotv2.yaml,templates/workloads.yaml(postgres StatefulSet): rendernodeSelector/affinity/tolerationsvia{{- with .Values.<component>.* }}, identical to the repoCache pattern.values.yaml: new empty defaults ({}/[]) per component — rendered output is unchanged when unset.values.schema.json: typed entries for the three new keys under each component.Chart.yaml: version bump0.1.79 → 0.1.80.Scope / not included
This covers the chart-managed control-plane pods only. The agent sandbox runtime pods are created by api-rs via the
agents.x-k8s.ioSandbox CRD and take no scheduling input from the chart today; pinning those would need an api-rs change (separate follow-up).Validation
helm lintpasses.helm templatewith sample overrides confirmsnodeSelector/tolerationsrender on all three workloads; with defaults, output is byte-identical to before.🤖 Generated with Claude Code