Fix resource issues with workbench session pods
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
Currently our nodes (on some workloads at least) are running 4 cpu and 16 gb of memory. We allow session pods to be created up to size large of 4 cpu and 8gb of memory. The requests are also extremely low, meaning Kubernetes thinks there is plenty of room on a node to schedule a new session pod based on the requests, then as soon as the memory spikes we see things crash. Two large or 4 medium session pods are already over the memory limit, not to mention all the other things that need to run on that node. Need to rethink these resource requests and limits, and also probably adjust our standard node sizes.
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. Start by locating the session pod resource configuration and the standard node-size configuration, then compare their requests and limits with the workloads described. Done means the resource settings and node sizing no longer allow memory overcommit that causes session pods or other node workloads to crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100