How to Install Kubernetes Cluster on Ubuntu 20.04 LTS with kubeadm | Install Kubernetes on Ubuntu

[@srikanth4041]

i have followed all the video and i could able to setup the cluster thanks for making great video.

[@DevOpsHint]

Thanks for sharing your feedback 👍

[@visva2005]

Hi thanks for the video . EC2 t.medium is free or needs to pay ??

[@DevOpsHint]

It is free in free tier, check details in official AWS page aws.amazon.com/ec2/instance-types/t2/#:~:text=Available%20on%20the%20AWS%20Free,of%20Linux%20and%20Windows%20t2.

[@ksubrahmanyam7747]

medium is not free tier

[@srikanth4041]

the only thing is we need to open the port for TCP with 6443 which means Kubernetes API Server is Running on 6443 and all nodes should communicate to API Server if we open this port in AWS, just add it in security group.

[@DevOpsHint]

Thanks for your update. Will update in videos description 👍

[@matross3097]

Please share the commands here. Thanks.

[@venkatvarun9790]

Hi Sir one small doubt please give me solution while entering "sudo kubeadm init --pod-network-cidr=192.168.10.0/24" it tells us to wait 4 minutes then after error coming why? sir.

[@DevOpsHint]

Please share error logs.

[@jumeirjme3736]

i have the same problem

[@itocean6628]

I am having the same issue...after run kubeadm init 192....

[@deverse]

thanks

[@chethannag7389]

Hi, when i run the kubeadm command(sudo kubeadm init --pod-network-cidr=192.168.10.0/24) getting the below error, Can you please help how to solve this issue??? [kubelet-check] The HTTP call equal to 'curl -sSL localhost:10248/healthz' failed with error: Get "localhost: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 Kubernetes containers running in docker: - 'docker ps -a | grep kube | grep -v pause' Once you have found the failing container, you can inspect its logs with: - 'docker 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

[@amulya269]

Did you find the solution for this?

[@amulya269]

Any solution?

[@indrakumar1928]

Same error. Do you have any solution?

[@itocean6628]

Same error

[@RameshKumar-rt8xb]

the article link in the description has a different process