Skip to content

1.1.80.0 March Update
Compare
Choose a tag to compare
@chrisdats chrisdats released this 23 Mar 16:27
· 84 commits to main since this release
1.1.80.0
bb82536
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

We are excited to release the March Update of AKS Edge Essentials, a lightweight Kubernetes platform that enables rapid application innovation and modernization at scale at the edge. This release adds new features including TPM Passthrough, dual-NIC support, and non-root access for logs, improved Arc connectivity, and updated Kubernetes version.

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

Key features

  • Existing features from previous (GA) release
  • K8s (upstream Kubernetes) distribution - 1.24.6
  • K3s distribution - 1.24.6
  • TPM Passthrough
  • Dual-NIC support
  • Improved Arc Connectivity (Az.ConnectedKubernetes v0.9.0)

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

  • No longer requires root user/group to access container log files
  • Miscellaneous bug fixes to improve stability

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
Assets 2
Loading