argoproj / argoproj/argo-workflows
Limit total number of pods created by the controller
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 138
Description
# Summary
Kubernetes clusters often max out with a number of scheduled running pods. For us, limiting this to 5k allow us to protect ourselves.
# Use Cases
Prevent broken clusters. Protect other cluster users.
---
**Message from the maintainers**:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
Contributor guide
Research direction
Start by reviewing the issue and merged pull request #4892, including its discussion and changed behavior. Check whether the merged work addresses the requested five-thousand-pod limit and what remains, then identify the relevant controller entry point and tests before defining completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100