envoy-gw 0.6.0 failed to install backend sample project

[ShyunnY]

Description:

When I install the backend project using in kubernetes
kubectl apply -f https://github.com/envoyproxy/gateway/releases/download/latest/quickstart.yaml -n default , the envoy-default-eg-xxx pod cannot start normally.

I use Kubernetes YAML installation envoy-gateway 0.6.0 version.

kubectl get pod -A

default                backend-564dd758c5-qq667                     1/1     Running            0               5m
envoy-gateway-system   envoy-default-eg-e41e7b31-5f556f7878-jgtwg   0/1     CrashLoopBackOff   5 (119s ago)    5m
envoy-gateway-system   envoy-gateway-55cd86c564-rbwm4               1/1     Running            0               8m16s
kube-system            calico-kube-controllers-85578c44bf-f4bgn     1/1     Running            3 (19m ago)     186d
kube-system            calico-node-bqc9t                            1/1     Running            1 (19m ago)     186d
kube-system            calico-node-ffnwv                            1/1     Running            3 (19m ago)     186d
kube-system            calico-node-ggchx                            1/1     Running            2 (19m ago)     173d
kube-system            coredns-7bdc4cb885-9w7lg                     1/1     Running            3 (19m ago)     186d
kube-system            coredns-7bdc4cb885-vlhzc                     1/1     Running            3 (19m ago)     186d
kube-system            etcd-master                                  1/1     Running            2 (19m ago)     172d
kube-system            kube-apiserver-master                        1/1     Running            3 (19m ago)     186d
kube-system            kube-controller-manager-master               1/1     Running            3 (19m ago)     172d
kube-system            kube-proxy-6jz4d                             1/1     Running            1 (19m ago)     186d
kube-system            kube-proxy-kssm4                             1/1     Running            3 (19m ago)     186d
kube-system            kube-proxy-tchd2                             1/1     Running            2 (19m ago)     173d
kube-system            kube-scheduler-master                        1/1     Running            3 (19m ago)     172d
metallb-system         controller-789c75c689-btqbl                  1/1     Running            2               25m
metallb-system         speaker-8dq55                                1/1     Running            1 (19m ago)     25m
metallb-system         speaker-crcj2                                1/1     Running            2 (19m ago)     25m
metallb-system         speaker-qh8gv                                1/1     Running            1 (19m ago)     25m

kubectl logs envoy-default-eg-e41e7b31-5f556f7878-jgtwg -n envoy-gateway-system

[2024-01-06 16:34:42.269][1][critical][main] [source/server/server.cc:117] error initializing configuration '': Protobuf message (type envoy.config.bootstrap.v3.Bootstrap reason INVALID_ARGUMENT:(common_tls_context.tls_certificate_sds_secret_configs[0].sds_config) path_config_source: Cannot find field.) has unknown fields
Protobuf message (type envoy.config.bootstrap.v3.Bootstrap reason INVALID_ARGUMENT:(common_tls_context.tls_certificate_sds_secret_configs[0].sds_config) path_config_source: Cannot find field.) has unknown fields

[optional Relevant Links:]

Any extra documentation required to understand the issue.

[ShyunnY]

It can be solved when I switch the eg gateway instance image version=envoy:1.28.0, but I find this very troublesome. Is there any way for me to configure it?

[tmsnan]

@ShyunnY, You can also use EnvoyProxy to customize bootstrap startup configuration.
https://gateway.envoyproxy.io/latest/user/customize-envoyproxy/#customize-envoyproxy-bootstrap-config

[arkodg]

@ShyunnY can you share the EnvoyProxy resource details ?

[ShyunnY]

@ShyunnY can you share the EnvoyProxy resource details ?

@arkodg I solved this problem, I modified the image configuration of EnvoyProxy. I think EnvoyProxy uses the dev stage image by default, which is a very confusing issue. And the official documentation does not point out this problem during the initial installation. This can make newbies very confused and find it difficult to find the problem.

[arkodg]

@ShyunnY EG uses the envoy dev images only for the main branch (which generates the v0.0.0-latest` helm tag). all releases are pinned to a specific envoy image https://gateway.envoyproxy.io/blog/2022/10/01/versions/ has the details