deckhouse / deckhouse/deckhouse
[vertical-pod-autoscaler] apply the flow-control to limit vpa patch-requests
Open
Nobody has claimed this yet.
area/kubernetes
type/enhancement
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 162
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 653
Description
Preflight Checklist
- I agree to follow the Code of Conduct that this project adheres to.
- I have searched the issue tracker for an issue that matches the one I want to file, without success.
Use case. Why is this important?
If there are lots of VPAs, they lead to lot's of PATCH-requests to the apiserver and, accordingly, etcd iops are growing.
Proposed Solution
Tune flow-control to limit PATCH requests to VPA resources and, probably, VPACheckpoints.
Additional Information
No response
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
Start by reviewing Kubernetes flow-control behavior and how the vertical pod autoscaler issues PATCH requests for VPA resources and VPACheckpoints. Determine the appropriate limits for apiserver requests and verify that PATCH traffic and associated etcd IOPS are constrained without disrupting VPA operation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100