Skip to content

1.0.266.0 (Public Preview)
Compare
Choose a tag to compare
@fcabrera23 fcabrera23 released this 03 Feb 21:51
· 105 commits to main since this release
1.0.266.0
5091db3
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.

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