Fedora Ask - Installing Kubernetes on Fedora Server Question
Intention
This is purely to learn how to set up Kubernetes using the bare necessities and not to use a prepackaged distribution of Kubernetes like EKS, GKS, AKS, Minikube, k3s, k0s, OpenShift or any of that.
and then upon starting up the kubelet service, I receive multiple errors. I was trying to install k8s on a virtual machine running Fedora 37 Server (netinstall). I simply performed:
From what I can tell with the below error is that kubelet is unable to determine the IP Address of the machine it’s running on. Since I’m not running a DNS server and this is a libvirtd virtual machine, is there anything special I need to do?
Looking at the kubeadm documentation, I need to use kubeadm, but that’s outside of what this Fedora Magazine article showed.
Yup, minikube, k0s, k3s, kind, and all that work. I want to get this setup working using vanilla setup as possible. I have yet to get it to work on Fedora Server even doing it the manual way or using kubespray.
The manual, “vanilla” way (if you have more than one node, hence without minikube*) of installing a cluster (not simply connecting via kubeconfig/kubelogin) is by kubeadm init, following the docs Installing kubeadm | Kubernetes
(I’m interested if you find another way to do that, but I think they have quite good docs, also with tabs for Red Hat-based distributions)
(*) Btw I work with AKS, GKE etc. and I find minikube perfectly suited for cheap dev/test experiments on a local, one node, (Fedora) machine.
A few other links🔗 about kubespray (aside from the official docs)
Creating a Kubernetes Cluster with Fedora CoreOS 36
I updated my original question. I’ve seen kubespray and almost got Kubernetes working on a single server but had issues with my IP not correctly being used or something.
I’ve also seen Kelsey Hightower’s learn kubernetes the hard way. I was assuming (shame on me) that the RPMs in the RPM repo for Fedora would perform most of the setup of Kubernetes that kubeadm or kubespray does so you could just pop one into existence.
If the RPMs do not do that, then I’ll go back to using kubeadm and kubespray to setup a single node kubernetes instance just to say I’ve done it successfully and go back
to using one of those other distributions.
I also work with AKS and EKS and OpenShift using minikube or k0s in Podman as a local dev environment but have never successfully set it up on my own to prove to myself I actually understand the platform without just blindly using it.
