apache / apache/pulsar-helm-chart
Add the possibility to set NodeAffinity
- Dominant language
- Shell
- Stars
- 240
- Forks
- 260
- Avg merge
- 4h 12m
- Merged PRs (30d)
- 1
Description
**Is your feature request related to a problem? Please describe.**
We work in GKE and in our cluster have several nodepools. When we need to change the nodepool where pulsar is deployed, we have to cordon nodes to make pulsar deployed where we want.
**Describe the solution you'd like**
Add NodeAffinity configuration in templates and in values.yaml to be able to specify nodes where pulsar's components must be deployed.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with values.yaml and the chart's templates to see how Pulsar components are configured and rendered. Trace each component deployment and verify the rendered Helm manifests accept configurable node affinity. Done means users can specify node placement for the relevant Pulsar components without cordoning nodes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100