Expose metrics about resource requests and limits that represent the pod model

[smarterclayton]

Enhancement Description

• Administrators of Kube need a metric that correctly describes resource requests from pods and hides the complexities of the evolving pod resource model.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-instrumentation/1748-pod-resource-metrics/README.md
• Primary contact (assignee): @smarterclayton
• Responsible SIGs: sig-instrumentation, sig-node, sig-scheduling
• Enhancement target (which target equals to which milestone):
  • Alpha release target (1.20)
  • Beta release target (1.21)
  • Stable release target (1.27)
    • KEP (k/enhancements) update PR(s):
      • KEP-1748: update to stable #3810
    • Code (k/k) update PR(s):
      • Promote pod resource metrics to stable kubernetes#115454
    • Docs (k/website) update(s):
      • WIP: [KEP-1748]: Add capacity planning documentation website#39998

[smarterclayton]

/sig instrumentation
/sig node
/sig scheduling

[harshanarayana]

Hey there @smarterclayton -- 1.19 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating in 1.19?

In order to have this part of the release:

1. The KEP PR must be merged in an implementable state
2. The KEP must have test plans
3. The KEP must have graduation criteria.

The current release schedule is:

• Monday, April 13: Week 1 - Release cycle begins
• Tuesday, May 19: Week 6 - Enhancements Freeze
• Thursday, June 25: Week 11 - Code Freeze
• Thursday, July 9: Week 14 - Docs must be completed and reviewed
• Tuesday, August 4: Week 17 - Kubernetes v1.19.0 released

If you do, I'll add it to the 1.19 tracking sheet (http://bit.ly/k8s-1-19-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

[smarterclayton]

I don't think we'll make implementable and merged by Tuesday, so should be targeted for 1.20

[harshanarayana]

Hey @smarterclayton Thanks for confirming the inclusion state. I've marked the Enhancement as Deferred in the Tracker and updating the milestone accordingly.

/milestone v1.20

[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

[palnabarun]

/remove-lifecycle stale