https://bugzilla.redhat.com/show_bug.cgi?id=2424524
Brad Smith <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|AutomationTriaged | --- Comment #3 from Brad Smith <[email protected]> --- This feature has some specific requirements including either containerd or crio and crun or runc. There are a few other technical requirements (idmap support in the filesystem) that are not too constraining. But the restriction to crio or containerd and crun or runc could potentially be blocking for some users and, in my perspective, make this capability optional and not (yet at least) a standard component. During some testing and debugging I found that if the `kubelet` user existing on the machine but subuids were not assigned, then the kubelet service will fail to start with an error message about the misconfiguration. So I suspect that if this were part of a kubernetes-common package that was a required dependency for the kubernetes packages (e.g. kubernetes1.34) then the out-of-the-box experience would be a failure to start unless the subuids are configured even when not used. -- You are receiving this mail because: You are always notified about changes to this product and component You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2424524 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202424524%23c3 -- _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
