Merge pull request #43527 from asa3311/sync-zh-72

[zh] sync ephemeral-volumes volumes windows-storage

Author: k8s-ci-robot

content/zh-cn/docs/concepts/storage/ephemeral-volumes.md

@@ -73,8 +73,7 @@ different purposes:
   [secret](/docs/concepts/storage/volumes/#secret): inject different
   kinds of Kubernetes data into a Pod
 - [CSI ephemeral volumes](#csi-ephemeral-volumes):
-  similar to the previous volume kinds, but provided by special
-  [CSI drivers](https://github.com/container-storage-interface/spec/blob/master/spec.md)
+  similar to the previous volume kinds, but provided by special {{< glossary_tooltip text="CSI" term_id="csi" >}} drivers
   which specifically [support this feature](https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html)
 - [generic ephemeral volumes](#generic-ephemeral-volumes), which
   can be provided by all storage drivers that also support persistent volumes
@@ -86,10 +85,9 @@ Kubernetes 为了不同的用途，支持几种不同类型的临时卷：
   [downwardAPI](/zh-cn/docs/concepts/storage/volumes/#downwardapi)、
   [secret](/zh-cn/docs/concepts/storage/volumes/#secret)：
   将不同类型的 Kubernetes 数据注入到 Pod 中
-- [CSI 临时卷](/zh-cn/docs/concepts/storage/volumes/#csi-ephemeral-volumes)：
+- [CSI 临时卷](#csi-ephemeral-volumes)：
   类似于前面的卷类型，但由专门[支持此特性](https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html)
-  的指定
-  [CSI 驱动程序](https://github.com/container-storage-interface/spec/blob/master/spec.md)提供
+  的指定 {{< glossary_tooltip text="CSI" term_id="csi" >}} 驱动程序提供
 - [通用临时卷](#generic-ephemeral-volumes)：
   它可以由所有支持持久卷的存储驱动程序提供
 

content/zh-cn/docs/concepts/storage/volumes.md

@@ -431,16 +431,15 @@ The `emptyDir.medium` field controls where `emptyDir` volumes are stored. By
 default `emptyDir` volumes are stored on whatever medium that backs the node
 such as disk, SSD, or network storage, depending on your environment. If you set
 the `emptyDir.medium` field to `"Memory"`, Kubernetes mounts a tmpfs (RAM-backed
-filesystem) for you instead.  While tmpfs is very fast, be aware that unlike
-disks, tmpfs is cleared on node reboot and any files you write count against
-your container's memory limit.
+filesystem) for you instead.  While tmpfs is very fast be aware that, unlike
+disks, files you write count against the memory limit of the container that wrote them.
 -->
 `emptyDir.medium` 字段用来控制 `emptyDir` 卷的存储位置。
 默认情况下，`emptyDir` 卷存储在该节点所使用的介质上；
 此处的介质可以是磁盘、SSD 或网络存储，这取决于你的环境。
 你可以将 `emptyDir.medium` 字段设置为 `"Memory"`，
 以告诉 Kubernetes 为你挂载 tmpfs（基于 RAM 的文件系统）。
-虽然 tmpfs 速度非常快，但是要注意它与磁盘不同：tmpfs 在节点重启时会被清除，
+虽然 tmpfs 速度非常快，但是要注意它与磁盘不同，
 并且你所写入的所有文件都会计入容器的内存消耗，受容器内存限制约束。
 
 <!--

content/zh-cn/docs/concepts/storage/windows-storage.md

@@ -62,7 +62,7 @@ As a result, the following storage functionality is not supported on Windows nod
 * Block device mapping
 * Memory as the storage medium (for example, `emptyDir.medium` set to `Memory`)
 * File system features like uid/gid; per-user Linux filesystem permissions
-* Setting [secret permissions with DefaultMode](/docs/concepts/configuration/secret/#secret-files-permissions) (due to UID/GID dependency)
+* Setting [secret permissions with DefaultMode](/docs/tasks/inject-data-application/distribute-credentials-secure/#set-posix-permissions-for-secret-keys) (due to UID/GID dependency)
 * NFS based storage/volume support
 * Expanding the mounted volume (resizefs)
 -->
@@ -73,7 +73,7 @@ As a result, the following storage functionality is not supported on Windows nod
 * 块设备映射
 * 内存作为存储介质（例如 `emptyDir.medium` 设置为 `Memory`）
 * 类似 UID/GID、各用户不同的 Linux 文件系统访问许可等文件系统特性
-* 使用 [DefaultMode 设置 Secret 权限](/zh-cn/docs/concepts/configuration/secret/#secret-files-permissions)
+* 使用 [DefaultMode 设置 Secret 权限](/zh-cn/docs/tasks/inject-data-application/distribute-credentials-secure/#set-posix-permissions-for-secret-keys)
   （因为该特性依赖 UID/GID）
 * 基于 NFS 的存储和卷支持
 * 扩展已挂载卷（resizefs）