match the kubelet and CRI implementer cgroup drivers #99808
Description
Metadata
Metadata
Assignees
Labels
Categorizes issue or PR as related to a new feature.Indicates that an issue or PR should not be auto-closed due to staleness.Indicates an issue or PR lacks a `triage/foo` label and requires one.Important over the long term, but may not be staffed and/or may need multiple releases to complete.Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.Categorizes an issue or PR as relevant to SIG Node.
What would you like to be added:
make it possible for CRI implementers and kubelet to match their cgroup drivers via auto-detection.
https://kubernetes.slack.com/archives/C0BP8PW9G/p1614888729200700
the above discussion on slack indicated a couple of options:
2 seems preferred.
Why is this needed:
ideally the two sides should auto-match cgroup drivers, so that we can attempt to hide this detail from user space.
currently, users that install container runtimes and the kubelet need to explicitly configure both to have a matching driver or otherwise the mismatch can cause failures. a lot of users don't know what "cgroup drivers/managers" are and they end up ignoring this important (but low level) detail.