To
run your applications and supporting services, you need a
Kubernetes node.
An AKS cluster has one or more nodes, which is an Azure virtual
machine (VM) that runs the Kubernetes node components and container
runtime:
- The
kubeletis the Kubernetes agent that processes the orchestration requests from the control plane and scheduling of running the requested containers.
- Virtual networking is handled by the kube-proxy on each node. The proxy routes network traffic and manages IP addressing for services and pods.
- The container runtime is the component that allows containerized applications to run and interact with additional resources such as the virtual network and storage. In AKS, Moby is used as the container runtime.
The
Azure VM size for your nodes defines how many CPUs, how much memory,
and the size and type of storage available (such as high-performance
SSD or regular HDD). If you anticipate a need for applications that
require large amounts of CPU and memory or high-performance storage,
plan the node size accordingly. You can also scale out the number of
nodes in your AKS cluster to meet demand.
In
AKS, the VM image for the nodes in your cluster is currently based on
Ubuntu Linux or Windows Server 2019. When you create an AKS cluster
or scale out the number of nodes, the Azure platform creates the
requested number of VMs and configures them. There's no manual
configuration for you to perform. Agent nodes are billed as standard
virtual machines, so any discounts you have on the VM size you're
using (including Azure
reservations)
are automatically applied.
If
you need to use a different host OS, container runtime, or include
custom packages, you can deploy your own Kubernetes cluster
using aks-engine.
The upstream
aks-engine releases
features and provides configuration options before they are
officially supported in AKS clusters. For example, if you wish to use
a container runtime other than Moby, you can use aks-engine to
configure and deploy a Kubernetes cluster that meets your current
needs
0 Response to "Nodes and node pools"
Post a Comment