stackabletech / stackabletech/commons-operator
Lower memory usage of commons-operator
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8
- Forks
- 4
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 7
Description
Currently the memory required by the commons-operator scales with the amount of Pods in a K8s cluster.
This can lead to more or less unbounded memory usage.
We need to investigate how we can limit this.
One possibility to limits this is by leveraging the work that will be done in https://github.com/stackabletech/issues/issues/188
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. Start by reading the linked Stackable issue #188 and measuring how commons-operator memory changes with the number of Pods in a cluster. Done should be a decided, bounded-memory approach with evidence that it addresses the reported scaling behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, python
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100