Skip to content

1.3.186.0 August Release
Compare
Choose a tag to compare
@chrisdats chrisdats released this 22 Aug 19:59
· 33 commits to main since this release
1.3.186.0
a607752
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 August Update of AKS Edge Essentials.
⚠️ WARNING: Note that some of the features in this release are not supported in GA yet.

New Features

  • Kubernetes 1.25 support (1.24 is now deprecated)
  • Kubernetes 1.24 to 1.25 upgrade
    - Existing deployments on AKS-EE 1.2.414.0 and Kubernetes minor version 1.24 can upgrade to Kubernetes minor version 1.25 by running Set-AksEdgeUpgrade -acceptUpgrade $True See documentation for more details
    • Note: Existing deployments with Windows node or Scalable Cluster must FIRST run an additional command in order to upgrade from Kubernetes version 1.24 to 1.25. For these deployments, running Set-AksEdgeUpgrade without setting this reg key will result in failure. reg add hklm\software\microsoft\aksedge /v acceptUpgrade /t REG_SZ /d True /f

Version Numbers

  • K8s (upstream Kubernetes) distribution - 1.25.7
  • K3s distribution - 1.25.8+k3s
  • Json version schema - 1.8

Experimental or Preview Features

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

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

Fixed issues

Known issues

Update​

  • OS upgrade (Windows 10 to Windows 11) will result in AKS Edge Essentials failing to work properly​
  • "Unable to Start HCS VM" exception caught when running command "Start-AksEdgeControlPlaneUpdate -firstControlPlane True" If this error is encountered, the following commands can be used to recover the cluster
    import-module "C:\Program Files\WindowsPowerShell\Modules\1.3.186.0" -Force $nodeConfig = Get-NodeConfig -NodeType ([NodeType]::Linux) $ServiceIpRange = ParseServiceIpRange -ServiceIpRange $nodeConfig.ServiceIpRange $scriptArgs = @{ firstControlPlane = $firstControlPlane networkPlugin = $(Get-ClusterNetworkPlugin) controlPlane = $(Get-LinuxNodeHasControlPlane) controlPlaneEndpointIp = $(Get-ClusterControlPlaneEndpoint).ControlPlaneEndpointIp serviceIPRangeStart = $($ServiceIpRange.Start) serviceIPRangeEnd = $($ServiceIpRange.End) } Update-PostScriptLinuxVM @scriptArgs

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​
  • 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​
  • Multi-Node update Fails to recreate Windows nodes
Assets 2
Loading