-
Notifications
You must be signed in to change notification settings - Fork 506
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
It is not possible to adjust arbiter's resource limits separately from cluster nodes #962
Comments
This issue is being marked stale because it has been open for 60 days with no activity. Please comment if this issue is still affecting you. If there is no change, this issue will be closed in 30 days. |
Not stale, still not possible |
This issue is being marked stale because it has been open for 60 days with no activity. Please comment if this issue is still affecting you. If there is no change, this issue will be closed in 30 days. |
Still relevant. |
Still relevant |
Hi, this isn't currently on our roadmap, but we do see the value in what's being asked. We will do this at some point, but no current estimate for when. |
any update for this issue ? |
Please implement the feature. I need to set Guaranteed QoS on mongo pods, but I can't reserve the same amount of CPUs for arbiter. It should be enough to modify this part |
We can not adjust resource limits for arbiter itself. Currently, it is just wasting resources, because we need arbiter only for election
Expected behavior:
We should be able to adjust it separately.
Currently, we use such yaml:
The text was updated successfully, but these errors were encountered: