Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article identifies known issues and their workarounds in AKS. These release notes are continuously updated, and as issues that require a workaround are discovered, they're added here.
If you encounter an issue that isn't listed here, please open a support request.
Known issues
The following section describes known issues for AKS Hybrid and Edge:
| AKS CRUD operation | Issue | Fix status |
|---|---|---|
| AKS cluster upgrade | Cluster with Azure Policy or Gatekeeper unhealthy after upgrade | Active |
| AKS cluster create | Cluster create fails after Azure Local update from 2510 | Active |
| AKS cluster create | Can't create AKS cluster with GPU-enabled default node pool | Active |
| AKS steady state | Storage provisioning issue impacting cluster and node pool creation | Active |
| AKS cluster delete | Deleted AKS cluster still visible on Azure portal | Active |
| AKS steady state | Disk space exhaustion on control plane VMs due to accumulation of kube-apiserver audit logs | Fixed in 2507 release |
| AKS cluster upgrade | AKS cluster stuck in "Upgrading" state | Fixed in 2505 release |