Enhancements: Expose status.containerStatuses[*].imageID through Downward API

Created on 24 Sep 2020 · 8Comments · Source: kubernetes/enhancements

Enhancement Description

One-line enhancement description (can be used as a release note): Expose status.containerStatuses[*].imageID through Downward API
Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/pull/2013
Discussion Link: https://github.com/kubernetes/kubernetes/issues/80346 and September 22nd, 2020 sig-node meeting
Primary contact (assignee): @mitar
Responsible SIGs: node
Enhancement target (which target equals to which milestone):
- Alpha release target (1.20)
- Beta release target (1.21)
- Stable release target (1.22)

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

sinode stagalpha trackeno

Source

mitar

Most helpful comment

We discussed this one in sig-node today. We will review and evaluate it for the next cycle. Thanks!

mrunalp on 7 Oct 2020

👍2

All 8 comments

/sig node

mitar on 24 Sep 2020

Hi @mitar

Enhancements Lead here. Are you intending this to be alpha in 1.20?

Please keep in mind that by Enhancements Freeze, Oct 6th, all KEPs intended for the 1.20 Release must be:

Merged in an implementable state
Have test plans
Have graduation criteria
Have an open issue in the release milestone

I see that your draft says alpha in 1.19 but that seems incorrect since it's new? https://github.com/kubernetes/enhancements/pull/2013/files#diff-12b3e049a4da31bbd2192aa631e47aeeR25

Please let me know your plans so the Enhancements team can track this KEP appropriately.

Best,
Kirsten

kikisdeliveryservice on 24 Sep 2020

Thank you for the comments. This my first KEP so I am not sure about the process. I think I can try to get it in for 1.20 and we can see if that slides. I will update the draft.

mitar on 24 Sep 2020

👍1

No problem, just keep us updating here in the issue =)

And if you have any questions, do let me know

kikisdeliveryservice on 24 Sep 2020

I have finished my draft and converted it to full PR. Should I just wait now or should I be proactive in some way? Like adding it to the meeting agenda to sig-node?

mitar on 24 Sep 2020

Definitely be proactive! I'd suggest reaching out on the mailing list and maybe slack to solicit feedback:
https://github.com/kubernetes/community/tree/master/sig-node#contact

They should be able to tell you next steps :)

kikisdeliveryservice on 24 Sep 2020

HI @mitar,

Just a reminder that the Enhancements Freeze is Tomorrow October 6th EOD PST. All KEPs and updates must be merged by that time. After October 6th, you will need to request an Exception to be included in the 1.20 Release.

Thank you!