helm: accept parameters to globally configure image registry & pull secrets

[lmmarsano]

Enterprises often require private image registries that proxy public ones.
Configuring a different, authenticated registry should be as simple as configuring a custom repository for any common package manager.
We shouldn't have to track down & replace the entire name of every image to add a constant prefix.

Other helm charts commonly do this.
In the bitnami/wordpress chart notice global parameters

• global.imageRegistry
• global.imagePullSecrets

for global settings alongside higher precedence image-specific parameters

• image.registry
• image.pullSecrets

to override specific images.

Please do the same for all charts here to simplify deployments?

[exu]

It would help our users too 🥺

[ypoplavs]

Hello all, @wallyqs,
are there any updates on this issue?

[plamen-kutinchev]

Our company also needs a fix for this issue. Any updates?

[caleblloyd]

#606 will allow for the registry to be overridden on a per-image basis. Could look at adding global next

[caleblloyd]

Global Image Registry and Pull Policy are supported in nats-1.0.0-beta.0

Global Image pull secrets are not in there yet so I'll leave this open