Skip to content

1.0.406.0 Generally Available (GA)

Compare
Choose a tag to compare
@fcabrera23 fcabrera23 released this 22 Feb 00:06
· 96 commits to main since this release
5759fba

We are excited to announce the GA of AKS Edge Essentials, a lightweight Kubernetes platform that enables rapid application innovation and modernization at scale at the edge. In addition, you can connect your AKS Edge Essentials cluster to Azure via Arc-enabled Kubernetes, enabling robust deployment, management, and governance capabilities for your IoT devices using the Azure portal.

⚠️ WARNING: Note that some of the features from public preview are not supported in GA yet.

Key features

  • K8s (upstream Kubernetes) distribution - 1.24.3
  • K3s distribution - 1.24.3
  • Run Linux containerized workloads
  • Create a single-node Linux (control plane and worker) cluster on a single machine:
    - deploymenttype : singlemachinecluster for Internal virtual swtich
    - deploymenttype : scalableCluster for External virtual switch
  • Remotely deploy your workloads using Azure Arc GitOps
  • Remotely deploy Azure services using Azure Arc
  • Use calico (K8s) or flannel (K3s) network plugins
  • Installation without internet connectivity and proxy enabled environments
  • Updates available through Microsoft Update and Microsoft Update Catalog

Experimental or Pre-release Features

  • Run Windows containerized workloads
  • Create a dual-node Linux node (control plane and worker) + Windows node (worker) cluster on a single machine
  • Create a cluster with multiple machines

For more information feature set and benefits, see AKS Edge Essentials Overview.

Fixed issues

Known issues

Runtime​

  • When disk space begins to run out, precached images may be removed by kubelet/containerd, causing Kubernetes to fail​

Update​

  • OS upgrade (Windows 10 to Windows 11) will result in AKS Edge Essentials failing to work properly​

Deployment​

  • Deploying a K8s Linux node on a 4GB RAM host machine fails
  • New deployment fails when the execution policy is set to AllSigned (Set-ExecutionPolicy –ExecutionPolicy AllSigned)​
  • Uninstalling and reinstalling k8s/k3s causes a “deployment already exists” error when creating a new deployment, so a restart is necessary​
  • Event logging fails when uninstalling and reinstalling an MSI without a reboot in between​
  • When a deployment fails due to lack of memory/disk space, it creates an incomplete VHDX file that causes errors in later deployments​
  • Deployment with External virtual switch fails when using Windows RS5

Windows nodes​

  • On a K3s Windows node, load balancer klipper-lb pulls images from the internet when connected​
  • Adding a Windows node takes around ~10 minutes to complete​
  • K3s Windows node with Calico as the CNI is not yet supported​
  • No storage provisioner is available for the Windows node​
  • NFS subdir external provisioner pod fails on Windows nodes​
  • Multi-Node update Fails to recreate Windows nodes