Hi Ravish , thanks for capturing the interview with scenario based questions . This is Rashmi here I have been following your channel and the Interview playlist is very useful. Just an improvement I would like to suggest, is it possible to segregate these videos as Kubernetes , AWS , Docker and Linux , Git(separate) folders ? that will be very helpful to locate the exact videos while watching them . Thanks
Namespaces are nothing but Projects by using it we are segregating pods as per applications. Also we can set Resource Quota on namespaces so pods will not utilise all resources of the Nodes.
when its started initially sound quality was good to understand but in few seconds later quality was not good enough to understand. keep voice as good to understand, anyway its helpful. will be more helpful if you are creating content by own que and Answers
Public AKS Cluster: Typically uses an Azure Load Balancer for services exposed to the internet. Private AKS Cluster: Can use an Internal Load Balancer for services within a VNet or rely on ClusterIP if services do not need external access. In production environments, whether you use an external load balancer, an internal load balancer, or none at all depends on your specific needs for traffic distribution, security, and access control.
can i get something like the things u explained on prometheus abt different env, how did u guys implemented that? i know abt prom but dont have much idea abt thanos
In the context of Kubernetes, rolling updates are used to update or roll out changes to a running application or workload in a controlled manner, without causing downtime. The parameters "maxsurge" and "maxunavailable" are used to control how many new replicas can be created and how many old replicas can be unavailable during the rolling update process.
The question was mostly based on the self-hosted cluster. It can vary but the general steps include: Updating the Kubernetes control plane components. Upgrading the kubelet and kubectl on worker nodes. Verifying that the cluster components and worker nodes are running smoothly after the upgrade.
Thanks for the feedback, Ritesh. While I value every opinion here as the idea of 'Best' is subjective. Thus, in order to improve the quality of these video, I'd love to have your feedback. Please do let me know what can be improved and what was not upto the mark in this video. Also, with questions and answers, this will help the community a lot. I'd request for the same, please do contribute from your end.
Dear Ravish,I genuinely appreciate your efforts, but I must express that I don't believe the candidate possesses expertise in Kubernetes. many of his answers were irrelevant to the questions asked.
Appreciate the genuine response, Karim. Please do let us know according to you what was not great and what can be improved? This will help us a lot. Thanks you, again.
@@LogicOpsLab From my understanding, the questions appear to focus on fundamental aspects of Kubernetes. However, I believe it would be beneficial to include more real-time scenarios and practical use cases commonly encountered in live environments or day-to-day operations.
While upgrading the cluster it would have been better if he might have talked about cordoning the nodes & utilizing pdb Secondly talking about cluster security rbac, ip masquerading & azure ad + crds to limit access, restricting pods with read and write access using cluster roles
Update Control Plane: kubeadm: If you used kubeadm to set up your cluster, you can use it to upgrade the control plane. Here's a high-level overview of the process: Drain and cordon the control plane node you want to upgrade: This ensures that no new pods are scheduled on the node during the upgrade process. Upgrade kubeadm, kubelet, and kubectl on the control plane node. Run kubeadm upgrade apply to upgrade the control plane components. Uncordon the control plane node after the upgrade is complete.
![Eminem - Fuel (feat. JID) [Official Lyric Video]](http://i.ytimg.com/vi/t5H_CewqpKA/mqdefault.jpg)
This is me guys😂 never expected that this video will get posted❤.
i need your help buddy
How much exp do u have and are u selected in this company ?
Amazing knowledge. When was this interview taken, bro?
Did you get selected? And, how much experience do you have?
How can i connect u????
@rohita9689 Congratulations bro u are the best i need your help I can't able to crack the interview of devops
Amazing! Very confident and reliable answers 🙏🏻
Kudos to the knowledge of the candidate 👌🏻
Thanks for the feedback.
One of the best interviews regarding K8s.
Glad you liked it 🤝🏻
Namespace will be used for isolation of our resources like dev, prod and qa and enable efficient usage of resources like cpu memeory
Correct 💯
Hi Ravish , thanks for capturing the interview with scenario based questions . This is Rashmi here I have been following your channel and the Interview playlist is very useful. Just an improvement I would like to suggest, is it possible to segregate these videos as Kubernetes , AWS , Docker and Linux , Git(separate) folders ? that will be very helpful to locate the exact videos while watching them . Thanks
Will try to segregate them. Thanks for the feedback.
@@LogicOpsLab Thanks a lot @Ravish.
Namespaces are nothing but Projects by using it we are segregating pods as per applications. Also we can set Resource Quota on namespaces so pods will not utilise all resources of the Nodes.
believe me I dont have any experience in devops and kube8,, but I know all the answers that you asked to the candidate..
Amazing!
You are hired🎉
Very nice interview. The candidate is very knowledgeable 👏🏻
Glad you think so!
Great interview very useful
Thanks a bunch.
Service is nothing but load balancer and it distribute the traffic to pods. There three types of services
ClusterIP
NodePort
Loadbalancer
when its started initially sound quality was good to understand but in few seconds later quality was not good enough to understand.
keep voice as good to understand, anyway its helpful. will be more helpful if you are creating content by own que and Answers
Thanks a lot for the feedback, mate.
Great video ravish, can you please do one video on real time scenarios in k8s and troubleshooting part that would be highly appreciated
Will work on something like this soon
We will secure using
1) RBAC
2) private subnet
Hi Sir... I want to learn Devops..are you having any batch???
Not yet, friend. 😊
A 545 liked by me to this awesome video.
Thanks a lot for your support
Does Aks mandatorily deploys a load balancer? What about In case of private aks ...in a production env can aks work without any load balancer
Public AKS Cluster: Typically uses an Azure Load Balancer for services exposed to the internet.
Private AKS Cluster: Can use an Internal Load Balancer for services within a VNet or rely on ClusterIP if services do not need external access.
In production environments, whether you use an external load balancer, an internal load balancer, or none at all depends on your specific needs for traffic distribution, security, and access control.
I am actively applying for DevOps as 2 years experience, im not getting any calls,is it same for everyone?
Yes, don't worry. The current market is not very good. But, keep on Up skilling, hopefully the next quarter will improve. Best wishes.
can i get something like the things u explained on prometheus abt different env, how did u guys implemented that? i know abt prom but dont have much idea abt thanos
My questions more or less this
How do you monitor a Kubernetes cluster and its applications?
@@LogicOpsLab yes then he explained abt multiple envs and they're managing it thru thanos..how they're doing i wanted to know
Do we have the list of questions?
As of now, I do not have it handy. But, if you can note them down as a comment here, I'd be able to answer them and help you.
@@LogicOpsLab Answering the questions
@@LogicOpsLab Answering the questions right for the questions?
Rolling update uses maxsurge and maxunavailable
In the context of Kubernetes, rolling updates are used to update or roll out changes to a running application or workload in a controlled manner, without causing downtime. The parameters "maxsurge" and "maxunavailable" are used to control how many new replicas can be created and how many old replicas can be unavailable during the rolling update process.
Tell us on kunernetes upgrade please
The question was mostly based on the self-hosted cluster. It can vary but the general steps include:
Updating the Kubernetes control plane components.
Upgrading the kubelet and kubectl on worker nodes.
Verifying that the cluster components and worker nodes are running smoothly after the upgrade.
Bro tell me seriously is this the best interview in Kubernetes. I don't think so
Thanks for the feedback, Ritesh. While I value every opinion here as the idea of 'Best' is subjective. Thus, in order to improve the quality of these video, I'd love to have your feedback. Please do let me know what can be improved and what was not upto the mark in this video. Also, with questions and answers, this will help the community a lot. I'd request for the same, please do contribute from your end.
Please make video on Docker
Soon
Dear Ravish,I genuinely appreciate your efforts, but I must express that I don't believe the candidate possesses expertise in Kubernetes. many of his answers were irrelevant to the questions asked.
Appreciate the genuine response, Karim. Please do let us know according to you what was not great and what can be improved?
This will help us a lot. Thanks you, again.
@@LogicOpsLab From my understanding, the questions appear to focus on fundamental aspects of Kubernetes. However, I believe it would be beneficial to include more real-time scenarios and practical use cases commonly encountered in live environments or day-to-day operations.
@@karim258 Appreciate it. We will try put more real time scenarios next time. Thank you.
I too felt same. no substance in answer to the upgrade question as an example : (
While upgrading the cluster it would have been better if he might have talked about cordoning the nodes & utilizing pdb
Secondly talking about cluster security rbac, ip masquerading & azure ad + crds to limit access, restricting pods with read and write access using cluster roles
Current kubernetes version 1.27
Upgrade part is not clear
We have to cardon the control plane / nodes before doing the upgrades
Update Control Plane:
kubeadm: If you used kubeadm to set up your cluster, you can use it to upgrade the control plane. Here's a high-level overview of the process:
Drain and cordon the control plane node you want to upgrade: This ensures that no new pods are scheduled on the node during the upgrade process.
Upgrade kubeadm, kubelet, and kubectl on the control plane node.
Run kubeadm upgrade apply to upgrade the control plane components.
Uncordon the control plane node after the upgrade is complete.
Was he selected
It is an old interview, so, can't remember. But, as far as I can hear, I think he was selected.
what is wrong with the audio?
Voice modulation in order to keep the identity of the person intact.
Current release 1.27.3
Perfect! I guess it is .4 now.
Official doc - kubernetes.io/releases/
@@LogicOpsLab i given CKA exam 2 months ago that time it was 1.27.3 so, they pushed update recently.