envoyproxy/envoy

Envoys do not use previous secret discovery provider when fetch timeout is changed

Open

#46,155 opened on Jul 15, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/sdsarea/xdsbughelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

Title: Envoys do not use previous secret discovery provider when fetch timeout is changed

Description: This is an identical issue to https://github.com/envoyproxy/envoy/issues/32283 but for SDS instead. A change in the fetch timeout on the SDS config provider causes the SDS secrets to be discarded and request new SDS secrets. However the control plane does not receive the fetch timeout as part of the secret request so it does not send the secrets again.

This causes the secret discovery provider to stop until the fetch timeout occurs and the listener finally warms. At that point new connections are rejected until either the envoy is restarted or the secret is changed.

Repro steps: I have a PR with a repro and fix in https://github.com/envoyproxy/envoy/pull/46154

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.