Skip to content

1.6.384.0 Release
Compare
Choose a tag to compare
@SummerSmith SummerSmith released this 08 Feb 17:03
· 16 commits to main since this release
1.6.384.0
8d616a4
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 February 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.6.384.0
  • Mariner Version: 2.0.20240123
  • K8s (upstream Kubernetes) distribution - 1.26.6, 1.27.6
  • K3s distribution – 1.26.10, 1.27.6
  • Json version schema - 1.11

New Features

  • Kubernetes versions supported: On K8S - 1.26.6 and 1. 27.6, On K3S 1.26.10 and 1.27.6
  • Update from K3S 1.26.6 to 1.26.10, and on K8S from 1.26.6 (Nov release) to 1.26.6 (Jan release).
  • Upgrade from K3s 1.25.11(Nov release) to 1.26.10(Jan release) and on K8s from 1.25.11(Nov release) to 1.26.6(Jan release)
  • We have added json config validation for location field and improved error handling to create a smoother deployment process.

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.

Key bug fixes

  • Updated journald config to ensure the journal log does not grow beyond the 250-300MB range in order to preserve log space
  • Improved install and update experience by optimizing to reduce the free disk space requirement

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