Introduce max pod age to Queue Proxies
Open
Nobody has claimed this yet.
area/autoscale
good first issue
help wanted
kind/feature
lifecycle/frozen
triage/accepted
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 1.2k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 2
Description
In what area(s)?
/area autoscale
/kind proposal
Describe the feature
We can introduce maxPodAge setting to queue proxies in order for them to commit suicide at some point, to ensure that the end app is built against pod restarts and network connections being broken (e.g. real life).
/cc @mattmoor
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points; begin by locating the queue proxy configuration and lifecycle code. Define how maxPodAge should control proxy restarts, including the intended behavior when network connections break, and add tests that demonstrate the setting and its completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100