Duration
1 day
Overview
This module covers the core infrastructure components of Kubernetes and how they're used in Azure Kubernetes Service (AKS).
Scenario
As application development continues to move towards a container-based approach, there's an increasing need to orchestrate and manage resources. Kubernetes provides reliable scheduling of fault-tolerant application workloads, making it the leading platform for container orchestration. Azure Kubernetes Service (AKS) is a managed Kubernetes offering that further simplifies container-based application deployment and management.
In this module, you learn about the core Kubernetes infrastructure components, including control plane nodes, node pools, and workload resources such as pods, deployments, and sets. You learn how to build and run modern, portable, microservices-based applications using Kubernetes to orchestrate and manage the availability of the application components. Finally, you learn how AKS provides a managed Kubernetes service that reduces the complexity of deployment and core management tasks, like upgrade coordination.
Learning Objectives
This module includes:
- Introduction to Kubernetes.
- Core Kubernetes Infrastructure Components.
- Control Plane Nodes and Node Pools.
- Workload resources.
Goals
The goal of this module is to provide an understanding of the core infrastructure components of Kubernetes and how they're used in Azure Kubernetes Service (AKS).
Outline
- Azure Kubernetes Service. The basic components for Azure Kubernetes Service are:
- Azure Kubernetes Service (AKS). AKS is a managed Kubernetes cluster hosted in the Azure cloud. Azure manages the Kubernetes API service, and you only need to manage the agent nodes.
- Virtual network. By default, AKS creates a virtual network into which agent nodes are connected. You can create the virtual network first for more advanced scenarios, which lets you control things like subnet configuration, on-premises connectivity, and IP addressing.
- Ingress. An ingress server exposes HTTP(S) routes to services inside the cluster.
- Azure Load Balancer. Once the AKS cluster is created, the cluster is ready to use the load balancer. Then, once the NGINX service is deployed, the load balancer is configured with a new public IP that will front your ingress controller. This way, the load balancer routes internet traffic to the ingress.
- External data stores. Microservices are typically stateless and write state to external data stores, such as Azure SQL Database or Azure Cosmos DB.
- Azure Active Directory. AKS uses an Azure Active Directory (Azure AD) identity to create and manage other Azure resources such as Azure load balancers. Azure AD is also recommended for user authentication in client applications.
- Azure Container Registry. Use Container Registry to store private Docker images, which are deployed to the cluster. AKS can authenticate with Container Registry using its Azure AD identity. AKS doesn't require Azure Container Registry. You can use other container registries, such as Docker Hub.
- Azure Monitor. Azure Monitor collects and stores metrics and logs, application telemetry, and platform metrics for the Azure services. Use this data to monitor the application, set up alerts, dashboards, and perform root cause analysis of failures. Azure Monitor integrates with AKS to collect metrics from controllers, nodes, and containers.
- Azure Kubernetes cluster architecture
- Azure Kubernetes Service pods
- Nodes and node pools for Azure Kubernetes Service
- Namespaces for Azure Kubernetes Service
- Access to Azure Kubernetes Service
- ClusterIP
- NodePort
- LoadBalancer
- ExternalName
- Azure virtual networks
- Kubenet networking
- Azure Container Networking Interface (CNI) networking
- Ingress controllers
- Monitoring and logging for Azure Kubernetes Service
- Azure Monitor
- AKS cluster and workload monitoring
Summary
In this module, you learned about:
- Control plane nodes, node pools, and workload resources like pods, deployments, and sets.
- Scheduling of fault-tolerant application workloads using Azure Kubernetes Service.
- Managing deployment and core management tasks, like upgrade coordination using Azure Kubernetes Service.
- Clustering of virtual or on-premises machines called nodes that share compute, network, and storage resources.
Programme scope, delivery arrangements and suitability are confirmed during enquiry.