From e99a7c9db83fff6fbe465e137423fa6ac45e0bb8 Mon Sep 17 00:00:00 2001 From: Matt Dorn Date: Thu, 31 Aug 2017 17:41:35 -0700 Subject: [PATCH] use the term 'node' for consistency --- docs/concepts/storage/volumes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/concepts/storage/volumes.md b/docs/concepts/storage/volumes.md index 28cb140e48..e6030cf18a 100644 --- a/docs/concepts/storage/volumes.md +++ b/docs/concepts/storage/volumes.md @@ -112,11 +112,11 @@ Some uses for an `emptyDir` are: container serves the data By default, `emptyDir` volumes are stored on whatever medium is backing the -machine - that might be disk or SSD or network storage, depending on your +node - that might be disk or SSD or network storage, depending on your environment. However, you can set the `emptyDir.medium` field to `"Memory"` to tell Kubernetes to mount a tmpfs (RAM-backed filesystem) for you instead. While tmpfs is very fast, be aware that unlike disks, tmpfs is cleared on -machine reboot and any files you write will count against your container's +node reboot and any files you write will count against your container's memory limit. #### Example pod