image registry not consistent across resources #4626
Description
Description:
Envoy gateway controller uses defined registry in manifest compared to automatically deployed proxy deployments that miss registry in image specification.
image: docker.io/envoyproxy/gateway:v1.1.2
vs
image: envoyproxy/envoy:distroless-v1.31.2
This causes proxy pods end up in ImageInspectError at clusters without set default registry.
It does not seem that repository for proxy deployment is configurable through helm.
Repro steps:
Follow installation docs.
Create gateway and httproute resources.
Check image specifications of deployments.
Environment:
envoy 1.1.2
kubernetes v1.29.5
Logs:
k get po -n envoy-gateway-system
NAME READY STATUS RESTARTS AGE
envoy-default-gateway-numerotres-de8f529f-7796bdd6f7-8gl5h 1/2 ImageInspectError 0 41m
envoy-envoy-gateway-system-gateway-numerodos-b28dbb2b-5d7c79x9k 1/2 ImageInspectError 0 41m
envoy-envoy-gateway-system-gateway-numerouno-c84cb3be-6b5bgsfmb 1/2 ImageInspectError 0 41m
envoy-gateway-655745744f-kmr6z 1/1 Running 0 128m
k describe po -n envoy-gateway-system | grep Image
Image: envoyproxy/envoy:distroless-v1.31.2
Image ID:
Reason: ImageInspectError
Image: docker.io/envoyproxy/gateway:v1.1.2
Image ID: ecdd82f22c5367f9c8168c60a4a289a92b756d436faa370c45cb6c5a48212a38
Warning Failed 40m (x10 over 41m) kubelet Error: ImageInspectError
Image: envoyproxy/envoy:distroless-v1.31.2
Image ID:
Reason: ImageInspectError
Image: docker.io/envoyproxy/gateway:v1.1.2
Image ID: ecdd82f22c5367f9c8168c60a4a289a92b756d436faa370c45cb6c5a48212a38
Warning Failed 40m (x10 over 41m) kubelet Error: ImageInspectError
Image: envoyproxy/envoy:distroless-v1.31.2
Image ID:
Reason: ImageInspectError
Image: docker.io/envoyproxy/gateway:v1.1.2
Image ID: ecdd82f22c5367f9c8168c60a4a289a92b756d436faa370c45cb6c5a48212a38
Warning Failed 40m (x10 over 41m) kubelet Error: ImageInspectError
Image: docker.io/envoyproxy/gateway:v1.1.2
Image ID: ecdd82f22c5367f9c8168c60a4a289a92b756d436faa370c45cb6c5a48212a38