Author : HASSAN MD TAREQ | Updated : 2021/04/13

AKS as PaaS

Deployment model of AKS

Service Object

Service object provides a set of capabilities that match the microservices requirements for service discoverability:

Azure Container Registry

Load Balancer

As PaaS service, AKS provides load balancer

Ingress Controller

Cluster Autoscaler

Managed Identities

Node Pool

a node pool is a grouping of nodes in the cluster with the same configurations

During provisioning in Azure portal, we can add additional node pool

[Courtesy of following: https://pixelrobots.co.uk/2020/06/azure-kubernetes-service-aks-system-and-user-node-pools/] When you create a new AKS cluster using the portal or Azure cli then the node pool that is automatically created is the system node pool. You don’t even have to specify it in the commands. It just happens. When you add additional node pools using the az aks nodepool add command the newly created node pool will be a user node pool.

By default K8s nodes are linux VMs

Bridge to Kubernetes

How bridge works?

Notes:

More:

Deployment Center

On left pane (under setting section) there will be “Deployment Center” option. You can setup Azure DevOps pipelines (CI/CD) and integrate Azure Container Repository from Deployment Center.

HTTP application routing

HTTP application routing add-on makes it easy to access AKS cluster deployed applications publicly

Node Resource Group

Helm

Helm Chart

https://azure.microsoft.com/en-us/topic/what-is-kubernetes/ https://docs.microsoft.com/en-us/azure/aks/concepts-clusters-workloads

https://azure.microsoft.com/mediahandler/files/resourcefiles/kubernetes-learning-path/Kubernetes%20Learning%20Path%20version%201.0.pdf