The whole category in one page.
A CONTAINER IS A PROCESS, NOT A MACHINE
The kernel is shared, which is why containers are packaging and isolation, but not a security boundary between untrusted parties.
DATA IN A CONTAINER DISAPPEARS WITH IT
Anything that must survive goes on a volume, and volumes need backups exactly like any other storage.
NEVER DEPLOY A MOVING TAG
Pin to a version or digest, or you cannot know what is running or reproduce it.
SET MEMORY LIMITS AND LOG ROTATION ON EVERYTHING
A leaking container without a limit takes the host down; unrotated logs fill the disk quietly over weeks.
SECRETS IN IMAGES OR BUILD ARGUMENTS ARE PERMANENT
They stay in the layers and the history, readable by anyone holding the image.
LIVENESS PROBES MUST NOT CHECK DEPENDENCIES
A database outage otherwise restarts every application pod and makes recovery harder.
GRACEFUL SHUTDOWN IS AN APPLICATION PROBLEM, NOT A PLATFORM ONE
Without it, every deployment drops requests in flight.
ORCHESTRATION SOLVES MULTI-HOST PROBLEMS — SO HAVE THEM FIRST
Most applications never reach the scale where a cluster pays for itself, and the honest test is whether someone can diagnose it at three in the morning.
