Set resources requests/limits on ptd's k8s workloads
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
This may be a little trial and error, but we should set some level of sane and logical resource requests and limits on our workloads in kubernetes rather than having nothing set for most things. This is related to PTD owned stuff like mimir, loki, system level stuff running from helm charts, team-operator, etc.
Not counting workbench session pods, those do have values set and there's a separate ticket for optimizing them.
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 inventorying the Kubernetes workloads named in the issue: Mimir, Loki, system-level Helm charts, and team-operator. Review their current resource configuration and compare it with the existing workbench session pod values, which are out of scope. Done means the PTD-owned workloads have sane requests and limits without changing workbench session pods.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100