Add ephemeral storage requests recommendation and update to vpa

[mfilotto]

It would be nice if vpa could also take care of ephemeral storage usage and set request accordinngly

[bskiba]

@kgolab I think you were looking into this. Are there usage metrics for ephemeral storage available form Metric Server?

[kgolab]

@bskiba , at the moment Metric Server only serves metrics for CPU & memory usage.
But, since:

• the ephemeral storage usage is also available via Kubelet summary API, scraped by Metric Server to obtain all the information,
• and ephemeral storage is part of Pod resource request,
• and it's been also mentioned in comments to in-place update KEP proposal,

maybe we could make a case for it being included in Metric Server and then supported by VPA.

@mfilotto , do you already have a use case in mind or, even better, described somewhere? We'd like to understand more about intended usage of these recommendations.
In particular I'm very interested in when would the recommendations be applicable from your perspective.

[mfilotto]

@kgolab I use vpa to set requests automatically. This way kubelets and scheduler will have a more precise intel of what's going on on each node. So my goal is to reduce evictions as much as possible. vpa do the job for memory and cpu but ephemeral storage are left unset so kubelet keep triggering evictions.
If vpa could also set ephemeral storage it would be awesome, this way vpa would help to reduce all evictions and be precious for capacity planning.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[kgolab]

/remove-lifecycle stale
Marking as not to disappear from the radar, this might be revisited at some point.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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/test-infra repository.