add memory request to kube-controller-manager and operator pod #106
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.
One in a series of PRs to set memory requests for all control plane and high memory use components.
We are encountering master instability (openshift/installer#408 openshift/installer#785) as the number of components increase because many components run
BestEffort
giving the scheduler no information on pod resource usage.On a steady state empty cluster,
kube-controller-manager
uses 143MB.{pod_name="openshift-kube-controller-manager-dev-master-0"} | 142659584
Because it is a control plane component, I'm giving it a buffer and setting to
200Mi
@deads2k @sttts @derekwaynecarr