Dapr Operator Not Utilizing Global Image Pull Secret

[kishanTakeda]

Issue Description:

When executing the following Helm upgrade command to pull the Dapr image from a custom image directory and configuring the global image pull secret, the Dapr operator is not utilizing the provided global image pull secret (dapr-imagepull-secret). Instead, it's creating its own operator secret.

Command Executed:

helm upgrade --install dapr --version 1.7.6 dapr/dapr --namespace dapr-system --set global.registry=<custom registry> --set global.imagePullSecrets=dapr-imagepull-secret

Expected Behavior:
The Dapr operator should use the provided global image pull secret (dapr-imagepull-secret) to pull images from the specified registry (custom registry).

Actual Behavior:
The Dapr operator is not utilizing the provided global image pull secret and is instead creating its own operator secret.

Steps to Reproduce:

1. Execute the above Helm upgrade command with the specified parameters.
2. Verify the secrets created and check if the Dapr operator is using the global image pull secret.

Additional Information:

• Kubernetes version: v1.25.12+ba5cc25
• Openshift version- 4.12.36
• Dapr version: 1.7.6

[kishanTakeda]

@yaron2 we discussed this on Discord channel , could you please suggest if this is default behavior of dapr operator to create custom secret?

[dapr-bot]

This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.