chore: support 'imagePullSecrets' propagation

[heyvister1]

Added imagePullSecrets propagation helper function, to support the following options:

1. Current chart's .Values.imagePullSecrets
2. Root chart .Values.global.imagePullSecrets

[e0ne]

Why should we do this? we can propagate imagePullSecrets for this chart like we do for sriov operator in NVIDIA Network Operator project

[heyvister1]

Why should we do this? we can propagate imagePullSecrets for this chart like we do for sriov operator in NVIDIA Network Operator project

The motivation was to refrain of declaring imagePullSecrects: ["foo-secret"] multiple time in network-operator's values.yaml. And declare it once, globally. Otherwise, users will need to fill in its content per each sub-chart

[e0ne]

Why should we do this? we can propagate imagePullSecrets for this chart like we do for sriov operator in NVIDIA Network Operator project

The motivation was to refrain of declaring imagePullSecrects: ["foo-secret"] multiple time in network-operator's values.yaml. And declare it once, globally. Otherwise, users will need to fill in its content per each sub-chart

I really don't like the idea to change upstream API

[heyvister1]

Why should we do this? we can propagate imagePullSecrets for this chart like we do for sriov operator in NVIDIA Network Operator project

The motivation was to refrain of declaring imagePullSecrects: ["foo-secret"] multiple time in network-operator's values.yaml. And declare it once, globally. Otherwise, users will need to fill in its content per each sub-chart

I really don't like the idea to change upstream API

I can suggest this fix for upstream

[adrianchiris]

id suggest to do the opposite. having this skew is not good practice.

i.e suggest changes upstream and let them be synced back to this fork.

[almaslennikov]

I agree with @adrianchiris. I think that we should go with the same approach that we have for the SR-IOV operator for now and let's try to push this PR upstream first before doing any changes in the fork.

[heyvister1]

Will wait until this change is merged by kubernetes-sigs#2191