Support custom header in registry about image

[mtrmac]

Thanks for your report.

That feature (assuming that’s https://github.com/dragonflyoss/helm-charts/blob/de67e651c0ce8dba76a284a5ef01eeb007d9b1cb/charts/dragonfly/values.yaml#L694-L695 ) does not make any sense to me.

How is an extra HTTP header better than adding a new DNS entry and a new virtual host to the server? (Or does that allow the client to use the mirror to contact any registry host at all, with no restrictions??)

Presumably clients would want to use the mirror system to access different backing registries simultaneously. So in that case every single pull operation would have to specify a custom header value? And that would propagate all over the call stack, to the skopeo and podman pull CLIs, and to Kubernetes Pod object definition , and to any other automation on top of Kubernetes?

Even if this were limited to mirrors configured in registries.d, and not intended to be used in podman pull, we would need a non-mirror mode for debugging / defining the mirror configuration.