remember events so this is again thanks for tuning in in so today I'll put the you know demands by a lot of the colleagues we are starting a new chapter all together which is called a getting you know starting everything from scratch or kubernetes I mean I mean starting with the architecture and how it is being played in this in devops world so today I will be explaining the first of all the architecture of this entire kubernetes for construction tool and then we'll take it further from there how I can simply understand architecture you can simply come on to Google and type this kubernetes architecture then you'll understand uh and then first link that you got it is the uh the authentic kubernetes which is being created by this entire kubernetes is being created by Google so you'll get this authentic link so I'll be explaining everything from this piece only so I've created a small PPT and I'll explain with the help of this one slider what is the entire architecture of this you know orchestration tool now if you see this is my entire architecture diagram I'll just show you that the left hand side is the control plane when I say control plane this is the brain of presenter kubernetes orchestration tool and the right hand side this is the these are all worker nodes so as you see our cluster which cost which we created is a single node cluster see it is only having one node it can have multiple nodes since if you're you know creating any multi-node cluster which is having three nodes or two node and a single control plane so that is how it it's being placed so in our case it is actually mini Cube so it is having single node worker node and remaining is the your brain of your entire orchestration tool so let's get into the detail of this brain the first of all you can see this component API so this is called a cube API server this is actually the front end of this brain and it communicates with everyone when I say communicate communicates with the node to schedule ports or to schedule any application to the to the respective worker nodes and then it communicates with the the controller manager the hcd and the scheduler and the other thing so this is actually the front end API of your kubernetes so this is actually the API call Api cover now the next item which is very very important is Theory at 3D is D is the back end database of this entire kubernetes booster which stores all the data into the key value pairs this is the hcd you normally set CD collector it's a 3D component basically now there's another component called as scheduler s CH you know HED so this is actually responsible for if any new pod is created make sure that pod is being scheduled to run on any particular node notice nothing but a you know operating system so this is the responsibility of a scheduler now the controller manager now is again very very important topic we don't want to put everything onto the cube API server you know a component of all the load so we have this controller man here what it does it is a small write-up there are four components under Cube controller manager I'm talking about this component as of now is node control what is this node controller suppose if my this node is getting down so it will automatically inform to my you know brain that this is down please you know reschedule it or maybe just you know scale it so this is the functionality of this node controller which is another called a job controller under the hood job controller maintains all the job prone jobs which are being scheduled on any particular name page suppose there's a job that runs every midnight to clean up the extra space so there is a job scheduler will take care of that stuff right and then there's the endpoint controller all sentiments welcome to what is the component another component is the third piece of this it is actually a providing a you know connection or the same link between these services and the Pod so what is the service and what is the port suppose you spin up a uh pod uh by multiplication and then application is exposed to a particular port 8080 so that is that communication has been provided by Android uh slide controller now with account controller is something which creates normal default service account for any new namespace that is getting created now these are all about four components another component called as CCM water can Cloud controller manual but this component is completely appended mini queue because it is not responsible for it is not available for local you know Standalone cluster for that matter then it console for communication with those Cloud components so it is actually appended mini Cube if we talk about node components no node component is what are the components in the worker node now there are two important components inside the worker note the cubelet and the cube proxy now cubelet is an agent which is running on every every worker node and it is responsible for that make sure that whatever specifications we are giving in pod that will get set fulfilled when I say that my pod should run with three containers and all those three containers should get you know executed so container is the lowest level and on top of it we have board right so support can contain one container board can contain three container three small you know operators operating system basically the cubelet is responsible for that a cube proxy is again responsible for it is a network property that is responsible for communicating within the Pod between the namespace so suppose we have report then that kind of communication or networking will happen with the output Q proxy API and ultimately these two communicates with this API server which is the brain so you can see the you know Arrow flow so these two are communicating with this so this is these are the node components earlier we saw all the control plane components there are only two kind of things one is brainer diversity worker nodes which is working on the assignation of the uh brain and finally the container runtime now container runtime is nothing but a software that runs inside every container so suppose above we created three containers within one pod now outside every container this is the container D container D is the container runtime which is running in the latest version of uh you know kubernetes version which is actually 127 as of now so this is quickly uh telling you about the architecture I don't want to spend more time because to these other container runtimes currently it is on container d in our kubernetes latest version yes version you can see I think 127 127 is a stable version see so and it is operated on container D runtime so quickly summarizing everything we have only two two components control plane component which is called as brain and the worker component is called as node component worker nodes and it has five components and the worker has two component ultimately it is everything running on the container on time yeah so that is all about the kubernetes architecture will again Circle back on the next fashion where we did talk about more on to the power the wizard and deployment and stateful that but still this entire documentation is indicator repository which is there into the description of this video please do like comment what are what else you want from this kubernetes series will help you to answer and thanks for watching thank you bye