Hi, here is my config: Vagrant file: 3.times do |i| config.vm.define "node#{i+1}" do |node| node.vm.hostname = "node#{i+1}" node.vm.network "public_network", bridge: "Intel(R) Wireless-AC 9560 160MHz", ip: "192.168.1.5#{i+1}" end end --apiserver-advertise-address: root@node1:~# cat /etc/kubernetes/manifests/kube-apiserver.yaml | grep advertise kubeadm.kubernetes.io/kube-apiserver.advertise-address.endpoint: 192.168.1.51:6443 - --advertise-address=192.168.1.51

Hi, 1. You have a local subnet. For example, 192.168.1.0/24. 2. Take nonbusy IP addresses. Your WiFi router gives IP addresses from the pool using the DHCP protocol. For example, 192.168.1.200-192.168.1.254. You can find busy IP addresses on your home WiFi router. And configure the static diapason of IP addresses (IP addresses not given by the DHCP server) there too.

Hi, kubernetes.io/docs/reference/setup-tools/kubeadm/

Hi, I'm going to make a video about it.

Hi, github.com/devops-serge

Hi, there are several options: - Your virtualization environment (VirtualBox, KVM, VMWare Workstation) - VPS Hosting - Cloud Providers - Container (Docker, Kubernetes)

Hi, I use VirtualBox with Vagrant to create VMs. In Linux, you can use KVM or VirtualBox too. Yes, you can use master for your workloads. To do it, remove taints on the master/control plane node.

Hi, 1. SystemdCgroup = true # The documentaion about it kubernetes.io/docs/setup/production-environment/container-runtimes/#containerd-systemd 2. The issue with sandbox image: github.com/cri-o/cri-o/issues/6985 discuss.kubernetes.io/t/can-not-install-kubernetes-cluster-with-kubeadm/24079 ---- Note that the version of the sandbox image in each Containerd version can be changed so check it. For example, in my video, the version is 3.6 and now it is 3.8. The message while installing Kubernetes: W0725 06:32:35.829024 14158 checks.go:844] detected that the sandbox image "registry.k8s.io/pause:3.8" of the container runtime is inconsistent with that used by kubeadm.It is recommended to use "registry.k8s.io/pause:3.9" as the CRI sandbox image.

Hi, containerd config default | sed 's/SystemdCgroup = false/SystemdCgroup = true/' | sed 's/sandbox_image = "registry.k8s.io\/pause:3.6"/sandbox_image = "registry.k8s.io\/pause:3.9"/' | sudo tee /etc/containerd/config.toml

Hi, I will consider.

Hi, have you disabled swap? stackoverflow.com/questions/56737867/the-connection-to-the-server-x-x-x-6443-was-refused-did-you-specify-the-right Try to execute these commands on the master node: 1. sudo -i 2. swapoff -a

@@LearnDevOpswithSerge Thanks You Very Much

Hi, here it is: kzbin.info/www/bejne/iYbOkIGjaqechtk

Hi, I run virtual machines using VirtualBox and Vagrant.

Hi, containerd config default | sed 's/SystemdCgroup = false/SystemdCgroup = true/' | sed 's/sandbox_image = "registry.k8s.io\/pause:3.6"/sandbox_image = "registry.k8s.io\/pause:3.9"/' | sudo tee /etc/containerd/config.toml

@@LearnDevOpswithSerge how did you generate this command. any documentation for it. up till this stage you have explained everything in detail but just copied and pasted this out of nowhere. the tutorial is very great!

​ @christopherobinna2140 Hi, 1. SystemdCgroup = true # The documentaion about it kubernetes.io/docs/setup/production-environment/container-runtimes/#containerd-systemd 2. The issue with sandbox image: github.com/cri-o/cri-o/issues/6985 discuss.kubernetes.io/t/can-not-install-kubernetes-cluster-with-kubeadm/24079 ---- Note that the version of the sandbox image in each Containerd version can be changed so check it. For example, in my video, the version is 3.6 and now it is 3.8. The message while installing Kubernetes: W0725 06:32:35.829024 14158 checks.go:844] detected that the sandbox image "registry.k8s.io/pause:3.8" of the container runtime is inconsistent with that used by kubeadm.It is recommended to use "registry.k8s.io/pause:3.9" as the CRI sandbox image.

