You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the usage of a daemonset is no longer strictly necessary. originally, the daemonset was used in order to add labels to individual pods for use with podAffinity in order to have argo target nodes that already had the images pre-pulled, however that's actually already a factor in the kubernetes scheduler algo
we can swap to using a deployment instead and reduce the number of controller pods that we need down to 1, although we would need to add privileges to get/list/watch nodes, and we lose the ability to target specific nodes for image pre-pulling which could be implemented taints/tolerations/nodeSelector on the daemonset right now.
The text was updated successfully, but these errors were encountered:
the usage of a daemonset is no longer strictly necessary. originally, the daemonset was used in order to add labels to individual pods for use with
podAffinity
in order to have argo target nodes that already had the images pre-pulled, however that's actually already a factor in the kubernetes scheduler algowe can swap to using a deployment instead and reduce the number of controller pods that we need down to 1, although we would need to add privileges to get/list/watch nodes, and we lose the ability to target specific nodes for image pre-pulling which could be implemented taints/tolerations/nodeSelector on the daemonset right now.
The text was updated successfully, but these errors were encountered: