envoyproxy/gateway

Use EDS instead of STRICT_DNS for Ratelimit Cluster in Envoy Gateway

Open

#6,992 opened on Sep 17, 2025

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (802 forks)auto 404
help wanted

Repository metrics

Stars
 (2,871 stars)
PR merge metrics
 (PR metrics pending)

Description

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.

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.