-
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
Conversation
|
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 |
content/en/docs/concepts/workloads/autoscaling/vertical-pod-autoscale.md
Outdated
Show resolved
Hide resolved
omerap12
left a comment
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.
Overall LGTM, just a few comments
| The Recommender analyzes both current and historical resource usage data (CPU and memory) for each Pod targeted by the VerticalPodAutoscaler. It examines: | ||
| - Historical consumption patterns over time to identify trends | ||
| - Peak usage and variance to ensure sufficient headroom | ||
| - Current resource requests compared to actual usage |
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.
Good catch!
| In the _Off_ update mode, the VPA recommender still analyzes resource usage and generates | ||
| recommendations, but these recommendations are not automatically applied to Pods. | ||
| The recommendations are only stored in the VPA object's `.status` field. | ||
| The recommendations are only stored in the VPA object's `.status` field. In this mode, only the recommender is active. |
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.
I’d prefer not to change this. All components are active - they just aren’t performing any actions.
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.
You're right all the VPA components are active, I removed those lines in fd7fd62
content/en/docs/concepts/workloads/autoscaling/vertical-pod-autoscale.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/workloads/autoscaling/vertical-pod-autoscale.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/workloads/autoscaling/vertical-pod-autoscale.md
Outdated
Show resolved
Hide resolved
…toscale.md Co-authored-by: Aman Shrivastava <[email protected]>
content/en/docs/concepts/workloads/autoscaling/vertical-pod-autoscale.md
Outdated
Show resolved
Hide resolved
…toscale.md Co-authored-by: Omer Aplatony <[email protected]>
|
Thanks! |
|
LGTM label has been added. Git tree hash: 12bc0650fc2755f80a01e05d51123c7e5d9178ad
|
|
/cc @lmktfy |
dipesh-rawat
left a comment
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.
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dipesh-rawat 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 |
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