Skip to content

Releases: Azure/aksArc

AKS on Azure Stack HCI and Windows Server 2024-06-11 update

11 Jun 23:28
4344282
Compare
Choose a tag to compare
Component 2024-02-08 2024-06-11
AKS hybrid 1.0.22.10209 1.0.23.10605
Kubernetes Versions 1.25.6, 1.25.11, 1.26.3, 1.26.6, 1.27.1, 1.27.3 1.26.10, 1.26.12, 1.27.7, 1.27.9, 1.28.3, 1.28.5

Release Notes

Version Numbers

  • KVA version: 1.28.5
  • PowerShell: 1.2.4
  • Containerd: 1.6.26
  • WAC: 2306 GA version
  • AKS Extension in WAC: 4.11.0

What's New

Features

  • Improvements in fail-back functionality allows AKS to efficiently use the recovered servers after a fail-over event has been resolved and the HCI cluster has been restored.

Software updates

  • We have updated several components and dependencies to the latest versions to fix the following CVEs:
    • CVE-2023-5528 Kubernetes Improper Input Validation vulnerability
    • CVE-2023-3955 Insufficient input sanitization on Windows nodes leads to privilege escalation
    • CVE-2023-3676 Insufficient input sanitization on Windows nodes leads to privilege
    • CVE-2023-45288 - Golang.org/x/net is bumped to v0.23.0 to address this
    • CVE-2024-24786 - Updated google.golang.org/protobuf to v1.33.0 to resolve this

Bug Fixes

  - A bug that would allow VHD to be deleted while it was still attached to a VM, has been fixed.
  - Several MOC bugs were fixed and enhancements made in the VHD attach/detach/cleanup processes.

Some important Bugs fixes and Regressions fixed in k8s 1.28 called out below

(please check the full list on Kubernetes release notes -1.28 changelog.md)

- Fix pod restart after node reboot when NewVolumeManagerReconstruction feature gate is enabled and SELinuxMountReadWriteOncePod disabled 
- Fix a race condition in kube-proxy when using LocalModeNodeCIDR to avoid dropping Services traffic if the object node is recreated when kube-proxy is starting 
- Fixed a race condition between Run() and SetTransform() and SetWatchErrorHandler() in shared informers. 
- Fixed a regression in default configurations, which enabled PodDisruptionConditions by default, that prevented the control plane's pod garbage collector from deleting pods that contained duplicated field keys (env. variables with repeated keys or container ports). 
- Fixed the issue where pod with ordinal number lower than the rolling partitioning number was being deleted it was coming up with updated image.
- Fixes calculating the requeue time in the cronjob controller, which results in properly handling failed/stuck jobs 
- Service Controller: update load balancer hosts after node's ProviderID is updated 
- Fix a bug in cronjob controller where already created jobs may be missing from the status.
- Fixed a bug where containers would not start on cgroupv2 systems where swap is disabled. 
- Fixed a regression in kube-proxy where it might refuse to start if given single-stack IPv6 configuration options on a node that has both IPv4 and IPv6 IPs. 
- Fixed an issue to not drain all the pods in a namespace when an empty-selector i.e. "{}" is specified in a Pod Disruption Budget (PDB) 
- Fixed attaching volumes after detach errors. Now volumes that failed to detach are not treated as attached, Kubernetes will make sure they are fully attached before they can be used by pods. 
- Fixed bug to surface events for the following metrics: apiserver_encryption_config_controller_automatic_reload_failures_total, apiserver_encryption_config_controller_automatic_reload_last_timestamp_seconds, apiserver_encryption_config_controller_automatic_reload_success_total
- Fixes a bug where Services using finalizers may hold onto ClusterIP and/or NodePort allocated resources for longer than expected if the finalizer is removed using the status subresource 
- Revised the logic for DaemonSet rolling update to exclude nodes if scheduling constraints are not met. This eliminates the problem of rolling updates to a DaemonSet getting stuck around tolerations
- Sometimes, the scheduler incorrectly placed a pod in the "unschedulable" queue instead of the "backoff" queue. This happened when some plugin previously declared the pod as "unschedulable" and then in a later attempt encounters some other error. Scheduling of that pod then got delayed by up to five minutes, after which periodic flushing moved the pod back into the "active" queue. 

AKS on Azure Stack HCI and Windows Server 2024-02-14 update

15 Feb 01:18
4344282
Compare
Choose a tag to compare

