add memory request to kube-apiserver and operator pods #161
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
openshift-ci-robot
added
the
size/XS
sjenning
changed the title
|
/retest |
1 similar comment
|
/retest |
|
Better than no requests at all. We can increase if we see need. /lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sjenning, sttts The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
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.
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
BestEffortgiving the scheduler no information on pod resource usage.On a steady state empty cluster,
kube-apiserveruses 980Mi.{pod_name="openshift-kube-apiserver-dev-master-0"} | 979714048
Setting request to
1Gi.This component uses the most memory and CPU of any component. Possible target for future optimization.
@deads2k @sttts @derekwaynecarr