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

[TASK] Adjust resources defaults for the unified Core deployment #2583

Open
jessesimpson36 opened this issue Nov 18, 2024 · 1 comment
Open

Comments

@jessesimpson36
Copy link
Contributor

Describe the use case:

In 8.7-alpha, we introduced a new "core" deployment type which will combine zeebe, operate, and tasklist . However, we still have the same resource requests and limits that zeebe had before despite it needing to respond to operate and tasklist requests and perform the steps that the operate importer and exporter would normally do.

Describe the enhancement/feature:

I would suggest we take the requests and limits for each application, and add them together for our new requests and limits for the core deployment. I would be open for other suggestions as well for what those requests and limits should be.

One minor concern I have about bumping these numbers up is that this may prevent scheduling the core deployment on nodes that do not meet the requests. So any solution we come up with for this issue should take that into account.

Desired outcome and acceptance tests:

@jessesimpson36 jessesimpson36 added the kind/enhancement New feature or request label Nov 18, 2024
@ChrisKujawa
Copy link
Member

@aabouzaid aabouzaid changed the title [ENHANCEMENT] adjust resources + limits for core deployment since it now has responsibilities of operate, zeebe, and tasklist [ENHANCEMENT] Adjust resources defaults for the unified Core deployment Nov 19, 2024
@aabouzaid aabouzaid changed the title [ENHANCEMENT] Adjust resources defaults for the unified Core deployment [TASK] Adjust resources defaults for the unified Core deployment Nov 19, 2024
@aabouzaid aabouzaid added kind/task and removed kind/enhancement New feature or request labels Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants