Loading...

XML

Word

Printable

Epic Name:
Support Global NodeSelectors and Tolerations in Central CR
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
True
Parent Link:
ROX-31014Global NodeSelector and Tolerances Support for Central CR
Color Status:
Not Selected
Epic Status:
In Progress
Feature Link:
ROX-31014 - Global NodeSelector and Tolerances Support for Central CR
Hierarchy Progress Bar:

0% To Do, 100% In Progress, 0% Done
Status Summary:
Hide

2025-11-25:

implementation PR (for both Central and Secured Cluster CRs) in progress

TBD: code clean-up and more E2E testing

2025-11-18:

started implementation work
Show
2025-11-25: implementation PR (for both Central and Secured Cluster CRs) in progress TBD: code clean-up and more E2E testing 2025-11-18: started implementation work
Intelligence Requested:
Market:
PX Impact Score:

Find a place for the new fields. Perhaps something like spec.deploymentDefaults would be a better home than top-level spec? Think of a name generic enough to:
- allow adding additional fields in the future (e.g. DeploymentSpec currently also contains hostAliases which could also use such default top-level setting)
- be consistent with SecuredCluster if we also add such fields to it (now or eventually)
Add the new fields to the schema
- nodeSelector
- tolerations
- pinToNodes: {None|InfraRole}
  - the former value is the default and is a no-op
  - the latter acts as the following default for the other ones:
    nodeSelector:
    node-role.kubernetes.io/infra: ""
    tolerations:
    - key: node-role.kubernetes.io/infra
    value: reserved
    effect: NoSchedule
    - key: node-role.kubernetes.io/infra
    value: reserved
    effect: NoExecute
  - background discussion
Change translator code to take them into account in addition to the component-specific deployment specs; add tests
[Optional] For consistency also do something similar to SecuredCluster schema/translator
Provide a high-level description for docs team