Announcements

  • For those customers using Windows Server 2019, be aware that it has reached end of mainstream support, we recommend customers to upgrade to latest Windows Server version if possible.
Component 2023-10-30 2024-02-08
AKS hybrid 1.0.21.11030 1.0.22.10209
Kubernetes Versions 1.24.10, 1.24.11, 1.25.6, 1.25.11, 1.26.3, 1.26.6 1.25.6, 1.25.11, 1.26.3, 1.26.6, 1.27.1, 1.27.3

Release Notes

Version Numbers

  • AKS hybrid version: 1.0.22.10209
  • Kubernetes versions: 1.25.6, 1.25.11, 1.26.3, 1.26.6, 1.27.1, 1.27.3
  • KVA version: 1.27.3
  • PowerShell: 1.1.104
  • WAC: 2306 GA version
  • AKS Extension in WAC: 4.11.0
  • Containerd: 1.6.26

What's New

Features

  • Update to Calico CNI 3.26.4

Bug Fixes

  • In some instances, KMS pod was not able to communicate to cloudagent. It was failing with the error “rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: i/o timeout””.
  • Expired tokens were observed in customer deployments even when the auto rotate feature was enabled.
  • Issues with HAproxy Loadbalancer failover cluster and failback. In some situations, we observed attempts to bind IPs before VIPs were available.
  • Problems scaling a cluster running on unsupported versions of Kubernetes caused by missing configmaps or wrong location used in MOC.

Software updates

AKS on Azure Stack HCI and Windows Server 2023-10-30 update

31 Oct 18:02
f31305b
Compare
Choose a tag to compare

Announcements

  • With this release, we will retire older AKS-HCI versions from July 2022, August 2022, September 2022, and October 2022. Please update your clusters to remain in support.
Component 2023-08-22 2023-10-30
AKS hybrid 1.0.20.10819 1.0.21.11030
Kubernetes Versions 1.24.10, 1.24.11, 1.25.6, 1.25.7, 1.26.0, 1.26.3 1.24.10, 1.24.11, 1.25.6, 1.25.11, 1.26.3, 1.26.6

Release Notes

Version Numbers

  • AKS hybrid version: 1.0.21.11030
  • Kubernetes versions: 1.24.10, 1.24.11, 1.25.6, 1.25.11, 1.26.3, 1.26.6
  • KVA version: 1.26.6
  • PowerShell: 1.1.95
  • WAC: 2306 GA version
  • AKS Extension in WAC: 2.170.0
  • Containerd: 1.6.22

What's New

Features

  • Updated to CAPI 1.4.2

Bug Fixes

  • Azure Arc onboarding prechecks were improved to handle transitory restricted network bandwidth.

Software updates

  • We have updated several components and dependencies to the latest versions to fix the following CVEs:

AKS on Azure Stack HCI and Windows Server 2023-08-22 update

24 Aug 23:41
2be441d
Compare
Choose a tag to compare

Announcements

  • This release adds support for Kubernetes 1.26.*
  • Deprecation alert: Support for the Flannel CNI will be removed on or after December 1st 2023.
Component 2023-07-10 2023-08-22
AKS hybrid 1.0.19.10705 1.0.20.10819
Kubernetes Versions 1.23.12, 1.23.15, 1.24.9, 1.24.11, 1.25.5, 1.25.7 1.24.10, 1.24.11, 1.25.6, 1.25.7, 1.26.0, 1.26.3

Release Notes

Version Numbers

  • AKS hybrid version: 1.0.20.10819
  • Kubernetes versions: 1.24.10, 1.24.11, 1.25.6, 1.25.7, 1.26.0, 1.26.3
  • KVA version: 1.26.3
  • PowerShell: 1.1.83
  • WAC: 2306 GA version
  • AKS Extension in WAC: 2.163.0
  • Containerd: 1.6.12

What's New

  • AKS hybrid node autoscaler moves to a more secure Kubernetes Namespace: Based on customer feedback, we have made changes in which Kubernetes namespace to deploy the AKS hybrid node autoscaler in, instead of using the default namespace it now resides in the kube-system namespace of the management cluster. This enhances the security posture of the node autoscaler, as it can be isolated from other resources and pods in the default namespace, and it also enables customers to apply custom policies and RBAC rules to the default namespace. During upgrade to the latest release, if the node autoscaler is enabled it will be relocated and re-configured from the default namespace to the kube-system namespace, during the move and the upgrade autoscaling will be paused and continues after the upgrade is completed.

