Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

increase CAPMVM manager default resources #258

Open
fire-ant opened this issue Feb 22, 2023 · 0 comments
Open

increase CAPMVM manager default resources #258

fire-ant opened this issue Feb 22, 2023 · 0 comments
Labels
kind/bug Something isn't working priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@fire-ant
Copy link

What happened:
During the initial rollout of CAPMVM we noticed that the manager was crashlooping. We had only one resource to reconcile and no pre-existing clusters or any interfering objects configured in the same namespace. The logical choice was bumping the controller resources from cpu 100m /mem 30m until we felt like the controller was stable. once we reached 300m / 300m the controller began and continued without restart. We doubled every time so Im sure it can be tuned lower.

What did you expect to happen:
CAPMVM to stay up without issue

How to reproduce it:

provide a single resource after deploying on existing deployment resources.

Anything else you would like to add:

but would like to performance

Environment:
6 node virtualised cluster. nodes are 4 core 16Gb RAM.

  • capmvm version:
    v0.8.0

  • OS (e.g. from /etc/os-release):
    Ubuntu 20.04

@fire-ant fire-ant added the kind/bug Something isn't working label Feb 22, 2023
@Callisto13 Callisto13 added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Feb 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

2 participants