Hi again. After making it work. It is time for me to create a snapshot of each server. What it is the step by step procedure to properly shutdown the K8s cluster. Which commands, services, and so should be stopped and in what order? Thank you again and regards
Thanks for the great tutorial; do you have a list of task to be done when when building a AKS cluster on azure? (so K8 cluster with cloud control manager)
Hi Brother, A pod is an k8s object that can spin/run only in one node. In the last step, since we haven't mentioned any node selection criteria, a random node is picked up by the scheduler to the pod. Hope this clarifies !
I don't get it, shouldn't be able to get info and manage the cluster from our host ( in our case is windows ) and not from the master itself, I mean when you do Kubectl get nodes, we Get all the nodes but why are we on the master node ? aren't we supposed to see the cluster from another host not from the master itself
Hi Ceci Ivanov, Yes of course you can the cluster details from your windows machine itself. Provided you should have installed the kubectl binary for windows in your local machine & update the Kube config file. That's it ! In this video we have used master node itself for the sake of simplicity. Thanks
I want to ask one more thing regarding Kubeadm init , if i shut down accidently the Master node having running the all the services, if master gets shut down accidently how could run again the same cluster upon rebooting the system? Given that Now Master VM ip address is changed. Should i have to do from scratch again all installations? Please need guidelines please..
Hi Eshan, The best practice is,.. the master node IP's should be static in nature. For your case, once the master node turns came up, you need to update the kubeconfig file location in the master node (May be you need to set the location as an environmental variable) + have to start the Kubelet just incase if it is not started automatically.
Hi Buddy, Seems docker has stopped its support to kubernetes from v1.24. you can consider the other container runtimes instead of docker. once such example is below (CRIO) ### Installing Container Runtime export OS=CentOS_8 export VERSION=1.26 curl -L -o /etc/yum.repos.d/devel:kubic:libcontainers:stable.repo download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/$OS/devel:kubic:libcontainers:stable.repo curl -L -o /etc/yum.repos.d/devel:kubic:libcontainers:stable:cri-o:$VERSION.repo download.opensuse.org/repositories/devel:kubic:libcontainers:stable:cri-o:$VERSION/$OS/devel:kubic:libcontainers:stable:cri-o:$VERSION.repo yum install -y cri-o systemctl enable --now crio Thanks
I got strucked at this 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. Please resolve the issue
Hi Sandeep, If the kubelet is not running, then its probably because of the firewall that is blocking its access. Plz disable the firewall and try again. Plz follow the step by step procedure as mentioned in the video description.
Thanks for the tutorial, when I tried to do kubeadm init I was getting below error. Can you please help me out. [ERROR CRI]: container runtime is not running: output: time="2023-08-14T10:39:16Z" level=fatal msg="validate service connection: CRI v1 runtime API is not implemented for endpoint \"unix:///var/run/containerd/containerd.sock\": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService"
Hi Sathish, if you are using docker as a CRT then this error may come as docker stopped its support for k8s from 1.25. Try to use other container runtimes instead of docker. FYI .. Installation of CRI-O is given in the description. Thanks
Hello, I have errors on step 7, the kubelet service is down and when running its command /usr/bin/kubelet, I got an error about step 6 and cgroups: "Failed to get the kubelet's cgroup. Kubelet system container metrics may be missing." err="cpu and memory cgroup hierarchy not unified. cpu: /, memory: /user.slice/user-0.slice/session-3.scope"
I have got this error when using kubernetes init : [init] Using Kubernetes version: v1.26.0 [preflight] Running pre-flight checks error execution phase preflight: [preflight] Some fatal errors occurred: [ERROR CRI]: container runtime is not running: output: E0106 21:48:19.883611 25351 remote_runtime.go:948] "Status from runtime service failed" err="rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService" time="2023-01-06T21:48:19Z" level=fatal msg="getting status of runtime: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService" , error: exit status 1 [ERROR FileContent--proc-sys-net-bridge-bridge-nf-call-iptables]: /proc/sys/net/bridge/bridge-nf-call-iptables contents are not set to 1 [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` To see the stack trace of this error execute with --v=5 or higher
from brazil 🇧🇷
tnks, man! awesome video, it helped me so much ❤️❤️
My pleasure :)
Thanks for posting.
No problem
Had you video that elaborates on Step 6 ? Perhaps with podman/cri-o ?
Hey, Sorry i don't have it at the moment.
Hi again.
After making it work. It is time for me to create a snapshot of each server.
What it is the step by step procedure to properly shutdown the K8s cluster.
Which commands, services, and so should be stopped and in what order?
Thank you again and regards
Thank you very much!!! You saved my life!!!
My Pleasure !!!
Thanks for the great tutorial; do you have a list of task to be done when when building a AKS cluster on azure? (so K8 cluster with cloud control manager)
Hi, Thanks for your comments...
Sorry ..We havent started our videos on Azure.
Why are we using docker in step 3 instead of Kubernetes?
Thanks a million !!! 😊
You are welcome !
to start cluster why i need to run from regular user ???
Thank you..
Thanks a ton 👏
Hi bro, why the pod is only ddployed on worker1 not both in the last step. Thank
Hi Brother, A pod is an k8s object that can spin/run only in one node. In the last step, since we haven't mentioned any node selection criteria, a random node is picked up by the scheduler to the pod. Hope this clarifies !
@@VSPARKZ thanks Bro.
Thanks
Awesome vid dude
That's my Pleasure.. Stay tune for more videos !
Why master node needs docker runtime and kubelet, please can you explain
Hi, even the master node will run the control plane components as container's only and so it needs CRT & kubelet
hi, i have a question, why you run
kubectl run vspark --image nginx
in master-node,
when you get pod, it show node worker01?
Hi, Its just a testing whether we are able to run a pod in the created cluster ! Nothing else.
Thanks
Hey bro can you please make a video on gcp cloud KMS or secret Manager
Hi Nishit,
Definitely I will make it for you. Please allow us some time.
Thanks
I don't get it, shouldn't be able to get info and manage the cluster from our host ( in our case is windows ) and not from the master itself, I mean
when you do Kubectl get nodes, we Get all the nodes but why are we on the master node ?
aren't we supposed to see the cluster from another host not from the master itself
Hi Ceci Ivanov, Yes of course you can the cluster details from your windows machine itself. Provided you should have installed the kubectl binary for windows in your local machine & update the Kube config file. That's it ! In this video we have used master node itself for the sake of simplicity. Thanks
I want to ask one more thing regarding Kubeadm init , if i shut down accidently the Master node having running the all the services, if master gets shut down accidently how could run again the same cluster upon rebooting the system? Given that Now Master VM ip address is changed. Should i have to do from scratch again all installations? Please need guidelines please..
Hi Eshan, The best practice is,.. the master node IP's should be static in nature. For your case, once the master node turns came up, you need to update the kubeconfig file location in the master node (May be you need to set the location as an environmental variable) + have to start the Kubelet just incase if it is not started automatically.
I'm getting yum not located. Not able to install it on ubuntu. Any fix?
Hi Akash, Yum is not a package manager for ubuntu, instead of yum try to use "apt-get" in case of ubuntu.
Thanks
currently, docker not allowing us to use as a container runtime why?
Hi Buddy,
Seems docker has stopped its support to kubernetes from v1.24. you can consider the other container runtimes instead of docker. once such example is below (CRIO)
### Installing Container Runtime
export OS=CentOS_8
export VERSION=1.26
curl -L -o /etc/yum.repos.d/devel:kubic:libcontainers:stable.repo download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/$OS/devel:kubic:libcontainers:stable.repo
curl -L -o /etc/yum.repos.d/devel:kubic:libcontainers:stable:cri-o:$VERSION.repo download.opensuse.org/repositories/devel:kubic:libcontainers:stable:cri-o:$VERSION/$OS/devel:kubic:libcontainers:stable:cri-o:$VERSION.repo
yum install -y cri-o
systemctl enable --now crio
Thanks
I got strucked at this
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.
Please resolve the issue
Hi Sandeep, If the kubelet is not running, then its probably because of the firewall that is blocking its access. Plz disable the firewall and try again.
Plz follow the step by step procedure as mentioned in the video description.
hi bro how to create 3 node in terminal with different ip address
Hi Mate,
You can install any local vm box like oracle vm box, vmware workstation.. etc., to create distinct vm's with different IP's.
Thanks
Thanks for the tutorial, when I tried to do kubeadm init I was getting below error. Can you please help me out.
[ERROR CRI]: container runtime is not running: output: time="2023-08-14T10:39:16Z" level=fatal msg="validate service connection: CRI v1 runtime API is not implemented for endpoint \"unix:///var/run/containerd/containerd.sock\": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService"
Hi Sathish, if you are using docker as a CRT then this error may come as docker stopped its support for k8s from 1.25. Try to use other container runtimes instead of docker.
FYI .. Installation of CRI-O is given in the description.
Thanks
Hello, I have errors on step 7, the kubelet service is down and when running its command /usr/bin/kubelet, I got an error about step 6 and cgroups:
"Failed to get the kubelet's cgroup. Kubelet system container metrics may be missing." err="cpu and memory cgroup hierarchy not unified. cpu: /, memory: /user.slice/user-0.slice/session-3.scope"
The solution for now was to move or delete this file /etc/containerd/config.toml, then $ systemctl restart containerd
I have got this error when using kubernetes init :
[init] Using Kubernetes version: v1.26.0
[preflight] Running pre-flight checks
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR CRI]: container runtime is not running: output: E0106 21:48:19.883611 25351 remote_runtime.go:948] "Status from runtime service failed" err="rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService"
time="2023-01-06T21:48:19Z" level=fatal msg="getting status of runtime: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService"
, error: exit status 1
[ERROR FileContent--proc-sys-net-bridge-bridge-nf-call-iptables]: /proc/sys/net/bridge/bridge-nf-call-iptables contents are not set to 1
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higher
had the same issue. You need to remove the config file and restart the service:
rm /etc/containerd/config.toml
systemctl restart containerd
@@MrDanik011
rm -rf /etc/containerd/config.toml
systemctl restart containerd
thank youuuuuuuuuu @@MrDanik011