-
Notifications
You must be signed in to change notification settings - Fork 59
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
F32: should we switch to cgroups v2 #373
Comments
this ticket is related to: #372 |
cc'ing @vrutkovs for that 3rd bullet point :) |
cgroupvs2 can be used, but it requires kubernetes/enhancements#1370 (kubernetes/kubernetes#85218), few crio fixes (merged in master already afaik) and swapping runc with crun (afaik runc is planning to support cgroupsv2). @giuseppe would know more details on OKD side we're safe because bootstrap / masters / workers switch to cgroupsv1 mode on pivot, so we're independent on defaults here |
the plan is to have cgroups v2 Alpha support for Kubernetes 1.19. |
Moby already has a basic support for cgroup2, but |
We discussed during the meeting today It appears that the moby and kubernetes projects are not quite there yet with regards to cgroups v2 support. In the meeting we proposed and agreed that we should probably wait for now:
|
We originally decided to stay on cgroups v1 so that the container ecosystem could catch up. We should evaluate if we can move to cgroups v2 for the Fedora 32 rebase. Some examples of things to investigate:
The text was updated successfully, but these errors were encountered: