Fix memory limit #413
Closed
Fix memory limit #413
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CA has a known bug kubernetes/autoscaler#3506 The container consumes more memory than it is limited to. This fix will prevent issues with OOMKill errors with cluster-autoscaler container
nckturner
reviewed
Aug 3, 2021
| ``` | ||
| kubectl patch deployment cluster-autoscaler \ | ||
| -n kube-system \ | ||
| -p '{"spec":{"template":{"spec":{"containers":[{"name":"cluster-autoscaler","resources":{"limits":{"memory":"1000Mi"}}}]}}}}' |
There was a problem hiding this comment.
This should probably be left to configure for the customer, with perhaps a suggestion that makes it obvious it is not a 1-size fits all.
|
Page content has changed, with memory limits discussed more generally. It's up to the user to determine what's best for their environment. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CA has a known bug kubernetes/autoscaler#3506
The container consumes more memory than it is limited to.
This fix will prevent issues with OOMKill errors with cluster-autoscaler container
Issue #, if available:
kubernetes/autoscaler#3506
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.