@Pavan Elthepu, You are videos are great. Thank you so much for your efforts. at 12:14 I think required during scheduling should be marked as hard in that table. Please correct me if I am wrong?
Great content Pavan! Thank you! By the way, could you tell me the k8s yaml extension you’re using? Mine doesn’t have auto complete function for k8s yaml format.
Yes true. Both work on the labels. But the main thing is that there are two labels. One is associated with the pod which is mentioned in the deployment.yaml file such a selector and labels. And another one is node label. Which can be given with the help of "kubectl label node nodename key=value".. So there is not only one label there are two labels. One is pod label which is given in the yaml file and another one is node label which is given in the command.
i tried same with nodeSelector field please help me to resolve ------- in my case there is 4 node cluster architecture,one is master and remaining are workers, i created pv on worker2,and i want to schedule all pods of application on worker1 i labeled worker1 as kubectl label node worker1 worker1: tmlabs-hp-280-g2-mt ---- #deployment.yaml nodeSelector: worker1: tmlabs-hp-280-g2-mt ------ Error:::: 0/4 nodes are available: 1 node(s) didn't match Pod's node affinity/selector. preemption: 0/4 nodes are available: 1 Preemption is not helpful for scheduling, 3 No preemption victims found for incoming pod..
Deserve for more subscribers. Very clear explanation.step by step Thankyou so much. Please do more real time tasks
Neat Explaination, thanks
Very underrated video
Superb bro, Thanks 😊
You are AWESOME, Pavan! You'd simplified so well. Appreciate your hard work for sharing this. :)
Thank you. Please subscribe and share with your friends and colleagues👍
@@PavanElthepu done and will share as well :)
Your videos are crystal clear with the concepts..
Thank you so much Mohammed. Please share with your friends and colleagues
@@PavanElthepu sure
Superb !! Thanks for being meticulous .. Cleared my concepts in one go
Good explanation skill. Keep it up...
awsome lession you are really great..
Please cover deployment strategy and kubernetes network policy also
Awesome video, great job 🎉
Thank you Ben Wilkinson. Please subscribe and share with your friends and colleagues
This tutorial is very useful!
Thank you. Please subscribe and share with your friends and colleagues
Please make a video that how we increase pods more than 110 pods in a node
Thank you Pavan , crystal clear your concept,. What about node antiaffinity .
Awesome tutorial man
Thank you so much Vimal. Please subscribe and share with your friends and colleagues
@@PavanElthepu I already liked and subscribed
@Pavan Elthepu, You are videos are great. Thank you so much for your efforts.
at 12:14 I think required during scheduling should be marked as hard in that table. Please correct me if I am wrong?
best ever
Thank you. Please subscribe and share with your friends and colleagues
Great 👍
Good content
Thank you Suresh. Please subscribe and share with your friends and colleagues
Hey buddy please make a detailed video on Helm charts
Yes, already on it Mohammed
Thank you so much..
Hi Pavan, will you provide online classes for AWS & DevOps?
Please connect on LinkedIn
Great content Pavan! Thank you! By the way, could you tell me the k8s yaml extension you’re using? Mine doesn’t have auto complete function for k8s yaml format.
You can install YAML and Kubernetes extensions in VS Code
Thank you! :)
Pod Topology Spread Constraints?
Hi RK! I will try to cover that as a separate video
@@PavanElthepu Thanks Pavan, you never disappointed me waiting for the video.
What is the next video you're expecting?
@@PavanElthepu
Pod Topology Spread Constraints ☺️☺️
🙂🙂
Superb bro, Thanks 😊
@PavanElthepu thanks for your efforts..is it possible to make videos on local k8s cluster or rancher instead of aws or aks for quick practice
Throughout the series I used minikube, which is a local cluster
16:58 = May I know how did you fix the indentation? Thank you.
I just hit tab
Super Pavan.. Thank you for dedicating your valuable time to everyone ....
Really nice bro. Crystal clear Explanation 👏👏👏
you are best and what a great and simple explanation, request you to kindly make new videos on terraform tool also.
Sire Shailendra. Stay tuned. Please share with your friends and colleagues
Thank you pavan you explained the concept with realtime which make more understandable.
Glad that you liked. Please subscribe and share with all your friends and colleagues
Great vedios.. nice explanation ..
Amazing explation skill ever seen by a youtuber crip and crystal clear!
Thank you Srinivas. Please share with your friends and colleagues
Super helpful
Wonderfull explanations. Thank a lot.
Thank you Sagar. Please subscribe and share with your friends and colleagues
superb video
sir pod affinity and node affinity both works on labels so how come they are different?
Sorry, I didn’t get it Rohan. Could you please elaborate your question please.
Yes true. Both work on the labels. But the main thing is that there are two labels. One is associated with the pod which is mentioned in the deployment.yaml file such a selector and labels.
And another one is node label. Which can be given with the help of "kubectl label node nodename key=value"..
So there is not only one label there are two labels. One is pod label which is given in the yaml file and another one is node label which is given in the command.
i tried same with nodeSelector field
please help me to resolve
-------
in my case there is 4 node cluster architecture,one is master and remaining are workers,
i created pv on worker2,and i want to schedule all pods of application on worker1
i labeled worker1 as
kubectl label node worker1 worker1: tmlabs-hp-280-g2-mt
----
#deployment.yaml
nodeSelector:
worker1: tmlabs-hp-280-g2-mt
------
Error::::
0/4 nodes are available: 1 node(s) didn't match Pod's node affinity/selector. preemption: 0/4 nodes are available: 1 Preemption is not helpful for scheduling, 3 No preemption victims found for incoming pod..