Container Resource based Pod Autoscaling

[arjunrn]

Enhancement Description

• One-line enhancement description (can be used as a release note): Container Resource based Pod Autoscaling
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-autoscaling/1610-container-resource-autoscaling/README.md
• Primary contact (assignee):
• Responsible SIGs: autoscaling
• Enhancement target (which target equals to which milestone):
  • Alpha release target 1.19
  • Beta release target 1.27
  • Stable release target 1.30
• Implementation: Add container based scaling to HPA kubernetes#90691 The graduation HPA container resource metrics to beta kubernetes#115467 graduate HPAContainerMetrics to stable kubernetes#123482
• Docs: Added docs about container resource metric source for HPA website#23523 graduate HPAContainerMetrics to stable website#45204
• KEP PR for beta: KEP-1610: update KEP to graduate the container resource metric to beta #3834
• KEP PR for main: KEP-1610: graduate ContainerResource to stable #4406
• k/k issue to track what we need for beta: The graduation HPA container resource metrics to beta kubernetes#115467

[arjunrn]

/sig autoscaling

[harshanarayana]

Hey there @arjunrn -- 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!

[harshanarayana]

Hey @arjunrn, I'm following up on my previous update on this Enhancement being part of the v1.19 release.

Do you happen to have any update on the possiblity of this being included in the release v1.19?

Thanks again for your time and contributions. 🖖

[harshanarayana]

Hey @arjunrn, I'm following up on my previous update on this Enhancement being part of the v1.19 release.

Do you happen to have any update on the possiblity of this being included in the release v1.19?

Thanks again for your time and contributions. 🖖

[harshanarayana]

Hey @arjunrn, any plans for the Enhancements to be included in v1.19? Please let me know so that I can update the tracking sheet to show the inclusion state.

Enhancements freeze is on May 19

Note that recently the KEP format has changed. Additionally, #1620 merged recently, adding production readiness review questions to the KEP template.
Please take this opportunity to reformat your KEP and also answer the questions added to the template in that PR.

Thanks,
🖖

[harshanarayana]

Hey @arjunrn, Unfortunately the deadline for the 1.19 Enhancement freeze has passed and the KEP is still in provisional state. For now this is being removed from the milestone and 1.19 tracking sheet. If there is a need to get this in, please file an enhancement exception.

[harshanarayana]

Marking to a deferred milestone after discussing with @arjunrn

/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

[arjunrn]

/remove-lifecycle stale