You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/azure/azure-kubernetes/create-upgrade-delete/aks-increased-memory-usage-cgroup-v2.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ This increase is caused by a change in memory accounting within version 2 of the
34
34
35
35
- 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).
36
36
37
-
- cgroup v2 uses a different API than cgroup v1. If there are any applications that directly access the cgroup file system, update them to newer versions that support cgroup v2. For example:
37
+
- cgroup v2 uses a different API than cgroup v1. If there are any applications that directly access the cgroup file system, update them to later versions that support cgroup v2. For example:
38
38
39
39
-**Third-party monitoring and security agents**:
40
40
@@ -54,7 +54,7 @@ This increase is caused by a change in memory accounting within version 2 of the
54
54
55
55
> [!IMPORTANT]
56
56
> - Use the DaemonSet cautiously. Test it in a lower environment before applying to production to ensure compatibility and prevent disruptions.
57
-
> - By default, the DaemonSet applies to all nodes in the cluster and will reboot them to implement the cgroup change.
57
+
> - By default, the DaemonSet applies to all nodes in the cluster and reboots them to implement the cgroup change.
58
58
> - To control how the DaemonSet is applied, configure a `nodeSelector` to target specific nodes.
0 commit comments