dry-island-5201
11/03/2022, 3:44 PMminiature-hairdresser-1087
11/03/2022, 6:52 PMdamp-tent-77102
11/03/2022, 8:30 PMcrooked-scooter-58172
11/04/2022, 2:47 AMproud-addition-21854
11/04/2022, 7:27 PMquaint-alarm-7893
11/08/2022, 5:39 PMquaint-alarm-7893
11/08/2022, 5:39 PMcuddly-umbrella-82227
11/08/2022, 8:50 PMsteep-salesmen-26256
11/09/2022, 5:26 AMbright-fireman-42144
11/10/2022, 3:43 PMbright-fireman-42144
11/10/2022, 3:59 PMbright-fireman-42144
11/11/2022, 1:35 AMbright-fireman-42144
11/11/2022, 4:18 PMbright-fireman-42144
11/11/2022, 5:43 PMpowerful-soccer-11224
11/15/2022, 6:50 AMAllocated CPU: 96C
Allocated Memory: 188GiB
Allocated Storage: 758GiB
Now when we are trying to create VMs (CPU: 4cores
Memory: 8Gi
)on the node using our custom k8s controller (operator), we observed that Actual memory usage was close to 35%, but the reserved memory on the Harvester node was almost 99% and VM creation was not going through anymore.
(attached snippet). Can anyone explain me the reason for this and how can we overcome this ?most-holiday-75301
11/16/2022, 8:32 PMlively-translator-30710
11/17/2022, 6:40 PMhigh-alligator-99144
11/17/2022, 8:02 PMcrooked-scooter-58172
11/17/2022, 9:50 PMchilly-jewelry-23407
11/18/2022, 2:57 AMmelodic-receptionist-94532
11/18/2022, 5:09 AMkubectl -n harvester-system get po
I see kube-vip-s9hsl
with Status Error
and disk read massive (230MBps). How can I dig into why this system isn't coming up?melodic-receptionist-94532
11/18/2022, 5:10 AMmelodic-receptionist-94532
11/18/2022, 5:26 AMmelodic-receptionist-94532
11/18/2022, 5:44 AMharvester...
= CrashLoopBackoff, kubevirt...
= StartError with a second in ContainerCreating
proud-addition-21854
11/18/2022, 3:29 PMcrooked-scooter-58172
11/18/2022, 5:59 PMchilly-jewelry-23407
11/18/2022, 8:17 PMjolly-answer-83836
11/18/2022, 9:02 PMcrooked-scooter-58172
11/21/2022, 7:20 PMstale-painting-80203
11/21/2022, 9:48 PM