Kuma DP image pull secret is missing

[brunda-bs]

What happened?

Hi,

We are using a private registry to pull the Kuma DP image using an image pull secret. The global image pull secret configuration works fine for Kuma CP, ingress, and egress. However, for Kuma DP, The global image pull secret specified in the Kuma Helm chart is not present in the application pod configuration being generated.

Some app pods come up because the image is present on the node, as the image pull policy is "IfNotPresent." Even though "Always" has been set in the Helm chart, it's not being overridden.

We encounter image pull back off errors for delegated gateway pods as well as it uses kuma-dp.