Why Statelessness Is the Whole Game
Kubernetes assumes your application pods are disposable. The autoscaler adds pods under load and removes them when traffic drops; rolling updates replace old pods with new ones; a failed node’s pods get rescheduled elsewhere. Any state stored inside a pod — a user’s session in JVM memory, an uploaded file on local disk, a cache on the container filesystem — vanishes the moment that pod is replaced.
Read More
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (0)