envoyproxy/gateway

Make Extension manager support Gateway specific

Open

#7,696 opened on Dec 8, 2025

View on GitHub
 (7 comments) (0 reactions) (0 assignees)Go (802 forks)auto 404
area/apihelp wanted

Repository metrics

Stars
 (2,871 stars)
PR merge metrics
 (Avg merge 14d 16h) (153 merged PRs in 30d)

Description

Currently for AI gateway installation, we are adding global controller configs patches

1.ai-gateway extension manager config: https://github.com/envoyproxy/ai-gateway/blob/main/manifests/envoy-gateway-values.yaml 2. Ratelimit config: https://github.com/envoyproxy/ai-gateway/blob/main/examples/token_ratelimit/envoy-gateway-values-addon.yaml 3.Inferencepool backend resources: https://github.com/envoyproxy/ai-gateway/blob/main/examples/inference-pool/envoy-gateway-values-addon.yaml

Can these configs be made gateway specific so that there is no need to patch the controller?(which is a problem in central envoy installations)

Contributor guide

Research direction
Investigate the current approach for applying extension manager configs globally and explore ways to make them gateway specific, such as adding a gateway level configuration field or using annotations.
Tech stack
go
Domain
backendinfrastructurenetworking
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50