VPA: document behavior for Requests & Limits

[omerap12]

In this issue, we discussed how the Vertical Pod Autoscaler (VPA) handles requests and limits values compared to how Kubernetes itself manages them. This distinction is important, and we need it to be properly documented.

@adrianmoisey has provided a great summary of the discussion here, which can serve as a basis for the documentation.

I propose adding this information to our FAQ.

/area vertical-pod-autoscaler
/good-first-issue
/kind documentation

[k8s-ci-robot]

@omerap12:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

In this issue, we discussed how the Vertical Pod Autoscaler (VPA) handles requests and limits values compared to how Kubernetes itself manages them. This distinction is important, and we need it to be properly documented.

@adrianmoisey has provided a great summary of the discussion here, which can serve as a basis for the documentation.

I propose adding this information to our FAQ.

/area vertical-pod-autoscaler
/good-first-issue
/kind documentation

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[novahe]

/assign

[Shubham82]

/triage accepted