Update aks-increased-memory-usage-cgroup-v2.md

Author: mosbahmajed

support/azure/azure-kubernetes/create-upgrade-delete/aks-increased-memory-usage-cgroup-v2.md

@@ -1,8 +1,8 @@
 ---
 title: Increased memory usage reported in Kubernetes 1.25 or later versions
 description: Resolve an increase in memory usage that's reported after you upgrade an Azure Kubernetes Service (AKS) cluster to Kubernetes 1.25.x.
-ms.date: 07/13/2023
-editor: v-jsitser
+ms.date: 12/22/2024
+editor: momajed
 ms.reviewer: aritraghosh, cssakscic, v-leedennis
 ms.service: azure-kubernetes-service
 ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
@@ -34,12 +34,36 @@ This increase is caused by a change in memory accounting within version 2 of the
 
 - If you see a higher eviction rate on the pods, [use higher limits and requests for pods](/azure/aks/developer-best-practices-resource-management#define-pod-resource-requests-and-limits).
 
+- cgroup v2 uses a different API than cgroup v1, so if there are any applications that directly access the cgroup file system, they need to be updated to newer versions that support cgroup v2. For example:
+
+  - **Third-Party Monitoring and Security Agents**:  
+    Some monitoring and security agents depend on the cgroup filesystem. Update these agents to versions that support cgroup v2.
+
+  - **Java Applications**:  
+    Prefer to use versions that fully support cgroup v2:
+    - OpenJDK / HotSpot: `jdk8u372`, `11.0.16`, `15`, and later.
+    - IBM Semeru Runtimes: `8.0.382.0`, `11.0.20.0`, `17.0.8.0`, and later.
+    - IBM Java: `8.0.8.6` and later.
+
+  - **uber-go/automaxprocs**:  
+    If you are using the `uber-go/automaxprocs` package, ensure the version is `v1.5.1` or higher.
+
+- An alternative temporary solution is to revert the cgroup version on your nodes by using the following DaemonSet:  
+[Revert to cgroup v1 DaemonSet](https://github.com/Azure/AKS/blob/master/examples/cgroups/revert-cgroup-v1.yaml)
+
+**Note**:  
+- The DaemonSet, by default, applies to all nodes in your cluster and will reboot them to implement the cgroup change.  
+- To control how this gets applied, configure a `nodeSelector` to target specific nodes.
+
+
 > [!NOTE]  
 > If you experience only an increase in memory use without any of the other symptoms that are mentioned in the "Symptoms" section, you don't have to take any action.
 
 ## Status
 
-We're actively working with the Kubernetes community to fix the underlying issue, and we'll keep you updated on our progress. We also plan to change the eviction thresholds or [resource reservations](/azure/aks/concepts-clusters-workloads#resource-reservations), depending on the outcome of the fix.
+We're actively working with the Kubernetes community to resolve the underlying issue. Progress on this effort can be tracked at [Azure/AKS Issue #3443](https://github.com/Azure/AKS/issues/3443). 
+
+As part of the resolution, we plan to either adjust the eviction thresholds or update [resource reservations](/azure/aks/concepts-clusters-workloads#resource-reservations), depending on the outcome of the fix.
 
 ## Reference