Kick start Kubernetes Managed Service(AKS) on Azure Series(Part-2)
In my previous post here we went through how to start deploying Azure AKS Cluster. Before we start deploying applications on AKS, i want to drill down little more into Logical components in Kubernetes(k8s) and how they are mapped to physical components in managed kubernetes services providers like Azure AKS.
Kubernetes is a cluster technology. In the container world there are four important entities on which applications are deployed and managed.
- Cluster – Group of machines that behave like ONE
- Node – Each machine in the cluster is called a NODE.
- Pods – POD is the smallest unit you will eventually deploy to the cluster. As single Pod can have multiple containers
- Container – Technology for packaging an application along with its runtime dependencies.
Now we know how applications are run on k8s clusters. Now we dig into logical components which help to run the applications on k8s.
This leaves us with question around how are these logical entities technically helping the kubernetes cluster to host the applications??
Well we then need to drill into cluster architecture and supporting components for k8s clusters. For the scope of this blog i would consider the Azure AKS cluster architecture.
Hold on!! There are a lot of concepts that i have not heard about here. Lets break down all these concepts and try to understand how this whole thing is stiched together.
Any managed kubernetes service provider will have two main components in the k8s cluster architecture.
- Master Node
- Worker Node
This leaves us with a high-level understanding of how the logical entities are mapped to the to physical components in managed k8s clusters.