Skip to content

1.5.203 release
Compare
Choose a tag to compare
@rcheeran rcheeran released this 03 Nov 03:20
· 24 commits to main since this release
1.5.203.0
b6cd42c
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 October Update of AKS Edge Essentials.
⚠️ WARNING: Note that some of the features in this release are not supported in GA yet.

Version Numbers

  • AKS-EE Version: 1.5.203.0
  • Mariner Version: 2.0.20231004
  • K8s (upstream Kubernetes) distribution - 1.26.6, 1.25.11
  • K3s distribution – 1.26.6, 1.25.11
  • Json version schema - 1.9

New Features

  • Kubernetes versions supported: On K8S - 1.25.11 and 1. 26.6, On K3S 1.25.11 and 1.26.6
  • Update from K3S 1.25.8 to 1.25.11, and on K8S from 1.25.7 to 1.25.11 and from 1.26.3 to 1.26.6

Experimental or Preview Features

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

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

Key bug fixes

  • Fixed bugs related to network switch impacting deployment experiences.
  • Fixed issues with resource group requirements during Arc connectivity.
  • Added checks in place, that prevents the windows node update if the machine does not have enough disk space to extract the new windows vhdx.
  • Added checks in place to identify scenarios where there are multiple Azure resource types with the same name.
  • WssdAgent updated to add subnet information if the switch does not have subnet information.
  • Improve deployment experience, by cleaning up artifacts from a previous deployment before starting the new deployment
  • Fixed the issue where single machine clusters were ignoring the DNS Server configuration parameter.

Known issues

Update

  • Updates from K8S 1.26.3 to 1.26.6 fails when disk pressure is high. As a workaround, extract the tarball /opt/container-images/container-images-tar-file.tar.gz and use ctr to reimport the images that are missing, using the command ctr -n=k8s.io images import {extracted tar files location}

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)​. Recommend setting the policy to 'ByPass'.
  • Uninstalling and reinstalling k8s/k3s causes a “deployment already exists” error or the 'Virtual machine creation failed' error, when creating a new deployment, so recommend restarting your machine before deployment​.
  • Event logging fails when uninstalling and reinstalling an MSI without a reboot in between​. Particularly true when switching between using K3S and K8S.
  • 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.​
Assets 2
Loading