Skip to content

1.9.262.0

Latest
Latest
Compare
Choose a tag to compare
@SummerSmith SummerSmith released this 20 Nov 18:09
· 2 commits to main since this release
1.9.262.0
bf8fdcd
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

We are excited to release the November 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.9.262.0

  • Mariner Version: 2.0.20241029

  • K8s (upstream Kubernetes) distribution: 1.28.9, 1.29.4

  • K3s distribution: 1.28.5, 1.29.6 

  • Json version schema: 1.14

New Features

  • We have updated the Mariner and Windows versions to include CVE fixes between this release and the previous release.

Experimental or Preview Features

  • Run Windows containerized workloads.

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

  • GPU-PV is in preview

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

CVE fixes

  • All CVEs that have been patched between Mariner version 2.0.20240731 and Mariner version 2.0.20241029.

Known issues

Update

  • When updating from 1.5.203 to 1.6.384.0 on both Linux and Windows, customers may see one of the following non-fatal errors:

    • "Get-Content: Cannot find path 'C:\Windows\System32\akswindows-manifest.json' because it does not exist."

    • "Get-Content: Cannot find path 'C:\Program Files\AksEdge\akswindows-manifest.json' because it does not exist."

This is a non-fatal error and can be ignored.

  • 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

  • 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 .

  • No storage provisioner is available for the Windows node .

  • NFS subdir external provisioner pod fails on Windows nodes.

Assets 2
Loading