Deprecated Features for AKS on Azure Stack HCI and Windows Server:

Deprecating Flannel CNI option for AKS hybrid networking: As part of our commitment to continuous innovation and providing the best possible service for our customers, we are deprecating the Flannel CNI option for AKS hybrid networking. Flannel was the original CNI when AKS hybrid released, but it has limitations in functionality, scalability, security, and observability. We have been using Calico as the default CNI option for AKS hybrid networking for 18 months, and it offers superior performance and features for hybrid scenarios. Customers who are still using Flannel should migrate to Calico as soon as possible by redeploying the target cluster with a new network configuration, as Flannel will be removed by December 1st 2023. We are also planning on adding additional CNI options in AKS hybrid over the next 12 months, to give customers more flexibility and choice for their hybrid deployments.

NOTE: This does not affect AKS Edge Essentials with K3s.

WAC updates

Bug Fixes

  • We fixed a bug where the volume was not detached after the pod and PVC objects were deleted.

Software updates

  • We have updated several components and dependencies to the latest versions to fix the following CVEs:

AKS on Azure Stack HCI and Windows Server 2023-07-10 update

11 Jul 00:26
2be441d
Compare
Choose a tag to compare

Announcements

Component 2023-05-09 2023-07-10
AKS hybrid 1.0.18.10425 1.0.19.10705
Kubernetes Versions 1.23.12, 1.23.15, 1.24.9, 1.24.11, 1.25.5, 1.25.7 1.23.12, 1.23.15, 1.24.9, 1.24.11, 1.25.5, 1.25.7

Release Notes

Version Numbers

  • AKS hybrid version: 1.0.19.10705
  • Kubernetes versions: 1.23.12, 1.23.15, 1.24.9, 1.24.11, 1.25.5, 1.25.7
  • KVA version: 1.25.7
  • PowerShell: 1.1.81
  • WAC: 2306 GA version
  • AKS Extension in WAC: 2.162.0
  • Containerd: 1.6.12

What's New

WAC updates

Bug Fixes

  • We fixed a bug where the volume was not detached after the pod and PVC objects were deleted.
  • To see other bug fixes, please check out our release blog.

Software updates

  • We have updated several components and dependencies to the latest versions to fix the following CVEs:

AKS on Azure Stack HCI and Windows Server 2023-05-09 update

10 May 01:11
2be441d
Compare
Choose a tag to compare

Announcements

  • Kubernetes 1.25
    With this release we are bringing in support for K8s 1.25. This version of K8s has 40 enhancements and has improved windows support by addition of Performance Dashboard, Unit Tests and Conformance Test.
    Some notable enhancements and changes are:

    • Kube-proxy images are now based on distroless images. This change will reduce image size by almost 50% and decrease the number of installed packages and files to only those strictly required for kube-proxy.
    • 1.25 also has newly added KMS v2alpha1 API to add performance, rotation and observability improvements.
    • endPort in Network Policy, Local Ephemeral Storage Capacity Isolation, core CSI Migration and CSI Ephemeral Volume have been promoted to Stable.
    • PodSecurityPolicy is removed and Pod Security Admission also graduates to stable.

    Deprecations:

    • PodSecurityPolicy is removed.
    • GlusterFS plugin is deprecated from available in-tree drivers.
  • Extended support for minor versions: We have added enhancements that allow us to provide extended support for minor versions beyond our previous capability. In line with AKS in Azure, we will be offering support for Kubernetes minor versions for a duration of one year, effective from v1.23.x.

Component 2023-03-15 2023-05-09
AKS hybrid 1.0.17.10310 1.0.18.10425
Kubernetes Versions 1.23.12, 1.23.15, 1.24.6, 1.24.9 1.23.12, 1.23.15, 1.24.9, 1.24.11, 1.25.5, 1.25.7

Release Notes

Version Numbers

  • AKS hybrid version: 1.0.18.10425
  • Kubernetes versions: 1.23.12, 1.23.15, 1.24.9, 1.24.11, 1.25.5, 1.25.7
  • KVA version: 1.24.11
  • PowerShell: 1.1.74
  • WAC: 2211 GA version
  • AKS Extension in WAC: 2.156.0
  • Containerd: 1.6.12

What's New

