A parks worker node runs out of inodes after image sprawl even though df -h still shows free bytes. What problem should be investigated?
Select an answer to reveal the explanation.
Short Explanation
Free gigabytes with zero free inodes is a classic trap—too many tiny files or image layers used up the filename slots.
Full Explanation
Nodes can exhaust inodes (or disk space) from container image layers, logs, and small files even when byte capacity looks acceptable depending on the check. Inode exhaustion blocks creating new files and can trigger DiskPressure-like failures. Service CIDR size, default StorageClass location, and RBAC get-on-Nodes are different troubleshooting tracks.