Auditing Minikube resource allocations to prevent unnecessary rebuilds
Using container inspection to verify cluster memory before deleting the environment.
What this is
This log documents how I verified resources for a local Minikube cluster using the Docker driver. It shows why you should inspect active containers before deleting your environment.
The constraint
I thought my 3-replica deployment was failing due to a default 2048MB memory limit in Minikube. I planned to delete the cluster, update the configuration, and rebuild everything to allocate 4096MB of RAM.
The proof
Before deleting the cluster, I checked the host Docker daemon and the active Kubernetes namespaces to verify the memory shortage:
$ minikube config view
$ docker inspect minikube --format='Memory: {{.HostConfig.Memory}}'
Memory: 8589934592
$ kubectl get pods -n default
NAME READY STATUS RESTARTS AGE
simple-model-api-deployment-6d694f7ddc-5z8fw 1/1 Running 1 (9m27s ago) 26h
simple-model-api-deployment-6d694f7ddc-crrxz 1/1 Running 0 3m44s
simple-model-api-deployment-6d694f7ddc-wsh4k 1/1 Running 0 3m44s
The resolution
The logs showed the active Minikube container already had an 8 GiB memory limit from its initial setup. Because the allocation was double my target, the control plane successfully scheduled all three replicas without bottlenecks.
Checking the true state of the container saved me from deleting and rebuilding the cluster.
The closing
Verifying the active infrastructure with inspection commands prevents unnecessary system resets.