Release notes for 2507

Author: rcheeran

AKS-Arc/aks-troubleshoot.md

@@ -24,8 +24,8 @@ The following sections describe known issues for AKS enabled by Azure Arc:
 
 | AKS Arc CRUD operation | Issue | Fix status |
 |------------------------|-------|------------|
-| AKS steady state       | [AKS Arc telemetry pod consumes too much memory and CPU](telemetry-pod-resources.md) | Active |
 | AKS cluster delete     | [Deleted AKS Arc cluster still visible on Azure portal](deleted-cluster-visible.md) | Active |
+| AKS steady state       | [AKS Arc telemetry pod consumes too much memory and CPU](telemetry-pod-resources.md) | Fixed in 2507 release  |
 | AKS cluster create     | [Can't create AKS cluster or scale node pool because of issues with AKS Arc images](gallery-image-not-usable.md) | Fixed in 2507 release |
 | AKS steady state       | [Disk space exhaustion on control plane VMs due to accumulation of kube-apiserver audit logs](kube-apiserver-log-overflow.md) | Fixed in 2507 release |
 | AKS cluster upgrade    | [AKS Arc cluster stuck in "Upgrading" state](cluster-upgrade-status.md) | Fixed in 2505 release |
@@ -43,7 +43,7 @@ The following sections describe known issues for AKS enabled by Azure Arc:
 | Create validation      | [KubeAPIServer unreachable error](kube-api-server-unreachable.md) |
 | Network configuration issues | [Use diagnostic checker](aks-arc-diagnostic-checker.md) |
 | Kubernetes steady state   | [Resolve issues due to out-of-band deletion of storage volumes](delete-storage-volume.md) |
-| Kubernetes steady state   | [Repeated Entra authentication prompts when running kubectl with Kubernetes RBAC](entra-prompts.md) | 
+| Kubernetes steady state   | [Repeated Entra authentication prompts when running kubectl with Kubernetes RBAC](entra-prompts.md) |
 | Release validation     | [Azure Advisor upgrade recommendation message](azure-advisor-upgrade.md) |
 | Network validation | [Network validation error due to .local domain](network-validation-error-local.md) |
 | Network validation | [Troubleshoot BGP with FRR in AKS Arc environments](connectivity-troubleshoot.md) |

AKS-Arc/gallery-image-not-usable.md

@@ -43,12 +43,10 @@ When you run `az aksarc get-versions`, you see the following errors:
 
 ## Mitigation
 
-This issue was fixed in AKS on [Azure Local, version 2507](/azure/azure-local/whats-new?view=azloc-2507&preserve-view=true#features-and-improvements-in-2507). Upgrade your Azure Local deployment to the 2507 build. 
+This issue was fixed in AKS on [Azure Local, version 2507](/azure/azure-local/whats-new?view=azloc-2507&preserve-view=true#features-and-improvements-in-2507). Upgrade your Azure Local deployment to the 2507 build.
 
-- Upgrade your Azure Local deployment to the 2507 build.
 - Once updated, confirm that the images have been downloaded successfully by running the `az aksarc get-versions` command.
-- For new AKS clusters: new AKS clusters should now be created successfully.
-- For scaling existing AKS clusters: scaling existing AKS clusters continues to encounter issues. Please file a support case.
+- You should now be able to create new clusters and scale existing clusters using the available images.
 
 ## Next steps
 

AKS-Arc/telemetry-pod-resources.md

@@ -9,8 +9,6 @@ ms.reviewer: abha
 
 ---
 
-# AKS Arc telemetry pod consumes too much memory and CPU
-
 ## Symptoms
 
 The **akshci-telemetry** pod in a AKS Arc cluster can over time consume a lot of CPU and memory resources. If metrics are enabled, you can verify the CPU and memory usage using the following `kubectl` command:
@@ -28,9 +26,13 @@ akshci-telemetry-5df56fd5-rjqk4   996m         152Mi
 
 ## Mitigation
 
+This issue was fixed in AKS on [Azure Local, version 2507](/azure/azure-local/whats-new?view=azloc-2507&preserve-view=true#features-and-improvements-in-2507). Upgrade your Azure Local deployment to the 2507 build.
+
+### Workaround for Azure Local versions 2506 and older
+
 To resolve this issue, set default **resource limits** for the pods in the `kube-system` namespace.
 
-### Important notes
+#### Important notes
 
 - Verify if you have any pods in the **kube-system** namespace that might require more memory than the default limit setting. If so, adjustments might be needed.
 - The **LimitRange** is applied to the **namespace**; in this case, the `kube-system` namespace. The default resource limits also apply to new pods that don't specify their own limits.
@@ -40,7 +42,7 @@ To resolve this issue, set default **resource limits** for the pods in the `kube
 
 To proceed with setting the resource limits, you can run the following script. While the script uses `az aksarc get-credentials`, you can also use `az connectedk8s proxy` to get the proxy kubeconfig and access the Kubernetes cluster.
 
-### Define the LimitRange YAML to set default CPU and memory limits
+#### Define the LimitRange YAML to set default CPU and memory limits
 
 ```powershell
 # Set the $cluster_name and $resource_group of the aksarc cluster
@@ -76,7 +78,7 @@ sleep 5
 kubectl get pods -l app=akshci-telemetry -n kube-system --kubeconfig "./kubeconfig-$cluster_name"
 ```
 
-### Validate if the resource limits were applied correctly
+#### Validate if the resource limits were applied correctly
 
 1. Check the resource limits in the pod's YAML configuration: