Skip to content

0.7.22335.1024 (Public Preview)
Compare
Choose a tag to compare
@fcabrera23 fcabrera23 released this 09 Dec 18:08
· 117 commits to main since this release
0.7.22335.1024
16a15ce
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 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.
Assets 2
Loading