superset
superset copied to clipboard
fix(helm): add nodeselector and tolerations to init job
SUMMARY
- Fixes issue #18004 adding a node selector and toleration to the init job configurable in the values file.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
N/A
TESTING INSTRUCTIONS
- Set the nodeselector, toleration and affinity to the
init
block in thevalues.yaml
file.
## Node selector to be added to init job pods
nodeSelector:
role: test-nodeselector
## Tolerations to be added to init job pods
tolerations:
- key: role
operator: Equal
value: test-toleration
## Affinity to be added to init job pods
affinity: {}
ADDITIONAL INFORMATION
- [x] Has associated issue:
- [ ] Required feature flags:
- [ ] Changes UI
- [ ] Includes DB Migration (follow approval process in SIP-59)
- [ ] Migration is atomic, supports rollback & is backwards-compatible
- [ ] Confirm DB migration upgrade and downgrade tested
- [ ] Runtime estimates and downtime expectations provided
- [ ] Introduces new feature or API
- [ ] Removes existing feature or API
@nytai @zhaoyongjie @craig-rueda the linter is failing due to a chart version mismatch, should I bump the version to 0.5.6
Hello
I have exactly the same problem
Can you apply this modification in the next version of the chart?
Im with the same problem :(
It looks like this PR still needs a version bump.
@zhaoyongjie Can we merge it?
@jakedsouza why was the PR closed?
I have applied the toleration and nodeSelector to the pods. all pods have the desired toleration and nodeSelector except for Redis pod. I haven't set up any caching config. it is deployed as it is in the 'values.yaml' file. What needs to be done to apply these setting to Redis pod?
Hi,
I setup: nodeSelector: nodetype: core-ccx23
but it applies only for superset and worker.
Redis and Postgresql with out node-selector.
How to fix that?