-
Notifications
You must be signed in to change notification settings - Fork 306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Azure Defender for Containers memory metrics reading error #3846
Comments
@miwithro - do we have and ETA on a fix for this |
Hey guys, |
Also hitting this issue and it's generating 300m load on the cluster |
@miwithro , @CocoWang-wql can we please help with next steps here. |
Guys, |
Seeing the same thing after enabling Defender for Containers
Inspecting one of the nodes, I can see 3 files
One thing I noticed, is that kubernetes/kubernetes#118916 mentions |
Guys, |
Also hitting the same issue on AKS 1.27.3. |
Hey guys |
Hello, |
+1 Kubernetes version - 1.27.3 |
k8s: 1.27.7 |
Issue needing attention of @Azure/aks-leads |
5 similar comments
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
Issue needing attention of @Azure/aks-leads |
For me issue is fixed. |
Describe the bug
From Jul 27 Defender pods stopped to read memory metrics because of changes cgroup to V2.
Now microsoft-defender-collector-ds pods spam messages
Expected behavior
Reading the correct system files
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: