Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Lower memory usage of commons-operator

Open
#154 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
kubernetes, python
Domain
devops, infrastructure

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.

Description

customer-request priority/medium type/feature-improvement

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

Dominant language
Python
Stars
8
Forks
4
Avg merge
7h 48m
Merged PRs (30d)
7

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackabletech/commons-operator

All issues in stackabletech/commons-operator

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.