for me Culster set up is ready because of you but little issue my pods are not running properly when im using flannel but when i using calico now my pods are running

Hi, it is an IP of your master node. You can find out it by the command: "ip address show" or shortly "ip a". ``` vagrant@master:~$ ip address show | grep 192.168.1.50 inet 192.168.1.50/24 brd 192.168.1.255 scope global enp0s8 ```

@@LearnDevOpswithSerge Thank you! Do you have a video to show how to setup the kubernetes dashboard?

I haven't done it yet. Thanks for the idea!

@@LearnDevOpswithSerge also, the --pod-network-cidr, where did you find that?

@@user-oz2of8yq7z Hi, 2d item kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#initializing-your-control-plane-node

Hi, I guess you mean Flannel when talking about kube proxy. 1. Check logs of the crashed container: "kubectl -n <namespace> logs -p <pod-name>" 2. Check events of the pod in the 'CrashLoopBackOff' state: "kubectl -n <namespace> describe pod <pod-name>" 3. Analyze the information from the 1st and 2d list items.

did it worked for you ? I am facing some trouble when i try to init cluster, says its: st:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused. 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

Hi, I've already done it. Here is the link: kzbin.info/www/bejne/rXq9kqCwqZyAoa8si=FtIFKyaZZ_Hsh91V

Hi, I only did the steps that I showed in the video. Nothing else. First of all, look at your GitLab runner log. Maybe, there is some additional information in it. Try to recheck your config, values, and network connectivity between the Kubernetes cluster and GitLab Server.

Yes, I think the problem is with network connectivity in the Kubernetes cluster that I deployed via oracle cloud. I tried to curl and ping my self hosted gitlab and the results didn't work but for nslookup it worked. I'm still trying to find out why the pods can't access the internet. wish me luck

Hi, Thank you. Your idea is very good!)

Glad to hear it. You are welcome!

Hi, here it is: apiVersion: apps/v1 kind: Deployment metadata: name: nginx-deployment labels: app: nginx spec: replicas: 3 selector: matchLabels: app: nginx template: metadata: labels: app: nginx spec: containers: - name: nginx image: nginx:1.14.2 ports: - containerPort: 80 --- apiVersion: v1 kind: Service metadata: name: nginx spec: type: ClusterIP ports: - targetPort: 80 port: 80 selector: app: nginx

You are welcome!

Hi, Kubernetes has not supported Docker since version 1.24. Here is more information about it: kubernetes.io/blog/2022/02/17/dockershim-faq/

You are welcome!

Hi, containerd config default | sed 's/SystemdCgroup = false/SystemdCgroup = true/' | sed 's/sandbox_image = "registry.k8s.io\/pause:3.6"/sandbox_image = "registry.k8s.io\/pause:3.9"/' | sudo tee /etc/containerd/config.toml

@@LearnDevOpswithSerge thank you! Subscribed

Hi, thanks. I've never used runner behind the proxy. I'll try to help you. 1. Do you have connectivity from your corporate network with Gitlab server where you are going to register the runner? Try to check it from another pod or your computer. 2. What version of Gitlab Runner do you use? 3. Can you send me - configuration of the Gitlab Runner or values of your Helm chart - and logs of the gitlab runner? My email is [email protected]

Hi, I suppose the reason of your issue that in k8s version 1.24 the dockershim was removed (kubernetes.io/blog/2020/12/02/dockershim-faq/). Try buildah or kaniko to build images. These solutions work without docker daemon.

You are welcome!

Just mind blowing content Serge. Thanks alot. One request if you can make a tutorial on umbrella chart for a fullstack 3 tier app and then to deploy to Test and prod. It would be great. Also, make another tutorial to combine kustomize with helm together for deploy the same fullstack app. No tutorial anywhere for such knowledge. Thanks in advance.

@@softwareengineer5764 Hi, I will consider it.

Hi. If you follow all recommendations, there will not be any issues with your GitLab server. Of course, you can do it on the test server for practise and then upgrade your production server. Don't forget to make backups and after all upgrade your GitLab runners for compitability.

Thanks