-
Notifications
You must be signed in to change notification settings - Fork 15.1k
add LimitRange section, make small improvements to the VPA write-up #53395
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
base: main
Are you sure you want to change the base?
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Welcome @iamzili! |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
/sig autoscaling |
|
|
||
| See [requests and limits](/docs/concepts/configuration/manage-resources-containers/#requests-and-limits) to learn more about those two concepts. | ||
|
|
||
| ## LimitRange resouces |
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.
Typo
| ## LimitRange resouces | |
| ## LimitRange resources |
Description
I propose small improvements to the new VPA write-up and suggest adding a section about LimitRange resources.
Issue
This issue relates to the one created in the
autoscalergit repository, but it does not necessarily close it: kubernetes/autoscaler#8839