Talk:Kubernetes

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)

According to its comment, kubernetes-bin^AUR is broken and outdated, we should use kubeadm-bin^AUR, kubelet-bin^AUR, kubectl-bin^AUR (and cni-plugins-bin^AUR ?).

I think kubectl is also fine. and AUR's kubernetes package (displayed as broken) is now pkgbase for kubeadm^AUR and kubelet^AUR. Ny-a (talk) 02:44, 31 March 2020 (UTC)

This discussion is obsolete, closing. — Lahwaacz (talk) 08:11, 29 June 2024 (UTC)

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)

Added link to the intro, closing. — Lahwaacz (talk) 08:10, 29 June 2024 (UTC)

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 https://docs.projectcalico.org/getting-started/kubernetes/quickstart, kubernetes cluster node change to Ready.

Shannxi.zyg (talk) 12:57, 11 April 2020 (UTC)Zheng Yagang

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)

There is a section which points to a list of all CNI plugins: Kubernetes#Installing CNI plugins (pod network addon). We can't cover everything from the upstream documentation pages, so this is the best we can do. — Lahwaacz (talk) 08:19, 29 June 2024 (UTC)

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)

Did you try this?

https://wiki.archlinux.org/title/CRI-O#Network Cobalt32 (talk) 21:56, 9 February 2024 (UTC)

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)

@Indigo Sorry for the note, I didn’t realize this would be so active. Keystone (talk) 22:40, 9 February 2024 (UTC)

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)

I recently went through this and besides enabling the /opt/cni/bin/ CNI plugin directory there was no gotcha. This is noted in Kubernetes#Installing CNI plugins (pod network addon), so I will close this. — Lahwaacz (talk) 08:16, 29 June 2024 (UTC)

I agree with this, the CRI-O section mostly confused me. Duchess (talk) 15:11, 14 July 2024 (UTC)

What statement did you find confusing? What did you try and what does not work? — Lahwaacz (talk) 15:31, 14 July 2024 (UTC)