Features

  • Added the ability to update proxy certs as a day 2 operation

  • Updated the install validator to add URLs that have been added since the last release

  • Limit commands available via ssh into Linux VM

    • Part 2 of the feature (Restrict SSH Access to VMs to certain IP addresses) from the last release
  • Added prechecks for KVA

  • Update now uses specific image name and retain old images

  • Updated to CAPI 1.2.10

  • Added new pre-install validations that include:

    • VMs hosting AKS components have internet connectivity
    • Verify DNS servers
    • Connectivity between the VM that hosts AKS hybrid (management cluster) and the cloud agent
  • Improvements in the management cluster update experience:

    • We have lifted a restriction that limited users from updating AKS hybrid management clusters when you have a target cluster that's running on a version that has been deprecated in the latest release. With the new change, update will proceed as long as the workload cluster's version is still a supported minor version.
    • We have incorporated an enhancement to expedite stepping between releases during updates. Now updates will transition much faster to the latest release, saving time spent on updates.
    • We’ve updated the AKS hybrid support policy to reflect these new changes.

Windows Containers

  • Windows Server 2022 container host support has moved out of preview and is now generally available. Using Windows Server 2022 as the container host enables:
    • Smaller base container images
    • Non domain joined gMSA for container applications

SDN + AKS hybrid Integration

  • Optimized SDN load balancer to be the same as default load balancer

Bug Fixes

  • We fixed a bug with our autoscaler feature. Previously, you may have experienced a scenario where the AKS HCI node pool autoscaling profiles skip-nodes-with-local-storage setting didn’t modify, meaning the setting is always "true" and won't change to "false.". This release has a fix for this issue, and you can now configure all the capabilities of our autoscaler profile feature.
    NOTE: for existing autoscaler profiles you will have to go in and edit the profile again to toggle the setting that did not get changed.

Software updates

  • We have updated several components and dependencies to the latest versions to fix the following CVEs:

Release 2023-03-15

15 Mar 21:32
686562c
Compare
Choose a tag to compare

Announcements

  • GPU-enabled node pools are now Generally Available! For more information, see our public docs.
  • Windows Server 2022 worker nodes are now Generally Available!
  • SDN + AKS Integration: Added upgrade support. If leveraging SDN + AKS, you can now upgrade your AKS clusters seamlessly.
  • Kubernetes 1.22.11 and 1.22.15 are deprecated with this release. Please upgrade to 1.23 or above to remain compliant and within support policies.
  • We are pushing out the release of Kubernetes 1.25.x to the next release due to a late breaking bug.
Component 2023-01-30 2023-03-15
AKS hybrid 1.0.16.10113 1.0.17.10310
Kubernetes Versions 1.22.11, 1.22.15, 1.23.8, 1.23.12, 1.24.3, 1.24.6 1.23.12, 1.23.15, 1.24.6, 1.24.9

Release Notes

Version Numbers

  • AKS hybrid version: 1.0.17.10310
  • Kubernetes versions: 1.23.12, 1.23.15, 1.24.6, 1.24.9
  • KVA version: 1.24.9
  • PowerShell: 1.1.67
  • WAC: 2211 GA version
  • AKS Extension in WAC: 2.145.0 (msft.sme.aks.2.145.0.nupkg)
  • Containerd: 1.6.12

What's New

Breaking Changes

  • To better align with AKS in the cloud, we are changing the Kubernetes version for a target cluster to default to the latest available version for a given release, instead of the oldest available version.
    • NOTE: This could break automation that relies on the now-deprecated behavior. To fix that, always specify the version you want to deploy in a target cluster. See the available versions using Get-AksHciKubernetesVersions for your installed release.
  • We are also changing how AKS hybrid assigns an IP address and FQDN to the cloudagent service in a failover cluster deployment. Previously, the system created a generic cluster service with a separate IP address and a random FQDN – and both had to be registered in DNS and Active Directory for the cloudagent to function. In this release, AKS hybrid picks the existing IP address and FQDN created and registered for the failover cluster, thus removing the registration requirements for DNS and Active Directory.
    • NOTE: This change could break automation if it does not specify a cloudServiceCIDR or cloudServiceIP parameter in Set-AksHciConfig.

Features

  • Automatic rotation of identity tokens
  • Additional pre-installation validation tests in Install-AksHci:
    • New endpoint tests, from the list of required URLs here
    • Ensure we can reach cloud agent (MOC) from the management VM
    • Ensure that we return right away if those tests fail
  • Restrict SSH Access to VMs to certain IP addresses

