Container Resources CRI API Changes for Pod Vertical Scaling

Enhancement Description

• One-line enhancement description (can be used as a release note):

Container Resources CRI API Changes for Pod Vertical Scaling

• Kubernetes Enhancement Proposal:

After merging #2266, we will get the file location: "/keps/sig-node/2273-kubelet-container-resources-cri-api-changes"

• Discussion Link: In-Place Vertical Pod Scaling KEP to implementable, and mini-KEP for CRI extensions #1342

• Primary contact (assignee):

  • "@vinaykul"
  • "@quinton-hoole"

• Responsible SIGs: sig-node

• Enhancement target (which target equals to which milestone):

  • Alpha release target (x.y):
  • Beta release target (x.y):
  • Stable release target (x.y):

• Alpha

  • KEP (k/enhancements) update PR(s):
  • Code (k/k) update PR(s):
  • Docs (k/website) update PR(s):

Alpha

• UpdateContainerResources and ContainerStatus API changes are done and tested
  with dockershim and docker runtime, backward compatibility is maintained.

Beta

• UpdateContainerResources and ContainerStatus API changes are completed and
  tested for Windows runtime.

Stable

• No major bugs reported for three months.

Implementation History

• 2019-10-25 - Initial KEP draft created
• 2020-01-14 - Test plan and graduation criteria added
  Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

/sig node

We need to update the "Enhancement target" and in the proposal as well.

[ehashman]

/sig autoscaling

[vinaykul]

We need to update the "Enhancement target" and in the proposal as well.

@shekhar-rajak Thanks for migrating the KEP to the new format (I apologize for being unresponsive about it). Could you please clarify what Enhancement target refers to here, and where should we make the update?

@thockin and I have been working on updating the design changes to the main KEP and I believe we have reached a consensus. Consequently, I reviewed the CRI KEP for potential changes. Besides the issue of dockershim deprecation and it's potential impact on alpha test criteria that I need to investigate closely, nothing in particular stands out as needing update.

I'm looking to target both KEPS for 1.21 release at this time, the estimate might change depending on my assessment of how much the codebase has evolved since my earlier implementation last summer.

/cc @kikisdeliveryservice

[kikisdeliveryservice]

Hi @vinaykul !

Enhancements freeze has passed and this KEP is not tracked/was not opted in. You'll need to discuss with the sponsoring SIGs and if they agree, submit an Exception Request ASAP to be included in the 1.21 release.

cc: @annajung

[ehashman]

/stage alpha
/milestone v1.22

ref #2474