Provide `global.affinity` and `global.tolerations` options to apply for all kubevious components
- Dominant language
- Shell
- Stars
- 18
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
It will be convenient to have `global.affinity` and `global.tolerations` option so that we don't have to define them at each component
example:
```
global: {
affinity: {
nodeAffinity: {
requiredDuringSchedulingIgnoredDuringExecution: {
nodeSelectorTerms: [{
matchExpressions: [{
key: 'deployment',
operator: 'In',
values: ['my-affinity'],
}],
}],
},
},
},
tolerations: [{
effect: 'NoSchedule',
key: 'dedicated',
operator: 'Equal',
value: 'my-toleration',
}],
},
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Inspect the Helm chart's values and the templates for each Kubevious component, then compare how component-level affinity and tolerations are currently configured. Trace how values flow into rendered Kubernetes workloads and verify the rendered charts with the repository's available validation workflow. Done means the global options apply consistently to all components without requiring repeated component-specific settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100