envoyproxy/gateway

Support forward_proto_config for K8s Gateway API

Open

#9,219 opened on Jun 13, 2026

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Go (802 forks)auto 404
help wantedkind/feature

Repository metrics

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

Description

Description: Envoy has this forward_proto_config feature to infer the x-forwarded-proto from PROXY protocol destination port, but this feature is not exposed in K8s Gateway API so it can't be configured. We'd like to request this feature to be exposed and configurable.

[optional Relevant Links:] https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_conn_man/headers#inferring-x-forwarded-proto-from-proxy-protocol-destination-port https://github.com/envoyproxy/envoy/issues/43031

Contributor guide

Research direction
Investigate how forward proto config is implemented in Envoy and how it can be exposed via the Gateway API. Look at existing configuration patterns in the repository for similar features like header manipulation or routing configuration.
Tech stack
go
Domain
backendinfrastructureapi
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.
1-2 days
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
GoKubernetesEnvoy
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50