I cannot define a separate nodeSelector for the metrics-agg.
Existing implementation assumes that the metrics daemonset and the metrics-agg will requirement the same nodeSelector configuration.
However, this may not always be the case. For example, I want to keep management workloads on a set of management nodes. The metrics-agg deployment will count as a management workload. However, I still want to have the metrics daemonset running on all my nodes to collect metrics. With the current template this is not possible and the .Values.nodeSelector is common for both the metrics daemonset and the metrics-agg deployment.
What you expected to happen:
I should be able to have separate nodeSelector for the metrics-agg
How to reproduce it (as minimally and precisely as possible):
Just try to define a separate nodeSelector for the metrics-agg
What happened:
I cannot define a separate
nodeSelector
for the metrics-agg.Existing implementation assumes that the metrics daemonset and the metrics-agg will requirement the same nodeSelector configuration.
However, this may not always be the case. For example, I want to keep management workloads on a set of management nodes. The metrics-agg deployment will count as a management workload. However, I still want to have the metrics daemonset running on all my nodes to collect metrics. With the current template this is not possible and the
.Values.nodeSelector
is common for both the metrics daemonset and the metrics-agg deployment.What you expected to happen:
I should be able to have separate nodeSelector for the metrics-agg
How to reproduce it (as minimally and precisely as possible):
Just try to define a separate
nodeSelector
for the metrics-aggAnything else we need to know?:
Environment:
kubectl version
):ruby --version
):cat /etc/os-release
):