I have a use-case where I pull images using a proxy-first approach to prevent reaching Docker Hub pull rate limits
Currently, the image names in the Helm templates (API, Front, Worker) are hardcoded as getlago/api or getlago/front. This prevents users from prepending a private registry or proxy URL.
Proposed solution is to introduce a registry variable in values.yaml e.g., image.registry that can be prepended to the image path in the deployment templates.
I have a use-case where I pull images using a proxy-first approach to prevent reaching Docker Hub pull rate limits
Currently, the image names in the Helm templates (API, Front, Worker) are hardcoded as getlago/api or getlago/front. This prevents users from prepending a private registry or proxy URL.
Proposed solution is to introduce a registry variable in values.yaml e.g., image.registry that can be prepended to the image path in the deployment templates.