Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CRI Native Container Copy #4582

Open
4 tasks
haircommander opened this issue Apr 16, 2024 · 10 comments
Open
4 tasks

CRI Native Container Copy #4582

haircommander opened this issue Apr 16, 2024 · 10 comments
Assignees
Labels
sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/node Categorizes an issue or PR as relevant to SIG Node. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team

Comments

@haircommander
Copy link
Contributor

haircommander commented Apr 16, 2024

Enhancement Description

  • One-line enhancement description (can be used as a release note): Add an official protocol in the CRI to copy files to and from containers
  • Kubernetes Enhancement Proposal: TODO
  • Discussion Link:
  • Primary contact (assignee): @haircommander @eddiezane
  • Responsible SIGs: Node, CLI
  • Enhancement target (which target equals to which milestone):
    • Alpha release target (x.y): 1.31
    • 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):

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

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Apr 16, 2024
@haircommander
Copy link
Contributor Author

/sig node
/sig cli

@k8s-ci-robot k8s-ci-robot added sig/node Categorizes an issue or PR as relevant to SIG Node. sig/cli Categorizes an issue or PR as relevant to SIG CLI. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Apr 16, 2024
@sftim
Copy link
Contributor

sftim commented May 13, 2024

For a title, I suggest: CRI Native Container File Copying

@SergeyKanzhelev
Copy link
Member

/label lead-opted-in
/milestone v1.31
/assign @haircommander
/stage alpha

@k8s-ci-robot k8s-ci-robot added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label May 23, 2024
@k8s-ci-robot k8s-ci-robot added this to the v1.31 milestone May 23, 2024
@k8s-ci-robot k8s-ci-robot added the lead-opted-in Denotes that an issue has been opted in to a release label May 23, 2024
@dipesh-rawat
Copy link
Member

Hello @haircommander @eddiezane 👋, 1.31 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024.

This enhancement is targeting for stage alpha for 1.31 (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: v1.31. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
  • KEP readme has up-to-date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

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

  • Create the KEP readme using the latest template and merge it in the k/enhancements repo.
  • Ensure that the KEP has undergone a production readiness review and has been merged into k/enhancements.

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

@haircommander
Copy link
Contributor Author

I don't think we'll be able to come to consensus and merge this in 1.31. @SergeyKanzhelev @mrunalp can you remove this from the milestone? I may open the KEP PR by next week but I don't want to take energy away from other KEPs for just a provisional one. We will revist this in 1.32

@BenTheElder
Copy link
Member

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.31 milestone Jun 7, 2024
@dipesh-rawat
Copy link
Member

Hello @haircommander 👋, 1.31 Enhancements team here.

Since this enhancement has been rescheduled for a future release, it’s now marked as Deferred for the current v1.31 release cycle. Confirming this based on the comment #4582 (comment). Thanks!

/remove-label lead-opted-in

@k8s-ci-robot k8s-ci-robot removed the lead-opted-in Denotes that an issue has been opted in to a release label Jun 7, 2024
@sreeram-venkitesh
Copy link
Member

/label tracked/no

@k8s-ci-robot k8s-ci-robot added the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Jun 24, 2024
@kannon92
Copy link
Contributor

@haircommander What do you want to do with this feature for 1.32? Do you want to propose working on it?

@haircommander
Copy link
Contributor Author

I'm not sure I'll have bandwidth but I'd love to be able to

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/node Categorizes an issue or PR as relevant to SIG Node. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
Status: Needs Triage
Status: Not for release
Status: Deferred
Development

No branches or pull requests

8 participants