Kubernetes / Pods, Containers & Application Health
Investigate container writable-layer growth before increasing node disks
A Pod can consume local ephemeral space through logs, writable layers or emptyDir data. Inspect its configured resource expectations.
Environment and inputs: Kubernetes · kubectl with supported client/server versions and delegated RBAC. Examples use namespace app unless noted. Check context, namespace, APIs and provider support first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
kubectl -n app get pod web-0 -o jsonpath='{.spec.containers[*].resources}'Read the result
The result shows declared requests and limits for regular containers. It does not report actual filesystem consumption or all Pod-level temporary volumes.
Resolve and verify
Compare workload metrics, node pressure and application write paths. Redirect durable content to appropriate storage and bound temporary growth through a tested design.
Before changing production
Do not delete runtime-managed files or assume a larger ephemeral limit creates physical capacity.