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
If the node Authentik worker ends up getting assigned to, happens to have less than optimal amount of RAM, k8s cannot know to not schedule it there without the request of resources specified so what happen is system OOM.
Node is an Raspberry Pi 4, with 2GB of RAM even tho there's others that have more.
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning SystemOOM 33m kubelet System OOM encountered, victim process: celery, pid: 3602044
Warning SystemOOM 30m kubelet System OOM encountered, victim process: celery, pid: 3603940
Warning SystemOOM 21m kubelet System OOM encountered, victim process: celery, pid: 3612872
Normal NodeHasSufficientPID 21m (x40 over 16h) kubelet Node k8s-worker3 status is now: NodeHasSufficientPID
Normal NodeReady 21m (x40 over 16h) kubelet Node k8s-worker3 status is now: NodeReady
Warning SystemOOM 6m28s kubelet System OOM encountered, victim process: celery, pid: 3632477
The text was updated successfully, but these errors were encountered:
If the node Authentik worker ends up getting assigned to, happens to have less than optimal amount of RAM, k8s cannot know to not schedule it there without the request of resources specified so what happen is system OOM.
Node is an Raspberry Pi 4, with 2GB of RAM even tho there's others that have more.
The text was updated successfully, but these errors were encountered: