concept copy in category kubernetes

This is an excerpt from Manning's book Core Kubernetes.
Copy-on-write is an idiom in which effects all levels of computing. You’ve likely had to write code, which copied a data structure and synchronized its contents with its original content at a later time. It is also likely that you’ve had to keep track of the changes when copying these changes. The best-known example of this type of behavior is
git, which heavily leverages this mechanism to store its ‘blobs’, which represent your code.

This is an excerpt from Manning's book Kubernetes in Action.
But layers don’t only make distribution more efficient, they also help reduce the storage footprint of images. Each layer is only stored once. Two containers created from two images based on the same base layers can therefore read the same files, but if one of them writes over those files, the other one doesn’t see those changes. Therefore, even if they share files, they’re still isolated from each other. This works because container image layers are read-only. When a container is run, a new writable layer is created on top of the layers in the image. When the process in the container writes to a file located in one of the underlying layers, a copy of the whole file is created in the top-most layer and the process writes to the copy.
While the application is running, you can decide you want to increase or decrease the number of copies, and Kubernetes will spin up additional ones or stop the excess ones, respectively. You can even leave the job of deciding the optimal number of copies to Kubernetes. It can automatically keep adjusting the number, based on real-time metrics, such as CPU load, memory consumption, queries per second, or any other metric your app exposes.