FS#74873 - [kubelet] fails to start by attempting to use deprecated flag "--cni-bin-dir"
Attached to Project:
Community Packages
Opened by Jonathon Waterhouse (jwtrhs) - Saturday, 28 May 2022, 05:59 GMT
Last edited by David Runge (dvzrv) - Wednesday, 24 August 2022, 17:59 GMT
Opened by Jonathon Waterhouse (jwtrhs) - Saturday, 28 May 2022, 05:59 GMT
Last edited by David Runge (dvzrv) - Wednesday, 24 August 2022, 17:59 GMT
|
Details
Description:
kubelet.service fails to start. The latest version of kubelet no longer supports the --cni-bin-dir flag, which is set in the KUBELET_ARGS environment variable in the file "kubelet.env" and referenced by the unit file. Additional info: * package version(s): 1.24.1 * link: https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/ the cni-bin-dir flag had been marked as deprecated Steps to reproduce: 1. pacman -S kubelet 2. systemd kubelet start 3. Service will not start due to above error. |
This task depends upon
[crio.network]
plugin_dirs = [
"/opt/cni/bin/",
]
If you have capacity to test things, please activate testing and help test kubernetes components (they are usually left in testing for one or two weeks before moving them to the stable repos).
0xAnselm: Thanks for adding that to the wiki (https://wiki.archlinux.org/title/Kubernetes#Configuration)!
Does this still fail without the cri-o config addition if you only remove the configuration option in /etc/kubernetes/kubelet.env?
@0xAnselm: As your issue is sort of unrelated (it's related to the container-runtime provided by cri-o), please regard this separately. Also, this issue is covered in cri-o's wiki page since September last year: https://wiki.archlinux.org/title/CRI-O#Plugin_Installation
If you think there is room for improval for cri-o, please open a ticket against that.