Skip to content

Increase default cpu/memory limits for the operator - #3831

Merged
J12934 merged 1 commit into
secureCodeBox:mainfrom
J12934:fix/increase-default-cpu-memory-limits-for-the-operator
Sep 15, 2026
Merged

J12934 merged 1 commit into
secureCodeBox:mainfrom
J12934:fix/increase-default-cpu-memory-limits-for-the-operator

Conversation

@J12934

@J12934 J12934 commented Sep 15, 2026

Copy link
Copy Markdown
Member

Description

30Mi is really low and not sufficient for a lot of setups.

100Mi is still rather low, but the extra 70Mi should really be no problem for anybody, even with the current memory price hike

This was also causing problems with local developments as docker seems to messure the resoruces of ressurected / restarted containers differently causing the operator to fail on kind cluster if the computer/docker engine was shut down / restarted

Checklist

  • Test your changes as thoroughly as possible before you commit them. Preferably, automate your test by unit/integration tests.
  • Make sure that all your commits are signed-off and that you are added to the Contributors file.
  • Make sure that all CI finish successfully.
  • Optional (but appreciated): Make sure that all commits are Verified.

@J12934 J12934 self-assigned this Sep 15, 2026
@J12934 J12934 added the bug Bugs label Sep 15, 2026
@netlify

netlify Bot commented Sep 15, 2026

Copy link
Copy Markdown

Deploy Preview for docs-securecodebox canceled.

Name Link
🔨 Latest commit 970d7b3
🔍 Latest deploy log https://app.netlify.com/projects/docs-securecodebox/deploys/6aa95c05559e2d0008266926

@J12934 J12934 moved this from Triage to To Review in secureCodeBox Sep 15, 2026
@github-project-automation github-project-automation Bot moved this from To Review to Reviewer Approved in secureCodeBox Sep 15, 2026
@Weltraumschaf
Weltraumschaf force-pushed the fix/increase-default-cpu-memory-limits-for-the-operator branch from d988027 to 4498cce Compare September 15, 2026 09:28
30Mi is really low and not sufficient for a lot of setups.

100Mi is still rather low, but the extra 70Mi should really be no
problem for anybody, even with the current memory price hike

This was also causing problems with local developments as docker seems
to messure the resoruces of ressurected / restarted containers
differently causing the operator to fail on kind cluster if the
computer/docker engine was shut down / restarted

Signed-off-by: Jannik Hollenbach <[email protected]>
@J12934
J12934 force-pushed the fix/increase-default-cpu-memory-limits-for-the-operator branch from 4498cce to 970d7b3 Compare September 15, 2026 14:53
@sonarqubecloud

Copy link
Copy Markdown

@J12934
J12934 merged commit 0da24ce into secureCodeBox:main Sep 15, 2026
49 checks passed
@github-project-automation github-project-automation Bot moved this from Reviewer Approved to Done in secureCodeBox Sep 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Bugs

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants