CPU vertical pod autoscaler for CrunchyDB
Open
4Refinement
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 21h 25m
- Merged PRs (30d)
- 70
Description
Defined a vertical pod autoscaling policy for crunchydb pods, to handle CPU spike for the multitude of jobs that write to the cluster.
AC
- [ ] Investigate maximum/minimum CPU usage/requests since deploying crunchy, using sysdig or prometheus queries to inform policy
- [ ] Define the policy as part of the crunchydb pod deployment using the above for maximums
Contributor guide
Research direction
Start by locating the existing CrunchyDB pod deployment and investigating CPU usage and requests since CrunchyDB was deployed, using Sysdig or Prometheus queries. Done means the observed maximums and minimums inform a vertical autoscaling policy defined as part of that deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql, prometheus
- Domain
- databases, infrastructure, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100