Skip to content

1.11.247.0

Latest
Latest

Choose a tag to compare

View all tags
@SummerSmith SummerSmith released this 25 Sep 01:16
· 3 commits to main since this release
1.11.247.0
1e2e8a9
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

We are excited to release the September Update of AKS Edge Essentials.

⚠️ WARNING: Note that some of the features in this release are not supported in GA yet.

Version Numbers

  • AKS Edge Essentials Version: 1.11.247.0

  • Azure Linux (previously Mariner) Version: 3.0.20250822

  • K8s (upstream Kubernetes) distribution: 1.30.5 (only available as upgrade from 1.10.868.0), 1.31.5

  • K3s distribution: 1.30.6 (only available as upgrade from 1.10.868.0), 1.31.6

  • Json version schema: 1.16

Available Upgrade/Update Paths

Current version Upgrade path
1.10.868.0 k8s/k3s 1.29 1.11.247.0 k8s/k3s 1.30
1.10.868.0 k8s/k3s 1.30 1.11.247.0 k8s/k3s 1.30
1.10.868.0 k8s/k3s 1.30 1.11.247.0 k8s/k3s 1.31

Please note that upgrading from one Kubernetes distribution to another within the same release version is not supported.

New Features

  • AKS Edge Essentials version 1.11.247.0 uses Azure Linux 3.0, an upgrade from Azure Linux 2.0, used in previous releases.

  • AKS Edge Essentials now connects to Azure Arc during deployment to decrease the number of steps required for customers. Arc parameters are required in the aks-edge configuration file during deployment. AKS Edge Essentials deployment will be blocked if Arc parameters are missing or invalid. Please note, this does not impact offline deployments or volume licensing customers.

  • October 2025 Update: KMS provider is now generally available on AKS Edge Essentials starting with AKS Edge Essentials version 1.11.247.0.

Experimental or Preview Features

  • Key manager for Kubernetes

  • 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

  • The previous AKS Edge Essential version had a bug that made the deployment incompatible with some non-English Windows Server OS. This has been fixed in version 1.11.247.0

Known issues

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