Add `imagePullSecrets` support for Custom Resources

[jurim76]

CRD supports image value only with predefined external registry. Sometimes access to registry is restricted to internal registry only, in this case you need to define imagePullSecrets or modify serviceAccount.

[Aym3nTN]

@jurim76 Can you provide more details? I'd like to help on this one

[jurim76]

CR should support imagePullSecrets directive

For example Define in CR yaml

image: "some.local.repo/dragonfly:v1.20.1"
imagePullSecrets:
  - name: regcred

The image will be pulled from some.local.repo, using "regcred" secret

[artsenko-cyco]

hi @Aym3nTN any ETA?

[mircea-pavel-anton]

I am also currently blocked by this, unable to even deploy an instance in my cluster since images from public repositories are not allowed...

@Aym3nTN Can I provide any assistance on this? Are you still working on it?

[Aym3nTN]

@mircea-pavel-anton I hadn't make significant progress. Feel free to work on it.

[mircea-pavel-anton]

I'll see if I can get something going sometime later next week!

[starek4]

After @jurim76 PR, it seems like the imagePullSecrets was being added here: https://raw.githubusercontent.com/dragonflydb/dragonfly-operator/main/manifests/dragonfly-operator.yaml, but it is missing in the latest release (e.g. dragonfly-operator-v1.1.10.tgz).