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
Which links every pod to every daemonsets, which is a but unfortunate.
Perhaps we can use the app.kubernetes.io/componentlabel to differentiate between pods from different daemonsets?
(add app.kubernetes.io/component to the spec.selector.matchLabels set and to spec.template.metadata.labels set)
As the chart already supports podExtraLabels per daemonset, another option would be to add some sort of extraSelectorLabels option and let the chart user create unique selector labels.
The text was updated successfully, but these errors were encountered:
The Helm chart allows you to define multiple daemonsets, which each a unique name. The (pod) selector for all daemonsets is the same though:
Which links every pod to every daemonsets, which is a but unfortunate.
Perhaps we can use the
app.kubernetes.io/component
label to differentiate between pods from different daemonsets?(add
app.kubernetes.io/component
to the spec.selector.matchLabels set and to spec.template.metadata.labels set)As the chart already supports
podExtraLabels
per daemonset, another option would be to add some sort ofextraSelectorLabels
option and let the chart user create unique selector labels.The text was updated successfully, but these errors were encountered: