СRI image pulling with progress notification

[byako]

Enhancement Description

• One-line enhancement description (can be used as a release note): СRI image pulling with progress notification
• Kubernetes Enhancement Proposal: KEP-3542: СRI image pulling with progress notification #3547
• Discussion Link: Sep 27th, 2022 sig-node weekly meeting
• Primary contact (assignee): @byako
• 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): KEP-3542: СRI image pulling with progress notification
  • Code (k/k) update PR(s): RFC: CRI PullImageWithProgress implementation PoC kubernetes#118326
  • 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.

[byako]

/sig node

[k8s-ci-robot]

@byako: The label(s) sig/sig-node cannot be applied, because the repository doesn't have them.

In response to this:

/sig sig-node

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/test-infra repository.

[byako]

/sig node

[marosset]

/milestone v1.26
/label lead-opted-in
(I'm doing this on behalf of @ruiwen-zhao / SIG-node)

[rhockenbury]

/stage alpha
/label tracked/yes

[derekwaynecarr]

/remove-label lead-opted-in

This design needs more time in SIG Node and would be reviewed during 1.26 for evaluation in 1.27.

[rhockenbury]

/label tracked/no
/remove-label tracked/yes
/milestone clear

[byako]

The design is proposed now in KEP PR.

[rhockenbury]

Just want to clarify - in #3547, it looks like the milestones are targeting v1.26. Based on a prior comment from @derekwaynecarr, we have this enhancement as Removed from Milestone. Let me know if you do in fact want to opt in for the v1.26 cycle.

[byako]

Yes, @rhockenbury, that is the intention, if the proposal is approved or agreed for its details to be ironed out during v1.26 cycle - we'd like to opt this into v1.26 cycle.

[rhockenbury]

I can opt it in but it's going to be pretty tight to meet the requirements for enhancements freeze since freeze will happen in a few hours.

/label lead-opted-in
/label tracked/yes
/remove-label tracked/no

Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022.

This enhancement is targeting for stage alpha for 1.26 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.26
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

For this KEP, we would need to update the following:

• Add the PRR review file and get a PRR review
• Merge up the open PR KEP-3542: СRI image pulling with progress notification #3547

The status of this enhancement is marked as at risk.

[rhockenbury]

Hello 👋, 1.26 Enhancements Lead here.

Unfortunately, this enhancement did not meet requirements for enhancements freeze.

If you still wish to progress this enhancement in v1.26, please file an exception request. Thanks!

/milestone clear
/label tracked/no
/remove-label tracked/yes
/remove-label lead-opted-in

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[jon-nfc]

+1

[tonybart1337]

/remove-lifecycle rotten

[BloodyIron]

I for one really feel blind not knowing the progress of an image pull. It really would be useful to have some insights into the speed being pulled (so I can also troubleshoot network related problems), some form of percentage progress, and maybe an estimate of completion.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[pacoxu]

/remove-lifecycle stale

[Superskyyy]

really need this, in a coproate setting you usually hit some mysterious network issues and not being able to see the download progress is just pain.

[w7team]

+1

[TarekMSayed]

Why you moved this to Not for release.
This is very important indication specially for AI/MLOps environment. Mostly we deal with large images +5 GB, so it takes very long time +15m up to 1h for on-prim with slow connection during the image pull with no indication for what is happening.

Please consider that situation
Thanks

[BloodyIron]

Yeah can we please have this actually implemented? Having zero mechanism to tell the progress of pulling an image causes substantial problems, especially at-scale. I honestly do not see how rudimentary progress insights are not something trivial to add, downloading file progress insights have been a thing for over 20 years in so many other protocols and methods. FTP, HTTP, and more.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[jon-nfc]

/remove-lifecycle stale

this feature is still desired by many of us!!!!

[wzshiming]

Hello everyone,
I have a new design proposal for this feature modeled on the exec and logs patterns.

If you're interested, take a look. #5335