-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add resources to our system components. #2532
Conversation
These values were determined from the graphs in the linked issue, which are from a knative/serving install running the e2e/conformance testing multiple times. Fixes: knative#2393
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Glad to see this.
LGTM as they should have been widely verified.
I'm thinking since we begin to care about practical issues. There can be more topics to consider.
e.g. we might want to set proper priority for components pods, so that they won't get evicted.
And also, the leader selection issue I mentioned before #2111
/retest |
/test pull-knative-serving-integration-tests |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mattmoor, mdemirhan 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 |
These values were determined from the graphs in the linked issue, which are from a knative/serving install running the e2e/conformance testing multiple times. Fixes: knative#2393
These values were determined from the graphs in the linked issue, which are from a knative/serving install running the e2e/conformance testing multiple times.
Fixes: #2393