envoyproxy/gateway

Using `NodePort` + `externalTrafficPolicy: Local` should set `Spec.Addresses` to only the nodes where Envoy is running

Open

#9,528 opened on Jul 20, 2026

View on GitHub
 (1 comment) (0 reactions) (1 assignee)Go (802 forks)auto 404
help wantedkind/bug

Repository metrics

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

Description

Description: When EnvoyProxy has type: NodePort:

  spec:
    provider:
      kubernetes:
        envoyService:
          externalTrafficPolicy: Local
          type: NodePort

all node addresses appear in Status.Addresses. But with externalTrafficPolicy: Local, the default, traffic is only routed to Envoy if it arrives at a node where there is a replica truly running. Only these addresses should appear in Status.Addresses

Repro steps: See above

Environment: Latest gateway version

Contributor guide

Research direction
Inspect the code that populates Status.Addresses for NodePort services. Understand the handling of externalTrafficPolicy: Local and filter addresses to only nodes running Envoy pods. Add tests covering this scenario.
Tech stack
go
Domain
backend
Issue type
Bug
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
GitGoKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60