You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered: