envoyproxy/gateway

shutdown-manager does not have default limit

Open

#7,550 opened on Nov 18, 2025

View on GitHub
 (7 comments) (1 reaction) (0 assignees)Go (802 forks)auto 404
help wanted

Repository metrics

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

Description

it been complain by some scaner. We could add a deployment patch in each EnvoyProxy, but I think it’s also quite reasonable to set a default instead. The shutdown-manager should never consume much memory or CPU. setting a limit of 1 core and 1 GB should be sufficient.

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.