Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with Helm Template: kube-rbac-proxy Image Hardcoded #828

Open
gioarag opened this issue Nov 4, 2024 · 0 comments
Open

Issue with Helm Template: kube-rbac-proxy Image Hardcoded #828

gioarag opened this issue Nov 4, 2024 · 0 comments

Comments

@gioarag
Copy link

gioarag commented Nov 4, 2024

I have encountered an issue with the Helm Template for the kube-egress-gateway. The image for the kube-rbac-proxy is hardcoded to gcr.io/kubebuilder/kube-rbac-proxy, which prevents the gatewayControllerManager.imageRepository parameter from being effective. This limits the flexibility to specify a different image repository for the kube-rbac-proxy.

Steps to Reproduce:

Deploy the kube-egress-gateway using the provided Helm Template.
Attempt to override the gatewayControllerManager.imageRepository parameter.
Expected Behavior: The gatewayControllerManager.imageRepository parameter should allow specifying a different image repository for the kube-rbac-proxy.

Actual Behavior: The kube-rbac-proxy image remains hardcoded to gcr.io/kubebuilder/kube-rbac-proxy, ignoring the gatewayControllerManager.imageRepository parameter.

kube-egress-gateway Version: v0.0.17
Helm Chart Version: 0.1.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant