StreamEndpoints gRPC config stream to contour closed since

[I-Abdelhamid]

What steps did you take and what happened:
Envoy pods sometimes fail requests When I checked the logs for Envoy pods I found the following.
The case is not permanent it happens only once or twice a day leading to timeout client requests
[warning][config] [./source/common/config/grpc_stream.h:201] StreamEndpoints gRPC config stream to contour closed since 80s ago: 14, upstream connect error or disconnect/reset before headers. reset reason: connection failure, transport failure reason: delayed connect error: 111

the logs directly before the issue
shutting down parent after drain

What did you expect to happen:
I want to understand why the connection is close between contour and envoy proxies and how to fix it

Environment:

• Contour version: 1.25.0
• Kubernetes version: v1.25.15-eks
• Cloud provider or hardware configuration: aws
• OS (e.g. from /etc/os-release): using bitnami/contour image

[github-actions]

Hey @I-Abdelhamid! Thanks for opening your first issue. We appreciate your contribution and welcome you to our community! We are glad to have you here and to have your input on Contour. You can also join us on our mailing list and in our channel in the Kubernetes Slack Workspace

[github-actions]

The Contour project currently lacks enough contributors to adequately respond to all Issues.

This bot triages Issues according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the Issue is closed

You can:

• Mark this Issue as fresh by commenting
• Close this Issue
• Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

[github-actions]

The Contour project currently lacks enough contributors to adequately respond to all Issues.

This bot triages Issues according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the Issue is closed

You can:

• Mark this Issue as fresh by commenting
• Close this Issue
• Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack