HOw do u differentiate between first kubelet (worker node1)and second kubelet (workernode1 ) while checking logs of kubelet.Means uhave not used command like kubelet1 and kubelet2 . HOw the system will understand whether it is for workernode 1 workernode2?
In the exam, I noticed that service is dead and even disabled. Make sure u start and enable because he said the changes should persist permanently. systemctl enable --now kubelet or systemctl start kubelet and systemctl enable kubelet. So even if node is restarted the kubelet would be running.
I am watching your tech talks on youtube. Those are really insightful ! I really like Kubernetes zero to hero series. I really wish to watch your AWS zero to hero series. Can you please make one for AWS as well.
thank you for your playlist. please do a kubernetes/containerization network series too!! i would really appreciate that
Very well organized explanation, I am happy on this journey, thanks Piyush!!!
Keep it going, only 3 videos left to conclude one of many journeys to come 💪
great content
Thanks for the great content
Glad you enjoy it!
Thanks, actually you did a great job!
Thank you for the feedback 🙂 happy to help
thank you sir , for this playlist
Welcome buddy!
Really useful to me
Thank you
Thank you bro 😎
You're welcome bro :)
Thanks Piyush
welcome 🤗
Good one
Thank you! Cheers!
HOw do u differentiate between first kubelet (worker node1)and second kubelet (workernode1 ) while checking logs of kubelet.Means uhave not used command like kubelet1 and kubelet2 . HOw the system will understand whether it is for workernode 1 workernode2?
Kubelet runs on the worker node itself. You have to ssh into the respective node to run kubelet commands. Let me know if you still have any doubts
hi piyush do containers have same static IP address or does it keep changing
Pod IP will change whenever it restarts
which next course you teach ? k8s application developer ?
2 more videos pending in this series, after that I will start a poll and ask everyone
In the exam, I noticed that service is dead and even disabled. Make sure u start and enable because he said the changes should persist permanently. systemctl enable --now kubelet or systemctl start kubelet and systemctl enable kubelet. So even if node is restarted the kubelet would be running.
Do not forget this. As you will lose marks.
That is true, I think I covered that part, didn't I? Even if I did not cover in this video, it is covered in Day 41 video.
I am watching your tech talks on youtube. Those are really insightful ! I really like Kubernetes zero to hero series.
I really wish to watch your AWS zero to hero series. Can you please make one for AWS as well.
Thank you for the feedback, I will try in the near future