Pod Overhead: account resources tied to the pod sandbox, but not specific containers

[tallclair]

Enhancement Description

• One-line enhancement description (can be used as a release note):
  Account resources consumed by the pod sandbox, both for scheduling and limiting runtime usage.
• Primary contact (assignee):
  @egernst
• Responsible SIGs:
  /sig node
• KEP: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/20190226-pod-overhead.md
• Design proposal link (community repo):
  WIP: https://docs.google.com/document/d/1EJKT4gyl58-kzt2bnwkv08MIUZ6lkDpXcxkHqCvvAp4/edit?usp=sharing
• Link to e2e and/or unit tests:
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
• Approver (likely from SIG/area to which enhancement belongs):
• Enhancement target (which target equals to which milestone):
  • Alpha release target: 1.16
  • Beta release target: 1.18
  • Stable release target: tbd

Relevant K/K issues/PRs for code-freeze::
e2e tests: kubernetes/kubernetes#87215
monitoring: kubernetes/kubernetes#87259
Relevant K/E issues: #1526

Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement

[tallclair]

/help
I'm looking for someone who is interested in picking back up this proposal. Specifically, the design proposal needs to be reworked in the context of RuntimeClass, and the details need to be worked through with the sig-node community before we can move to implementation.

/cc @egernst

[egernst]

Thanks @tallclair. I may have questions on the process, but am happy to pick this up.

[tallclair]

\o/
/remove-help
/assign @egernst

[k8s-ci-robot]

@tallclair: GitHub didn't allow me to assign the following users: egernst.

Note that only kubernetes members and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

\o/
/remove-help
/assign @egernst

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.

[tallclair]

/assign @egernst

[egernst]

Hey @tallclair et al, I made several suggestions for the WIP RFC @ https://docs.google.com/document/d/1EJKT4gyl58-kzt2bnwkv08MIUZ6lkDpXcxkHqCvvAp4/edit?usp=sharing

I added a section for updating the runtimeClass CRD, and explained how the values would be obtained from the new suggested runtimeClass fields rather than configured in the runtimeController. The suggested runtimeController scope is also greatly reduced, allowing this first iteration to just handle adding the pod overhead.

PTAL.

[vinaykul]

@tallclair @egernst I quickly went though the design proposal. We are working on In-Place Vertical Scaling for Pods, and I want to clarify a couple of things.

In the context or in-place resize, do you see PodSpec.Overhead as something VPA should be aware of via metrics reporting? And perhaps in the future, track this field and make recommendations for it. It would be a good idea to nail down early-on if this field should be mutable by an external entity.

CC: @kgolab @bskiba @schylek

[kacole2]

Hello @tallclair, I'm the Enhancement Lead for 1.15. It looks like there is no KEP accepted yet. Is it safe to assume this will not make the enhancement freeze deadline for 1.15?