envoyproxy / envoyproxy/gateway

Use EDS instead of STRICT_DNS for Ratelimit Cluster in Envoy Gateway

Abierto
#6,992 3 comentarios 0 reacciones 0 asignados Ver en GitHub
help wanted
Lenguaje dominante
Go
Estrellas
3k
Forks
864
Merge medio
2 d 2 h
PR fusionados (30 d)
140

Descripción

*Description*:
Currently, the ratelimit cluster that is spawned by Envoy Gateway uses the STRICT_DNS discovery type. However, since the Envoy Gateway is responsible for spawning and managing this service internally, it has full visibility into the ratelimit service and could instead use Endpoint Discovery Service (EDS) — which is the preferred and more dynamic method of service discovery in Envoy.

Using EDS provides several advantages:

- More flexible scaling and dynamic endpoint management.
- Avoids reliance on DNS resolution, which can have caching/staleness or timeout issues.
- Aligns with how other internally-managed services are typically handled in Envoy.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.