Move Guide topics: Container Lifestyle Hooks, Images, Volumes

2017-03-20 15:35:51 -07:00
parent 6f8c97f4d2
commit f0cd49a007
34 changed files with 1055 additions and 1025 deletions
@@ -9,7 +9,7 @@ This page shows how to configure a Pod to use a Volume for storage.
 A Container's file system lives only as long as the Container does, so when a
 Container terminates and restarts, changes to the filesystem are lost. For more
 consistent storage that is independent of the Container, you can use a
-[Volume](/docs/user-guide/volumes). This is especially important for stateful
+[Volume](/docs/concepts/storage/volumes/). This is especially important for stateful
 applications, such as key-value stores and databases. For example, Redis is a
 key-value cache and store.

@@ -27,7 +27,7 @@ key-value cache and store.

 In this exercise, you create a Pod that runs one Container. This Pod has a
 Volume of type
-[emptyDir](/docs/user-guide/volumes/#emptydir)
+[emptyDir](/docs/concepts/storage/volumes/#emptydir)
 that lasts for the life of the Pod, even if the Container terminates and
 restarts. Here is the configuration file for the Pod:

@@ -103,7 +103,7 @@ of `Always`.
 supports many different network-attached storage solutions, including PD on
 GCE and EBS on EC2, which are preferred for critical data, and will handle
 details such as mounting and unmounting the devices on the nodes. See
-[Volumes](/docs/user-guide/volumes) for more details.
+[Volumes](/docs/concepts/storage/volumes/) for more details.

 {% endcapture %}