*** Bug 1795185 has been marked as a duplicate of this bug. ***
*** Bug 1802639 has been marked as a duplicate of this bug. ***
verified with version : 4.4.0-0.nightly-2020-06-08-083627 memory-hog-pod got Evicted after 3m2s $ oc get pod -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES memory-hog-pod 0/1 Evicted 0 6m4s <none> ip-10-0-210-116.us-east-2.compute.internal <none> <none> $ oc describe node ip-10-0-210-116.us-east-2.compute.internal Name: ip-10-0-210-116.us-east-2.compute.internal Roles: worker ... Allocated resources: (Total limits may be over 100 percent, i.e., overcommitted.) Resource Requests Limits -------- -------- ------ cpu 547m (36%) 100m (6%) memory 2027Mi (29%) 537Mi (7%) ephemeral-storage 0 (0%) 0 (0%) hugepages-1Gi 0 (0%) 0 (0%) hugepages-2Mi 0 (0%) 0 (0%) attachable-volumes-aws-ebs 0 0 Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning EvictionThresholdMet 2m40s kubelet, ip-10-0-210-116.us-east-2.compute.internal Attempting to reclaim memory Normal NodeHasInsufficientMemory 2m33s kubelet, ip-10-0-210-116.us-east-2.compute.internal Node ip-10-0-210-116.us-east-2.compute.internal status is now: NodeHasInsufficientMemory
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2589