From ArchWiki
Latest comment: 29 March by Duchess in topic Add section of deploy CNI

Non-AUR version of kubectl

As far as I can tell, the page does not mention the community package kubectl. Should it? PeterSR (talk) 08:27, 31 May 2019 (UTC)Reply[reply]

According to its comment, kubernetes-binAUR is broken and outdated, we should use kubeadm-binAUR, kubelet-binAUR, kubectl-binAUR (and cni-plugins-binAUR ?).
I think kubectl is also fine. and AUR's kubernetes package (displayed as broken) is now pkgbase for kubeadmAUR and kubeletAUR. Ny-a (talk) 02:44, 31 March 2020 (UTC)Reply[reply]

Mentioning minikube

All kubernetes packages mentioned in this article is AUR package, but minikube is in official repository. Although it's not full kubernetes, I think it's still worth mentioning. Ny-a (talk) 15:27, 29 March 2020 (UTC)Reply[reply]

Add section of deploy CNI

I suggest adding a section of deploying cni for kubernetes, like calico/weave. I have deployed the base kubernetes just now according to the wiki, and then the node is NotReady status. After deploying calico refer to the calico guide, kubernetes cluster node change to Ready.

Shannxi.zyg (talk) 12:57, 11 April 2020 (UTC)Zheng YagangReply[reply]

This is a very good idea, CNI is one of the less obvious requirements of installing bare-metal Kubernetes, some explanation of how it works on Arch would be handy. Duchess (talk) 22:59, 29 March 2024 (UTC)Reply[reply]

CRI-O section needs an update

I just went through this guide and at this point I'm comfortable saying cri-o is non-functional at the end of it. Starting from scratch and going the containerd route resulted in a running system in about 10 minutes.

The issue that I ran into (not sure how it is related to cri-o btw) is that no matter what you do to install the CNI addon, nor which addon you choose, you will wind up in a state where the runtime cannot see your /etc/cni/net.d directory (even though it has the right files, distinct from the majority of issues, stackoverflows, and reddit posts) and therefore the cluster fails to ready up. Keystone (talk) 21:30, 9 February 2024 (UTC)Reply[reply]

Did you try this? Cobalt32 (talk) 21:56, 9 February 2024 (UTC)Reply[reply]
Yeah, only the IPv4 and 6 not the loopback ones. I have to do this to a few more machines, so I’ll make sure to try loopback too. Keystone (talk) 22:09, 9 February 2024 (UTC)Reply[reply]
@Indigo Sorry for the note, I didn’t realize this would be so active. Keystone (talk) 22:40, 9 February 2024 (UTC)Reply[reply]
No worries, I just went through recent changes and saw your note only after I added the template for this talk. It's prominent enough hopefully. --Indigo (talk) 22:56, 9 February 2024 (UTC)Reply[reply]