Skip to content

1.2.414.0 June Release
Compare
Choose a tag to compare
@rcheeran rcheeran released this 16 Jun 01:28
· 37 commits to main since this release
1.2.414.0
bb0e4e7
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 June Update of AKS Edge Essentials.
⚠️ WARNING: Note that some of the features in this release are not supported in GA yet.

Key Updates

  • New version Kubernetes support - K8s (upstream Kubernetes) distribution - 1.25.4 and on K3s distribution - 1.25.8. You cannot update from 1.24.x to 1.25.x using the Microsoft Updates channel, you would have to start afresh.
  • Updates on existing version - K8S distribution - 1.24.9, K3S distribution - 1.24.12. You can update your existing 1.24.x deployments to the latest versions on 1.24.-
  • On the Windows node, replaced the Windows client image with the ServerCore image. This feature is still in preview.

Experimental or Preview Features

  • Run Windows containerized workloads
  • Create multi-node deployments either on a single machine or across multiple machines.
  • Create a cluster with multiple machines

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

Fixed issues

  • Failure to start WSSD Agent Service when creating a full deployment with auto created external switch - Fixed by waiting for the host adapter to come online, before creating the external switch
  • Fixed the issue when you cannot deploy SingleMachineCluster, ARP check does not find available IPs addresses that can be used.
  • Fix to ensure that proxy settings works on Windows VM as well
  • Fixed the failure of Windows Vhdx extraction on PS 5.0 and 7.0
  • Fixed the issue where DNS would not resolve in the Windows node](#100).

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

Linux nodes

  • When you use the Remove-AksEdgeNode to remove a node, it might still show up in the kubectl get nodes as the cluster tries to reconcile the state of the present nodes. Please note that the command Remove-AksEdgeNode is a asynchronous call and will return before the cluster state is updated to reflect the new state.

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