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

Kubectl Checkpoint #5091

Open
6 tasks
adrianreber opened this issue Jan 27, 2025 · 2 comments
Open
6 tasks

Kubectl Checkpoint #5091

adrianreber opened this issue Jan 27, 2025 · 2 comments
Labels
needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one.

Comments

@adrianreber
Copy link
Contributor

adrianreber commented Jan 27, 2025

Enhancement Description

  • One-line enhancement description (can be used as a release note): Introduce the kubectl checkpoint sub-command to allow users to checkpoint a container.
  • Kubernetes Enhancement Proposal:
  • Discussion Link:
  • Primary contact (assignee): @adrianreber
  • Responsible SIGs:
  • Enhancement target (which target equals to which milestone):
    • Alpha release target (x.y):
    • Beta release target (x.y):
    • Stable release target (x.y):
  • Alpha
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jan 27, 2025
@k8s-ci-robot
Copy link
Contributor

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

  • /sig <group-name>
  • /wg <group-name>
  • /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

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-sigs/prow repository.

@kikisdeliveryservice
Copy link
Member

Hi @adrianreber,

Please fill out the Discussion Link section of the issue which indicates that you've spoken to a SIG about opening this KEP. Also please identify the sponsoring SIG for this KEP.

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

3 participants