Windows Containers

  • Windows Server 2022 container host support has moved out of preview and is now generally available. Using Windows Server 2022 as the container host enables:
    • Smaller base container images
    • Non domain joined gMSA for container applications

Windows Admin Center

  • Bug Fixes
    • Installing workload cluster on DHCP network fails: dns servers is null or empty
    • Cannot load billing status information or connection status

SDN + AKS hybrid Integration

  • Support for deploying AKS hybrid on existing SDN virtual Network

Mariner Linux

Bug Fixes

  • Certificate mismatch when registry decrypt fails
  • Kube-apiserver doesn't reload the kubelet client certificate/key on each logs query resulting in error error: You must be logged in to the server (the server has asked for the client to provide credentials (pods/log kube-prometheus-stack-1664-operator-xxxxxxj)
  • CSI Node Driver is ignoring the check to see if the volume is already mounted
  • Windows node base image does not include the latest versions of several container images, resulting in extra downloads for each node that is instantiated
  • Updated several components and dependencies to the latest versions to fix CVEs.
  • Load balancers (HAProxy) lose track of their peers when multiple are deployed

Release 2023-01-30

30 Jan 23:23
686562c
Compare
Choose a tag to compare

The AKS-hybrid update for January2023 has been released. If you have installed any of the previous releases of AKS-hybrid, you can upgrade to the January 2023 update of AKS-hybrid.

Please download the latest release here.

Announcements

  • We will retire AKS-HCI versions, starting with February 2022, March 2022 and May 2022 updates in January 2023. Please update your clusters to remain in support.

  • Important: If you had shut down your AKS clusters during the holiday season or trying to update them, you likely may have internal certificates or tokens that are expired when you restart. You can follow these steps to recover your AKS cluster from expired certs.

  • GPU-enabled node pool is in preview. Follow these steps to try it out.

  • SDN + AKS Integration: If leveraging SDN + AKS, you can now upgrade your AKS clusters this month.

  • Please upgrade to the latest Kubernetes version. Current supported versions are:

Component October 2022 January 2023
AKShybrid 1.0.15.11104 1.0.16.10113
Kubernetes Versions 1.22.11, 1.22.15, 1.23.8, 1.23.12, 1.24.3, 1.24.6 1.22.11, 1.22.15, 1.23.8, 1.23.12, 1.24.3, 1.24.6

Release notes

Version numbers

  • AKShybrid version: 1.0.16.10113

  • Kubernetes versions: 1.22.11, 1.22.15, 1.23.8, 1.23.12, 1.24.3, 1.24.6

  • KVA version: 1.24.6

  • PowerShell: 1.1.60

  • WAC: 2211 GA version

  • AKS Extension in WAC: 2.131.0 (msft.sme.aks.2.131.0.nupkg)

  • ContainerD: 1.6.12

Features

Powershell changes

Install pre-checks for AKS on Azure Stack HCI and AKS on Windows Server

  • We continue to listen to your feedback; you told us that you have seen some specific problems when installing AKS hybrid on your system. To address those problems, in the last 2 releases, we have been adding validation tests to ensure that your system and configuration values will work prior to proceeding with the installation. Now you will see output messages highlighting the following tests:

    • MOC Host Internet Connectivity
    • MOC Host Limits
    • MOC Host Remoting
    • MOC Network Configuration
    • MOC SDN Configuration
    • MOC directories
    • Failover Cluster Health
    • Failover Cluster HCI Registration
    • VM Creation in Hyper-V
    • Availability of a Switch in Hyper-V
    • AKS Management cluster configuration
    • Azure user permissions
    • Proxy configuration
  • We plan to continue adding validation tests in the coming releases. Here are some PowerShell changes we did to increase the number of validation tests:

  • Changes to Set-AksHciConfig:

    • Current Behavior: Set-AksHciConfig runs validation test for the Microsoft On-Premises Cloud (MOC) and set configuration values for both MOC and AKS hybrid. Currently It does not Install MOC or run validation tests for AKS hybrid.
    • New Behavior:
      • Set-AksHciConfig will now install MOC as prerequisites for AKS hybrid, if it is not already installed. MOC is required to run AKS hybrid validation tests.
      • In addition to running validation check for MOC , It will also run validation test for AKS hybrid. Validation tests can be skipped by passing -SkipValidationCheck flag.
      • If MOC is already installed, Set-AksHciConfig will skip setting configuration for MOC and continue setting configuration for AKS hybrid. Users will have to execute 'Uninstall-Moc' first, if they want to provide new configuration for MOC before installing AKS hybrid.
      • If Set-AksHciConfig fails after installing MOC, it will automatically uninstall MOC.
  • Changes to Set-AksHciRegistration:

    • We have also added a validation check during Set-AksHciRegistration. This validation check will make sure the user has proper AAD permission to create Azure Resources in case they don't provide one. The validation check can be skipped by passing -SkipValidationCheck flag.
  • Changes to Install-AksHci: Install-AksHci will not install MOC anymore. MOC will be installed in Set-AksHciConfig.

  • Restrict SSH Access to VMs to an allowed set of IPs

    • There is a new security feature in the Jan AKS hybrid release to restrict ssh access to underlying VMs to only certain IP addresses. Today, anyone with administrator access to AKS hybrid has access to VMs through ssh on any machine.
  • Required system telemetry endpoint

    • We have introduced a new endpoint for telemetry. AKShybrid users should ensure that the endpoint gcs.prod.monitoring.core.windows.net is enabled.

