In this video I’ll show you how to successfully install K8S 1.29.1 on an Ubuntu 22.04.3 LTS server with containerd 1.7.13.
UBUNTU SERVER LTS 22.04.3
KUBERNETES 1.29.1
CONTAINERD 1.7.13
RUNC 1.1.12
CNI PLUGINS 1.4.0
CALICO CNI 3.27.2
Also cover how to install with custom pod network network CIDR.
[ad_2]
source
At the end I was confused about the worker node role for k8s-1, here is the command to label that node so its a worker node:
kubectl label node k8s-1 node-role.kubernetes.io/worker=worker
Thank you so much man! I have struggled for weeks to set up k8's on VM's (never did it before). I went through dozens of tutorials and none worked. Your tutorial not only taught me why the other wouldn't work but also made it possible to finally get my cluster working. You're Amazing!
Fantastic 💯
Pls keep up the great work!
How did you add the repo key without the certificate issuer? I'm getting msg erros regarding not being able to verify the certificate: " "Failed to update apt cache: W:Updating from such a repository can't be done securely, and is therefore disabled by default."
Hello, thank you very much for the tutorial, I managed to configure my kubernetes cluster.
I just have a problem, I'm trying to download with curl into a container but I get the error "it doesn't resolve the host", apparently the pods or containers don't have access to the internet. Could you please help me solve this problem?
Thank you so much.
hello thank u sir. cluster is running. much informational sir. tried many youtube vidoes and documentation. it worked.
You method always works, thanks a ton 🙂
thank you
its was quick and simple to learn from here. great video. please make a video on UI and any microservice deployment on kubernetes worker-nodes video. Thank you
Hey mate, thank you very much, this has been the best explanation video I've seen for K8s deployment in Ubuntu 22. Yesterday I was super frustrated trying to get this done until your video. Thanks again, btw the link in the description does not work.
Thanks for video. In this case there is no need to install etcd?
…Sensational video! Thanks so much!!! Please keep them coming on K8s
Hello, join 2 worker nodes.
calico-system calico-node-579hc 0/1 Running 1 (43s ago) 12m *.***.**.* worker-node-0 <none> <none>
calico-system calico-node-6h5hq 0/1 Running 1 (43s ago) 15m *.***.**.* worker-node-1 <none> <none>
calico-system calico-node-95mgh 0/1 Running 1 (43s ago) 10m *.***.**.* master-node <none> <none>
Pods drop to 0/1. Is this normal behavior?
Is it a mistake?
join 1 worker nodes no problem
calico-system calico-node-6h5hq 1/1 Running 0 3m40s *.***.**.* worker-node-0 <none> <none>
calico-system calico-node-95mgh 1/1 Running 0 15m *.***.**.* master-node <none> <none>
thank you! best instruction for beginners!
I was trying to install kubeadm with many tutorials and none of them worked. Yours worked perfectly.
When i was executing the comand "kubeadm init" it get stuck on "wait-control-plane" and after a few minutes then get an error, I don't understand why.
It was about your containerd configuration I guess, because that's the only difference of the others tutorials.
printf "n192.168.15.93 k8s-controln192.168.15.94 k8s-1n192.168.15.95 k8s-1nn" >> /etc/hosts
maybe the last one host should be "k8s-2" ?
Thanks a lot for this video. Finally I understand the whole process how-to set this thing up!
It is possible to upload with 4 resolution
Thanks
Hi LOVE YOU VIDEOS. !!!!!!!!!!! Please any recommendation on a good low power server to build my home lab. preferably a Mini PC that could handle virtualization and Type 1 hypervisor such as proxmox
Getting below error:
[kubelet-start] Starting the kubelet
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
Unfortunately, an error has occurred:
timed out waiting for the condition
This error is likely caused by:
– The kubelet is not running
– The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
– 'systemctl status kubelet'
– 'journalctl -xeu kubelet'
Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.
Here is one example how you may list all running Kubernetes containers by using crictl:
– 'crictl –runtime-endpoint unix:///var/run/containerd/containerd.sock ps -a | grep kube | grep -v pause'
Once you have found the failing container, you can inspect its logs with:
– 'crictl –runtime-endpoint unix:///var/run/containerd/containerd.sock logs CONTAINERID'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
To see the stack trace of this error execute with –v=5 or higher
root@master-node:~#
=====================================================================================================================================
root@master-node:~# systemctl status kubelet
● kubelet.service – kubelet: The Kubernetes Node Agent
Loaded: loaded (/lib/systemd/system/kubelet.service; enabled; vendor preset: enabled)
Drop-In: /usr/lib/systemd/system/kubelet.service.d
└─10-kubeadm.conf
Active: active (running) since Tue 2024-02-27 07:12:46 UTC; 4min 36s ago
Docs: https://kubernetes.io/docs/
Main PID: 30107 (kubelet)
Tasks: 13 (limit: 4558)
Memory: 26.9M
CPU: 3.132s
CGroup: /system.slice/kubelet.service
└─30107 /usr/bin/kubelet –bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf –kubeconfig=/etc/kubernetes/kubelet.conf –config=/var/lib/kubelet/c>
Feb 27 07:17:18 master-node kubelet[30107]: E0227 07:17:18.201422 30107 remote_runtime.go:193] "RunPodSandbox from runtime service failed" err="rpc error: code = Unkno>
Feb 27 07:17:18 master-node kubelet[30107]: E0227 07:17:18.201539 30107 kuberuntime_sandbox.go:72] "Failed to create sandbox for pod" err="rpc error: code = Unknown de>
Feb 27 07:17:18 master-node kubelet[30107]: E0227 07:17:18.201599 30107 kuberuntime_manager.go:1172] "CreatePodSandbox for pod failed" err="rpc error: code = Unknown d>
Feb 27 07:17:18 master-node kubelet[30107]: E0227 07:17:18.201757 30107 pod_workers.go:1298] "Error syncing pod, skipping" err="failed to "CreatePodSandbox" for "ku>
Feb 27 07:17:18 master-node kubelet[30107]: E0227 07:17:18.715882 30107 controller.go:145] "Failed to ensure lease exists, will retry" err="Get "https://10.247.60.81:>
Feb 27 07:17:18 master-node kubelet[30107]: I0227 07:17:18.872135 30107 kubelet_node_status.go:73] "Attempting to register node" node="master-node"
Feb 27 07:17:18 master-node kubelet[30107]: E0227 07:17:18.872644 30107 kubelet_node_status.go:96] "Unable to register node with API server" err="Post "https://10.247>
Feb 27 07:17:20 master-node kubelet[30107]: E0227 07:17:20.238710 30107 event.go:355] "Unable to write event (may
nailed it!
you're on fire lately! Keep it up!
that's a lot of numbers.
Be sure to check the video description / details for the commands text file used in the video.