Replies: 1 comment
-
|
is the Envoy proxy on the node with the controller? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The Envoy proxy deployment created by Envoy Gateway is not becoming ready. The pod is stuck in a degraded state with only 1/2 containers ready, and the deployment reports ProgressDeadlineExceeded.
From logs, Envoy is unable to connect to the xDS server (envoy-gateway service), resulting in repeated gRPC connection timeouts.
Envoy Gateway version: v1.7.2
Envoy image: docker.io/envoyproxy/envoy:distroless-v1.37.2
Kubernetes version: v1.32.5 (On-Prem)
Logs:
[warning][config] gRPC config: initial fetch timed out for type.googleapis.com/envoy.config.endpoint.v3.ClusterLoadAssignment
DeltaAggregatedResources gRPC config stream to xds_cluster closed:
upstream connect error or disconnect/reset before headers.
reset reason: connection timeout
Envoy is configured to connect to xDS server:
envoy-gateway.envoy-gateway-system.svc.cluster.local:18000
Beta Was this translation helpful? Give feedback.
All reactions