envoyproxy / envoyproxy/gateway

Support restricting Listener address to `podIPs`

Open
#9,535 4 comments 0 reactions 0 assignees View on GitHub
triage
Dominant language
Go
Stars
3k
Forks
864
Avg merge
1d 22h
Merged PRs (30d)
148

Description

*Description*:
Right now it's a static "all addresses". Restricting to pod IPs would be much cleaner. Especially important if the gateway is running in `hostNetwork` mode where using all addresses can cause collisions.

Contributor guide

No contributing guide indexed for this repository

Research direction

Trace the Kubernetes gateway implementation for Listener address handling and pod IP discovery, then identify the existing tests covering listener binding. Add support for restricting a Listener to pod IPs, and verify that hostNetwork deployments no longer bind all addresses while existing listener behavior remains intact.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
networking
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.