Windows Admin Center

  • You can now edit the details of existing node pool configurations in the Kubernetes cluster creation wizard
  • UI improvements to DNS servers field on the Host configuration page
  • UI improvements to the Resource group and Azure region fields on the Azure registration pages

SDN + AKS Hybrid Integration

  • Upgrade Support: You can now upgrade your AKS clusters.

  • Resolution of the 80-character limit bug that may have been seen by using naming conventions.

Mariner

  • Mariner version 2.0.20221222

Bugs fixes/ Documentation

October 2022 Update

15 Nov 23:34
7fad049
Compare
Choose a tag to compare

The AKS-hybrid update for October 2022 has been released. If you have installed any of the previous releases of AKS-hybrid, you can upgrade to the October 2022 update of AKS-hybrid.

Please download the latest release here.

Announcements

  • We will retire AKS-HCI versions, starting with February 2022, March 2022 and May 2022 updates in January 2023. This release also marks the end-of-support for the August 2022 update (AKS-HCI versions 1.0.13.10907). Please update your clusters to remain in support.

  • Announcing support for Azure Stack HCI 22H2 as a validated host OS for AKS on Azure Stack HCI.

  • Important: If you plan on shutting down your AKS clusters or skip updating during the holiday season, you will likely have internal certificates or tokens expiring when you restart your environment. You can follow these steps to recover your AKS cluster from expired certs.

  • GPU-enabled node pool is in preview. Follow these steps to try it out.

  • We have retired 'v1.22.6' in this release and announcing support for v1.24.x. please upgrade to the latest Kubernetes version. Current supported versions are:

Component September 2022 October 2022
AKShybrid 1.0.14.10929 1.0.15.11104
Kubernetes Versions 1.22.6, 1.22.11, 1.23.5, 1.23.8 1.22.11, 1.22.15, 1.23.8, 1.23.12, 1.24.3, 1.24.6

Release notes

Version numbers

  • AKShybrid version: 1.0.15.11104

  • Kubernetes versions: 1.22.11, 1.22.15, 1.23.8, 1.23.12, 1.24.3, 1.24.6

  • KVA version: 1.23.12

  • PowerShell: 1.1.51

  • WAC: 2110.2

  • AKS Extension in WAC: 2.108.0 (msft.sme.aks.108.0.nupkg)

  • ContainerD: 1.6.6

Features

  • Azure RBAC preview

  • Offline download GA

Mariner

Bugs fixes/ Documentation

Features that improve install experience

September 2022 Update

11 Oct 17:55
1fabec7
Compare
Choose a tag to compare

The AKS-HCI update for September 2022 has been released. If you have installed any of the previous releases of AKS-HCI, you can upgrade to the September 2022 update of AKS-HCI.

Please download the latest release here.

Release Notes

Version Numbers:

  • AKS-HCI version: 1.0.14.10929

  • Kubernetes versions: 1.22.6, 1.22.11, 1.23.5, 1.23.8

  • KVA version: 1.23.8

  • PowerShell: 1.1.43

  • WAC: 2110.2

  • AKS Extension in WAC: 2.96.0 (msft.sme.aks.2.96.0.nupkg)

  • ContainerD: 1.6.6

Features

  • SDN is now in GA

  • [Preview] Image offline download cmdlets

  • Support for multiple administrators via Administrators group

Mariner

  • CBL-Mariner 2.0

Windows

  • September update

Bug Fixes