envoyproxy / envoyproxy/gateway

Use EDS instead of STRICT_DNS for Ratelimit Cluster in Envoy Gateway

Offen
#6,992 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
help wanted
Vorherrschende Sprache
Go
Sterne
3k
Forks
864
Ø Merge
2 T. 2 Std.
Gemergte PRs (30 T.)
140

Beschreibung

*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.

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.