enhancements icon indicating copy to clipboard operation
enhancements copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

СRI image pulling with progress notification

Open byako opened this issue 2 years ago • 57 comments

Enhancement Description

  • One-line enhancement description (can be used as a release note): СRI image pulling with progress notification
  • Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/pull/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): 1.30
    • Beta release target (x.y): 1.31
    • Stable release target (x.y): 1.32
  • [ ] Alpha

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

byako avatar Sep 23 '22 07:09 byako

/sig node

byako avatar Sep 26 '22 07:09 byako

@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.

k8s-ci-robot avatar Sep 26 '22 07:09 k8s-ci-robot

/sig node

byako avatar Sep 26 '22 07:09 byako

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

marosset avatar Sep 30 '22 18:09 marosset

/stage alpha /label tracked/yes

rhockenbury avatar Oct 01 '22 01:10 rhockenbury

/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.

derekwaynecarr avatar Oct 03 '22 20:10 derekwaynecarr

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

rhockenbury avatar Oct 03 '22 21:10 rhockenbury

The design is proposed now in KEP PR.

byako avatar Oct 05 '22 18:10 byako

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.

rhockenbury avatar Oct 06 '22 01:10 rhockenbury

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.

byako avatar Oct 06 '22 07:10 byako

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 https://github.com/kubernetes/enhancements/pull/3547

The status of this enhancement is marked as at risk.

rhockenbury avatar Oct 06 '22 20:10 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

rhockenbury avatar Oct 07 '22 01:10 rhockenbury

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Jan 05 '23 02:01 k8s-triage-robot

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

k8s-triage-robot avatar Feb 04 '23 03:02 k8s-triage-robot

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!

If I read this correctly, this feature, much needed by many, will not make it to 1.26... It has been in the pipeline for too long. Hopefully, we'll see it implemented in the next release.

dvasilen avatar Feb 09 '23 12:02 dvasilen

I presume you meant 1.27, since 1.26 was released almost two months ago. I'll try to progress with it for 1.27, but code freeze is in one month, so there is a risk. I've been busy with primary-work related tasks, unfortunately, but I'm still committed to this KEP. Apologies for the delay.

byako avatar Feb 09 '23 13:02 byako

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

This bot triages 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:

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

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

/close not-planned

k8s-triage-robot avatar Mar 11 '23 14:03 k8s-triage-robot

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

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

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

/close not-planned

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.

k8s-ci-robot avatar Mar 11 '23 14:03 k8s-ci-robot

@dvasilen: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

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.

k8s-ci-robot avatar Mar 11 '23 14:03 k8s-ci-robot

/reopen

byako avatar Mar 13 '23 07:03 byako

@byako: Reopened this issue.

In response to this:

/reopen

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.

k8s-ci-robot avatar Mar 13 '23 07:03 k8s-ci-robot

Moving to 1.28, had no time this quarter.

byako avatar Mar 13 '23 08:03 byako

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

This bot triages 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:

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

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

/close not-planned

k8s-triage-robot avatar Apr 12 '23 08:04 k8s-triage-robot

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

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

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

/close not-planned

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.

k8s-ci-robot avatar Apr 12 '23 08:04 k8s-ci-robot

/reopen

byako avatar Apr 12 '23 08:04 byako

@byako: Reopened this issue.

In response to this:

/reopen

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.

k8s-ci-robot avatar Apr 12 '23 08:04 k8s-ci-robot

/remove-lifecycle rotten

byako avatar Apr 12 '23 08:04 byako

@byako do you plan to work on this for 1.28 release?

SergeyKanzhelev avatar May 05 '23 21:05 SergeyKanzhelev

Yes, @SergeyKanzhelev , I've started today with this as main task.

byako avatar May 08 '23 06:05 byako

@byako can you mark the PR https://github.com/kubernetes/enhancements/pull/3547 as non-draft when it is ready for review. I see you updated version in PR's kep.yaml so applying milestone here:

/milestone v1.28

SergeyKanzhelev avatar May 26 '23 21:05 SergeyKanzhelev