add tolerations and nodeSelector to entire chart

[jassherman]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

---

Is your feature request related to a problem? Please describe.

We have taints on the specific cluster nodes and would like gossipEncryption to tolerate the nodes.

Feature Description

Use Case(s)

Adding tolerations and nodeSelector would allow for precise placement of the gossipEncryption pod.

Contributions

[jassherman]

Based on our configuration, we needed to add tolerations and nodeSelector to the following yamls:
gossip-encryption-autogenerate-job
tls-init-job
tls-init-cleanup-job

tls example
{{- if .Values.global.tls.tolerations }} tolerations: {{ tpl .Values.global.tls.tolerations . | indent 8 | trim }} {{- end }} {{- if .Values.global.tls.nodeSelector }} nodeSelector: {{ tpl .Values.global.tls.nodeSelector . | indent 8 | trim }} {{- end }}

[olegbzk]

The same problem: consul-tls-init pod is stuck with an error

0/8 nodes are available: 1 node(s) had untolerated taint {CriticalAddonsOnly: true}, 
1 node(s) had untolerated taint {company.com/purpose: argocd}, 
1 node(s) had untolerated taint {company.com/purpose: infra}, 
1 node(s) had untolerated taint {company.com/purpose: kafka}, 
4 node(s) had untolerated taint {company.com/purpose: application}. 
preemption: 0/8 nodes are available: 
8 Preemption is not helpful for scheduling.

[jassherman]

The toleration options are not available in the following yaml files, assuming you are using the helm chart.

gossip-encryption-autogenerate-job
tls-init-job
tls-init-cleanup-job

You need to edit each of these yaml files adding the code above in the correct format (the formatting is not correct above. Look at another yaml file for the correct formatting)

After you add the code to those three yamls, you need add the tolerations: and nodeSelector to the correct places in the values.yaml file.

[olegbzk]

I'm using the chart directly from the Hashicorp repo; there is no chance to edit YAML. No tolerations and nodeSelector in the code of tls-init-job

[jassherman]

I suggest you use helm pull to download the chart locally. Then you can update the yamls as describe above.