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

auto-pause: support non-docker runtimes #10597

Closed
medyagh opened this issue Feb 24, 2021 · 3 comments · Fixed by #11834
Closed

auto-pause: support non-docker runtimes #10597

medyagh opened this issue Feb 24, 2021 · 3 comments · Fixed by #11834
Assignees
Labels
co/auto-pause kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@medyagh
Copy link
Member

medyagh commented Feb 24, 2021

No description provided.

@medyagh medyagh added kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. co/auto-pause labels Feb 24, 2021
@medyagh medyagh added this to the v.1.19.0-candidate milestone Feb 26, 2021
@hetong07
Copy link
Contributor

hetong07 commented Mar 2, 2021

/assign

@hetong07
Copy link
Contributor

hetong07 commented Mar 3, 2021

@medyagh Take a quick look at this issue, seems crio and containerd both have implemented PauseContainers(), ListContainers() and UnpauseContainers(), which are keys to the auto-pause feature. Is there any specific requirement to support crio and containerd?

@hetong07
Copy link
Contributor

hetong07 commented Mar 5, 2021

/unassign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/auto-pause kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants