Security context: runasuser, runasgroup, fsgroup, capabilities: - to add linux capabilities: add or drop: like Linux_ADMIN Can be at pod level or container level
Thank you for your excellent teaching skills and the valuable visuals that greatly enhance the learning experience. Looking forward to future topics like Kubernetes network CNI, kube-dns, and an end-to-end project.
Congratulations on clearing the CKA, Achieving a 74% score in your first attempt is commendable. Well done on your hard work and dedication. Keep up the excellent work, and may you continue to achieve great success in your future endeavours!
excellent tutorials....Thank you so much. Please make similar in detail videos for terraform, Ansible, Helm charts, Github Actions Ci/CD, Jenkins Ci/CD :)
Security context give container only those capabilities access , required only to run the application tasks. That's how you increase it's security. Pod security context will inherit to all containers of multi container pod. container level security is higher priority. It will be preferred.
Maim m from pakistan exlent ap ny explain kya h but i hv a question userID or other ID,s jo ap ny mention ki hain ya user create hony chahya pehly sy or ya ID apny suppose kr k dali h??
Thank you for your positive feedback! In the video, I mentioned the userID and other IDs as examples for demonstrating the implementation of security context in Kubernetes. These IDs can be customized based on your specific requirements. They don't necessarily have to be pre-existing user IDs, but you can choose appropriate values for them. The purpose is to showcase how security context can be applied at the pod and container levels to ensure secure deployments of your applications. I hope this clarifies your question. If you have any further inquiries, feel free to ask!
In Kubernetes, not everything is a POD. While PODs are like the basic building blocks, there are also other important things like Services, Deployments, and ConfigMaps. These help manage different parts of your apps running in containers. Each of these does a specific job in making sure your apps run well together.
We've covered almost all topics except troubleshooting. We're now focusing on creating videos on different tools. If you have any specific topics in mind, let us know!
Ma'am, Could you please provide some clarity on how RBAC authorization and Security Contexts differ in their functions within a Kubernetes cluster? Any examples or use-cases would be greatly appreciated to help enhance my understanding.
RBAC authorization in Kubernetes controls access to cluster resources based on user roles and permissions, while Security Contexts define security settings at the pod or container level, such as user IDs, group IDs, and privileges. An example use-case could be granting a user read-only access (RBAC) while ensuring their containers run with non-root privileges (Security Context).
Hi it's an informative video. Also please can you make video on multiple ingress controllers for multiple application on multiple namespace. That will be helpful 👍
Thank you! This series covers almost all the topics required for the CKA exam, providing a solid foundation. However, I recommend supplementing it with additional practice and hands-on experience to maximise your chances of success in the exam.
Hi Riya, Can you please let me know when we add another ip in eth0 inside a container then can we access the same container via 2nd ip ie at that moment we have 2 IPs for same container. Can we add security context in case of deployment?
When you add another IP address to the eth0 network interface inside a container, you can indeed access the container using both IP addresses. Each IP address will be associated with the container's network interface, allowing incoming connections on both IPs. Regarding your second question, yes, security context can also be applied in the case of deployments. I hope this clarifies your doubts.
I have 2 more doubts when the POD died and recreate then is there any way to configure 2 IPs which can communicate with related service. 2: is it possible security context can apply on cluster level if yes then can you make a video where we can practically see how to protect the cluster from intruders.
1. When a Pod dies and is recreated, the IP address associated with it may change. Kubernetes assigns IP addresses dynamically to Pods, so there's no direct way to configure specific IP addresses for a Pod to communicate with related services after recreation. However, you can use services in Kubernetes, such as ClusterIP or NodePort, which provide stable endpoints for communication with Pods. 2. Security context can be applied at both the Pod and container level. However, applying security context at the cluster level is not possible.
mam please ek video banado kubeadm say aws ec2 instances par cluster setup krna. Please step by step guide bnado I mean kha kha say cheeza search kara and eksa setup kara sabkuch. Master and worker nodes kesa bnaya etc
Please help us with your valuable feedback - forms.gle/E9r3xvTxnLPKz9Hw9
Aapke concepts bohot crisp and clear hai, maine youtube me Kubernetes kaa isse achee lecture kahi nahi dekha.
Hats off to your hard work🫡
Superb i recommend everyone she is great teacher of kubernetes awesome explanation mam 👍👍
Thank you for the kind words and recommendation! I appreciate your support
Nice. Please make and upload more videos on kubernetes networking part.
Security context:
runasuser, runasgroup, fsgroup, capabilities: - to add linux capabilities: add or drop: like Linux_ADMIN
Can be at pod level or container level
All mentioned can apply at both levels except capabilities, capabilities setting can only be applied at the container level, not at the pod level.
Wow!!!
Best explanation!!!!!
thanks for this video mam
Please keep making such videos!!!!!!!!
Awesome explaination!!!!!
This series is making everyone easy for k8s ... thanks for updating new concept
Glad to hear that
please bring more videos like this because these videos are the main game
Thank you for your feedback and support! More videos like this are on the way! 🎉
Thank you for your excellent teaching skills and the valuable visuals that greatly enhance the learning experience. Looking forward to future topics like Kubernetes network CNI, kube-dns, and an end-to-end project.
the animation used very useful to understand conecpts
Thanks
Very will explained 👌
The best way of explanation I have seen....awesome
Appreciate your kind words! 🙏
Such a nice leacture, really thankfull!!
Please create an tutorial on HPA, metrics servers and monitoring.
Sure, will create!
please upload more video about kubernetes
best k8 playlist . please frequently post the videos. next helmchart and real time scenarios.
Noted
Very informative content
Very very important
Thanku so much!!
Thanks Sandeep
Hi Riya, I have just cleared CKA with 74% in my frst attempt itself
Congratulations on clearing the CKA, Achieving a 74% score in your first attempt is commendable. Well done on your hard work and dedication. Keep up the excellent work, and may you continue to achieve great success in your future endeavours!
Me - 96%😅
excellent tutorials....Thank you so much. Please make similar in detail videos for terraform, Ansible, Helm charts, Github Actions Ci/CD, Jenkins Ci/CD :)
Very soon and Thank you so much for your kind words.
doing gr8 job..u deserve more subs...u handled such complex topic with ease..nicely done
Thank you so much! Your support means a lot. I'm glad you found the channel helpful. 😊
Security context give container only those capabilities access , required only to run the application tasks. That's how you increase it's security.
Pod security context will inherit to all containers of multi container pod.
container level security is higher priority. It will be preferred.
Very useful information.please add troubleshooting steps
Sure, Noted
Maim m from pakistan exlent ap ny explain kya h but i hv a question userID or other ID,s jo ap ny mention ki hain ya user create hony chahya pehly sy or ya ID apny suppose kr k dali h??
Thank you for your positive feedback! In the video, I mentioned the userID and other IDs as examples for demonstrating the implementation of security context in Kubernetes. These IDs can be customized based on your specific requirements. They don't necessarily have to be pre-existing user IDs, but you can choose appropriate values for them. The purpose is to showcase how security context can be applied at the pod and container levels to ensure secure deployments of your applications. I hope this clarifies your question. If you have any further inquiries, feel free to ask!
immensely way to explain. SUPERB👍
Thank you so much 😀
Is UserId 1000 created initially?
how it is created
and also group id
im confused with those ids
please explain
superb animation, best explanation keep it up.
Thanks
ye hacker ko access kaise mil sakta h, you mean ki us cluster ka master node ssh pe hacker ne access kar lia or wo kubectl command run kar skta tha?
Hello Can we say everything in Kubernetes is a POD. I was asked this question in an interview, Not sure how to answer this.
In Kubernetes, not everything is a POD. While PODs are like the basic building blocks, there are also other important things like Services, Deployments, and ConfigMaps. These help manage different parts of your apps running in containers. Each of these does a specific job in making sure your apps run well together.
Mam please istio service mesh bhi ek video banado na
Will consider your suggestion for future content. Stay tuned!
@@DevOpsPro thank you for replying... truly ur way of teaching and the topics u have covered are just awesome
Great
Please make a detailed video on k8s networking
Very Good
Thanks
Hey Riya,
Was this the last video of kuberntes.
Any other topics are remaining ?
We've covered almost all topics except troubleshooting. We're now focusing on creating videos on different tools. If you have any specific topics in mind, let us know!
ma'am more security realted videos please
Ma'am, Could you please provide some clarity on how RBAC authorization and Security Contexts differ in their functions within a Kubernetes cluster? Any examples or use-cases would be greatly appreciated to help enhance my understanding.
RBAC authorization in Kubernetes controls access to cluster resources based on user roles and permissions, while Security Contexts define security settings at the pod or container level, such as user IDs, group IDs, and privileges. An example use-case could be granting a user read-only access (RBAC) while ensuring their containers run with non-root privileges (Security Context).
Mam helm par video banye
@DevOpsPro please make video on kubernetes cluster autoscaling
Thanks for your request! I'll definitely create a video on Kubernetes cluster autoscaling. Stay tuned for the upcoming tutorial!
Please can you explain what is oAuth and oidc ?
Your Videos Were very helpful , but you didn't covered various topics such as Hpa and all. it would be very helpful if you make videos on same.
Thank you for the feedback! Will consider covering HPA in future videos.
Can you please make a video on k8s operators and CRD
Hi it's an informative video. Also please can you make video on multiple ingress controllers for multiple application on multiple namespace. That will be helpful 👍
Sure I will
@@DevOpsPro Yes looking for it asap.Thank you!
Hey hi, When can we expect the above mentioned related topic video?
@@DevOpsProwaiting for the requested video
I am also waiting for above mentioned topic videos.
Great Content , Mam is this series complete, is it enough to crack cka exam
Thank you! This series covers almost all the topics required for the CKA exam, providing a solid foundation. However, I recommend supplementing it with additional practice and hands-on experience to maximise your chances of success in the exam.
Thanks madam
Hi Riya,
Can you please let me know when we add another ip in eth0 inside a container then can we access the same container via 2nd ip ie at that moment we have 2 IPs for same container.
Can we add security context in case of deployment?
When you add another IP address to the eth0 network interface inside a container, you can indeed access the container using both IP addresses. Each IP address will be associated with the container's network interface, allowing incoming connections on both IPs.
Regarding your second question, yes, security context can also be applied in the case of deployments. I hope this clarifies your doubts.
I have 2 more doubts when the POD died and recreate then is there any way to configure 2 IPs which can communicate with related service.
2: is it possible security context can apply on cluster level if yes then can you make a video where we can practically see how to protect the cluster from intruders.
1. When a Pod dies and is recreated, the IP address associated with it may change. Kubernetes assigns IP addresses dynamically to Pods, so there's no direct way to configure specific IP addresses for a Pod to communicate with related services after recreation. However, you can use services in Kubernetes, such as ClusterIP or NodePort, which provide stable endpoints for communication with Pods.
2. Security context can be applied at both the Pod and container level. However, applying security context at the cluster level is not possible.
Mam kubernetes autoscaling concept missing hn is series mai plz add
Sure, will consider adding Kubernetes autoscaling in future content. Thanks for the suggestion! 🙏
Could you please make video on istio and complete process how we are using it end to end in kubernetes, still waiting for this
Thanks for your suggestion! I'll definitely consider creating videos on Istio. Stay tuned for updates!
mam please ek video banado kubeadm say aws ec2 instances par cluster setup krna. Please step by step guide bnado I mean kha kha say cheeza search kara and eksa setup kara sabkuch. Master and worker nodes kesa bnaya etc
Can you make videos on istio with kubernetes
Sure, I'll consider it for future content. Thanks for the suggestion!
Also is this series completed ?
HPA m video bnao 🦋🫂🥰
Hi
Please make istio vedio
Absolutely! Thanks for your suggestion! I'll definitely consider creating videos on Istio.
Yes please make video on istio with kubernetes