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
Your support suggested to increase the resource requests to alleviate resource issues, and thus we suggest you upstream this change here too for others to avoid the same issue.
As per your colleagues:
To address the issue of "container ID not found" logs on Kubernetes nodes, it appears that the resource allocations for both the `s1-agent` DaemonSet and the `s1-agent-helper` Deployment have been updated. The changes are as follows:
DaemonSet `sentinel-one/s1-agent`
- Previous Resource Requests:
- CPU: 100m
- Memory: 800Mi
- Updated Resource Requests:
- CPU: 900m
- Memory: 1500Mi
Deployment `sentinel-one/s1-agent-helper`
- Previous Resource Requests:
- CPU: 100m
- Memory: 100Mi
- Updated Resource Requests:
- CPU: 900m
- Memory: 1945Mi
These changes should help in addressing the resource constraints that might be causing the "container ID not found" logs.
Your support suggested to increase the resource requests to alleviate resource issues, and thus we suggest you upstream this change here too for others to avoid the same issue.
As per your colleagues:
I.e. changing these default values:
For the Agent:
helm-charts/charts/s1-agent/values.yaml
Lines 84 to 90 in ecffe4c
For the Helper:
helm-charts/charts/s1-agent/values.yaml
Lines 114 to 120 in ecffe4c
The text was updated successfully, but these errors were encountered: