helm chart should move nodeSelector to each section and possibly default to a global nodeSelector #7132
Unanswered
iamasmith
asked this question in
Error / Bug Report
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Also, affinity/taint toleration handling would be good.
One of my home lab clusters has amd64 and arm64 nodes and I do not taint the arm64 nodes, preferring to treat them equal and use nodeSelector on kubernetes.io/arch label either way which has worked very well with most software deployed.
The helm chart has a global nodeSelector value but it passes this on to the wiki.js container only and not to the PostgreSQL container.
The upshot of this is that the PostgreSQL statefulset can land on the arm64 nodes where it appears not to work becaue the image specified isn't an arm64 image.
Using a tag with arm64 images (if available) would duck the problem - nodeSelectors are there to precisely control placement without the requirement for taints and tolerations. Charts delivering multiple workloads should allow one to specify nodeSelector and preferrably also tolerations if that approach has been used to schedule the workloads accordingly.
Workaround for now is to deploy PostgreSQL indepdendently with a more targetted means.
Beta Was this translation helpful? Give feedback.
All reactions