The team is deploying gitops-promoter via the Helm chart and noticed that the kube-rbac-proxy container image is hardcoded in the template:
In some environments, it is required to:
Use a private registry
Pin a different version
Mirror images internally
Override the image tag for security or compliance reasons
Because the image is not configurable, users cannot adapt the deployment to their environment requirements.
Suggested Improvement
Expose the kube-rbac-proxy image configuration in values.yaml, similar to how the main controller image is configurable.
The team is deploying gitops-promoter via the Helm chart and noticed that the kube-rbac-proxy container image is hardcoded in the template:
In some environments, it is required to:
Use a private registry
Pin a different version
Mirror images internally
Override the image tag for security or compliance reasons
Because the image is not configurable, users cannot adapt the deployment to their environment requirements.
Suggested Improvement
Expose the kube-rbac-proxy image configuration in values.yaml, similar to how the main controller image is configurable.