At 34:00 duration, just need one clarification. While editing command 'echo' under demo pod . Can we just run command kubectl replace --force -f (temporary file generated.yaml) ------------as its not allowing us to edit the original demo pod YAML file. Is this fine from exam point of view as here i am forcefully deleting existing pod and replacing the same with new one ? Kindly confirm.
If pod events are not displaying in Kubernetes, several factors could be at play. Insufficient permissions, cluster issues, event retention policies, misconfigured logging or monitoring setups, or API server problems might be causing this. To troubleshoot, ensure proper permissions, check the cluster's health, review logging configurations, and verify the event retention policy.
Please Verify the kubelet configuration files (kubelet.conf or /etc/kubernetes/kubelet) to ensure they are correctly set up. Common configuration issues include incorrect API server endpoints, certificates, or improper flags. And try restarting kublet
At 17.00 duration, why you perform the steps to move apiserver.yaml file . I think you can skip this step because as far as i know if we modify/update anything under kube-apiserver.yaml file then kubeadm tool will automatically restart kube-apiserver static pod. Sorry, you can correct me in case if I am wrong.
Hi! Actually we are moving the file out of the location where kubelet will look and it won't find it there then once the file is available then it will restart the pod. This is just one way of restarting the static pods. .. Yes you are correct we have other ways too as the video explains. Thank you
Hi there, you can join our live batches for [CKA] Docker & Certified Kubernetes Administrator and ask questions during the live sessions. If you're interested, here's the link for the same: k21academy.com/kubernetes
why suddenly error came like did u specify right host or port came in between .... suddenly api-server stop working in between ................. its fluctuating like situation came in between please guide in this sir.......................... cant get any proper solution over the internet
To start using the cluster set the environment variable $ cp /etc/kubernetes/admin.conf $HOME/ $ chown $(id -u) $HOME/admin.conf $ export KUBECONFIG=$HOME/admin.conf $ echo 'export KUBECONFIG=$HOME/admin.conf' >> $HOME/.bashrc try this if does not work then try kubeadm reset.
💼Join our free Docker & Kubernetes class to get certified: bit.ly/3W5hu0Q
Fantastic, and very practical, video on troubleshooting all sorts of K8s issues. This is really good stuff.
Glad you liked it! 😊
Please do let us know what videos you'll like to see next?
One of the best videos I have seen on k8s troubleshooting ....
We believe in giving the best to our people. Thanks, keep watching!
Thank you. Excellent practical session on kubernetes troubleshooting. 👍
Glad you liked it! 😊
Please do let us know what videos you'll like to see next?
Very good troubleshooting and explaining!!
Glad you like it !
Excellent video!!!
Glad you liked it! Do let us know what video you’d like to see next?
At 34:00 duration, just need one clarification. While editing command 'echo' under demo pod . Can we just run command kubectl replace --force -f (temporary file generated.yaml) ------------as its not allowing us to edit the original demo pod YAML file. Is this fine from exam point of view as here i am forcefully deleting existing pod and replacing the same with new one ? Kindly confirm.
Yes, you can do that as well.
best video on Tshoot
Thanks for your kind words. This keeps us motivated. Do let us know what videos you'd like to see next?
Awesome buddy 💖💐💐💐🙏🙏🙏
Best video for troubleshooting ❤
Thank you for the awesome training sir.
Glad you liked it! 😊
Please do let us know what videos you'll like to see next?
One of the best videos. Thanks you sir for knowledge sharing
You are most welcome
A Great one!! Thanks for this.
Hi, Thanks. Do let us know what videos you'd like to see next?
if in event is not showing what to do
If pod events are not displaying in Kubernetes, several factors could be at play. Insufficient permissions, cluster issues, event retention policies, misconfigured logging or monitoring setups, or API server problems might be causing this. To troubleshoot, ensure proper permissions, check the cluster's health, review logging configurations, and verify the event retention policy.
This is very much usefull...Thanks..!!
Hey, thanks for watching. Do let us know what videos you'd like to see next?
Very interested & very important
Glad you think so!
Thanks😊
Welcome 😊
Can u guide me on the error that kubelet is activating......... Please guide sir
Please Verify the kubelet configuration files (kubelet.conf or /etc/kubernetes/kubelet) to ensure they are correctly set up. Common configuration issues include incorrect API server endpoints, certificates, or improper flags. And try restarting kublet
At 17.00 duration, why you perform the steps to move apiserver.yaml file . I think you can skip this step because as far as i know if we modify/update anything under kube-apiserver.yaml file then kubeadm tool will automatically restart kube-apiserver static pod. Sorry, you can correct me in case if I am wrong.
Hi!
Actually we are moving the file out of the location where kubelet will look and it won't find it there then once the file is available then it will restart the pod. This is just one way of restarting the static pods. ..
Yes you are correct we have other ways too as the video explains.
Thank you
Thank you
Hey, thanks for this video, how can be present during those live video.
Hi there, you can join our live batches for [CKA] Docker & Certified Kubernetes Administrator and ask questions during the live sessions. If you're interested, here's the link for the same: k21academy.com/kubernetes
why suddenly error came like did u specify right host or port came in between .... suddenly api-server stop working in between ................. its fluctuating like situation came in between
please guide in this sir.......................... cant get any proper solution over the internet
To start using the cluster set the environment variable
$ cp /etc/kubernetes/admin.conf $HOME/
$ chown $(id -u) $HOME/admin.conf
$ export KUBECONFIG=$HOME/admin.conf
$ echo 'export KUBECONFIG=$HOME/admin.conf' >> $HOME/.bashrc
try this if does not work then try kubeadm reset.