1.0.358.0 (Public Preview) Update MSI Release Only

This release is the third AKS-EE public preview release. Please note that this release is Update MSI release only, meaning customers must update from1.0.266.0 to get to 1.0.358.0. There is no mechanism to install 1.0.358.0 outright. Please also note that the changes in this release are relatively small, and largely intended to give customers some experience with the update process.

Key features

• Update available through Microsoft Update and Microsoft Update Catalog. For more information on updates please visit AKS-EE Updates.
• Windows nodes continue to be an experimental feature
• Updated warnings and log outputs
• K8s (upstream Kubernetes) distribution - 1.24.3
• K3s distribution - 1.24.3

Fixed issues

• Fixed: Default proxy settings in the aksedge-dc.json template file is preventing computed no_proxy configuration from working

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​

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​
• GitOps steps provided in the documentation are not compatible with Windows nodes

1.0.266.0 (Public Preview)

This version is a public preview refresh and a release candidate for our final GA bits.

Key features

• Improved stability of both Linux and Windows nodes
• Windows nodes continue to be an experimental feature
• Refactored AKSEdge Powershell module with newly exposed cmdlets and new JSON configuration files. The new JSON parameters can be found here.
• Support for external NFS storage provisioned
• K8s (upstream Kubernetes) distribution - 1.24.3
• K3s distribution - 1.24.3

Fixed issues

• #15 - Hyper-V Internal Switch is lost after a restart on Win11 Pro 22H2 22623.746
• #34 - K3s New-AksEdgeDeployment fails on current PowerShell versions (7.3.x)
• #40 - Allow container images to be loaded from archives
• #43 - Calico strictAffinity is false when installing Windows Node
• Memory leak on K3s cluster impacts long duration run of K3s Linux nodes

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​

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​
• GitOps steps provided in the documentation are not compatible with Windows nodes

0.7.22335.1024-final

Final code base to use with first Public Preview bits.

0.7.22335.1024 (Public Preview)

We are excited to announce the public preview of AKS Edge Essentials (introduced as Project Haven during Microsoft Build 2022). AKS Edge Essentials is a lightweight, Kubernetes platform that enables rapid application innovation and modernization at scale at the edge. In addition to this, 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.

Key features

• K8s (upstream Kubernetes) distribution - 1.22.6
• K3s distribution - 1.23.6
• Run Linux containerized workloads
• Run Windows containerized workloads
• Create a single-node Linux (control plane and worker) cluster on a single machine
• Create a dual-node Linux node (control plane and worker) + Windows node (worker) cluster on a single machine
• Create a cluster with multiple machines (experimental)
• 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

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

Known Issues

• AKS Edge Essentials Public Preview does not yet have over-the-air updates: a reinstallation will be required to update to the next version of the public preview.
• Public Preview reinstallation: When you uninstall a public preview MSI and reinstall a public preview MSI, please ensure to reboot the system in between. Otherwise, event logging will not work.
• SSH.exe may hang on the Windows host. If this occurs, please press Ctrl + C to break the deployment and rerun the deployment command.
• If your machine goes to sleep while a cluster is running, it may disappear and not return reliably when machine is awake. A cold restart should make the cluster return. If you would like to prevent this issue from occurring, please turn off the power management so that your machine does not go to sleep while your cluster is running.
• Test-AksEdgeNetworkParameters returns True with same config file in a different machine after you have installed it on one machine (they have the same IP addresses). The error may show up too late when a New-AksEdgeDeployment is created on the second machine with the same config file on the same network. Please make sure to change the network parameters for the deployments on each machine.
• When the AksEdgeWindows-V1.exe fails (i.e. due to lack of memory, etc.), it creates an incomplete VHDX file that causes errors later on. If this occurs, please remove the incomplete AksEdgeWindows-v1.vhdx file before proceeding.
• In a Full deployment, if you provide an External Switch name and not create a switch on Hyper-V with that name, then the New-AksEdgeDeployment will not attempt to create a switch with that name and the deployment will fail.
• Memory leak on K3s cluster impacts long duration run of K3s Linux nodes

Scaling issues

• Scaling LinuxAndWindows nodes as control planes may fail to start the Linux VM on K3s. If this occurs, please use K8s as a workaround for now.
• When deploying a LinuxAndWindows cluster, it may get stuck on testing the connection after Windows VM creation. To avoid this, please validate that the IP addresses are free before deploying the cluster.