Support Configurable Scaling Delay with Pod Resource Exposure

[Chunxia202410]

Enhancement Description

• One-line enhancement description (can be used as a release note): Support Configurable CPU Scale Down Delay
• Kubernetes Enhancement Proposal: KEP 6122: Configurable Scaling Delay with Pod Resource Exposure KEP creation #6123
• Discussion Link: SIG Node meeting
• Primary contact (assignee): @Chunxia202410 , @lukaszwojciechowski , @radoslawc , @jain-ashish-sam, @subh007 , @shiya0705
• Responsible SIGs: sig-node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.37
  • Beta release target (x.y): 1.38
  • Stable release target (x.y): 1.40
• PRs by stage and milestone:
  • Alpha - v1.37
    • KEP (k/enhancements) update PR(s): KEP 6122: Configurable Scaling Delay with Pod Resource Exposure KEP creation #6123
    • Code (k/k) update PR(s): [WIP][FG:InPlacePodVerticalScaling] Configurable CPU Scale Down Delay kubernetes#136015
    • Docs (k/website) update PR(s):

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

[radoslawc]

/sig node

[radoslawc]

/milestone v1.37
/label lead-opted-in
/stage alpha

[k8s-ci-robot]

@radoslawc: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.

Details

In response to this:

/milestone v1.37
/label lead-opted-in
/stage alpha

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.

[k8s-ci-robot]

@radoslawc: The label(s) lead-opted-in cannot be applied or removed, because you are not in one of the allowed teams and are not an allowed user. Must be a member of one of these teams: release-team-enhancements, release-team-leads, sig-api-machinery-leads, sig-apps-leads, sig-architecture-leads, sig-auth-leads, sig-autoscaling-leads, sig-cli-leads, sig-cloud-provider-leads, sig-cluster-lifecycle-leads, sig-contributor-experience-leads, sig-docs-leads, sig-etcd-leads, sig-instrumentation-leads, sig-k8s-infra-leads, sig-multicluster-leads, sig-network-leads, sig-node-leads, sig-release-leads, sig-scalability-leads, sig-scheduling-leads, sig-security-leads, sig-storage-leads, sig-testing-leads, sig-windows-leads

Details

In response to this:

/milestone v1.37
/label lead-opted-in
/stage alpha

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.

[haircommander]

/label lead-opted-in
/milestone v1.37