When testing configmap creation via Local PC, kubectl takes a whooping 1.5GB RAM and 20% CPU util to create the configmap
Strange thing is, same kubectl version in a different env works perfectly fine, using hardly 124MB RAM from the microservice
I am using alpine-3.18 image with kubectl copied to its /usr/bin/.The image in other env takes 124MB RAM for the process to complete, while in actual env takes more than 1.5GB RAM to do the same operation (gets OOM Killed most of the time while exiting with Client.Timeout or context cancellation while reading body error sometimes)
Can you share what/how to debug such high RAM utilization for the said env ?