Allow setting Registry endpoint's Authorization header token as a k8s secret
The following discussion from !1225 (merged) should be addressed:
@ggillies started a discussion: (+1 comment)
Can we please add support for the "endpoints.header.Authorization" field to come from a Kubernetes secret object, instead of just coming straight from the values passed to the chart? We won't be able to use this functionality for gitlab.com unless that credential is stored safely in a Kubernetes secret object
@twk3's reply
lets remove the Auth headers examples from this MR. And open an issue tackle this. I think it should be a followup as it will likely be rather complicated.
- Helm doesn't read the k8s secrets, the container does, so we can't use the helm templates to help us do this replacement.
- The current init image for this container is busybox. Leaving us with pretty much only having
sed
to be able to do this. It's likely time to switch to a different image. (Our kubectl one has yq, or maybe we need to build a new one)