Support multiple image pull secrets in Helm values

[aeroyorch]

Description

Currently, the Helm chart allows specifying only a single image pull secret via the field:

registry:
  secretName: my-secret

I possible proposal would be:

• Allowing registry.secretName to accept a list of strings, or
• Introducing a new key such as registry.secretNames: [] to define multiple secrets.

Always ensuring backward compatibility.

Use case/motivation

In some environments, Airflow images and sidecar containers are pulled from multiple private registries. Kubernetes supports specifying multiple image pull secrets natively, but the Helm chart currently limits this flexibility.

By supporting multiple pull secrets, users could pull images from different private registries.

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.