Merge pull request #41920 from asa3311/sync-zh-25

[zh-cn] sync ephemeral-volumes storage-classes connect-applications-service

Author: k8s-ci-robot

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

@@ -75,7 +75,7 @@ different purposes:
 - [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)
- which specifically [support this feature](https://kubernetes-csi.github.io/docs/drivers.html)
+ 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
 -->
@@ -87,7 +87,7 @@ Kubernetes 为了不同的用途，支持几种不同类型的临时卷：
  [secret](/zh-cn/docs/concepts/storage/volumes/#secret)：
  将不同类型的 Kubernetes 数据注入到 Pod 中
 - [CSI 临时卷](/zh-cn/docs/concepts/storage/volumes/#csi-ephemeral-volumes)：
- 类似于前面的卷类型，但由专门[支持此特性](https://kubernetes-csi.github.io/docs/drivers.html)
+ 类似于前面的卷类型，但由专门[支持此特性](https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html)
  的指定
  [CSI 驱动程序](https://github.com/container-storage-interface/spec/blob/master/spec.md)提供
 - [通用临时卷](#generic-ephemeral-volumes)：

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

@@ -88,6 +88,28 @@ mountOptions:
 volumeBindingMode: Immediate
 ```
 
+<!--
+### Default StorageClass
+
+When a PVC does not specify a `storageClassName`, the default StorageClass is
+used. The cluster can only have one default StorageClass. If more than one
+default StorageClass is accidentally set, the newest default is used when the
+PVC is dynamically provisioned.
+
+For instructions on setting the default StorageClass, see
+[Change the default StorageClass](/docs/tasks/administer-cluster/change-default-storage-class/).
+Note that certain cloud providers may already define a default StorageClass.
+-->
+### 默认 StorageClass {#default-storageclass} 
+
+当一个 PVC 没有指定 `storageClassName` 时，会使用默认的 StorageClass。
+集群中只能有一个默认的 StorageClass。如果不小心设置了多个默认的 StorageClass，
+当 PVC 动态配置时，将使用最新设置的默认 StorageClass。
+
+关于如何设置默认的 StorageClass，
+请参见[更改默认 StorageClass](/zh-cn/docs/tasks/administer-cluster/change-default-storage-class/)。
+请注意，某些云服务提供商可能已经定义了一个默认的 StorageClass。
+
 <!--
 ### Provisioner
 

content/zh-cn/docs/tutorials/services/connect-applications-service.md

@@ -229,11 +229,11 @@ my-nginx-7vzhx IPv4 80 10.244.2.5,10.244.3.4 21s
 You should now be able to curl the nginx Service on `<CLUSTER-IP>:<PORT>` from
 any node in your cluster. Note that the Service IP is completely virtual, it
 never hits the wire. If you're curious about how this works you can read more
-about the [service proxy](/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies).
+about the [service proxy](/docs/reference/networking/virtual-ips/).
 -->
 现在，你应该能够从集群中任意节点上使用 curl 命令向 `<CLUSTER-IP>:<PORT>` 发送请求以访问 Nginx Service。
 注意 Service IP 完全是虚拟的，它从来没有走过网络，如果对它如何工作的原理感到好奇，
-可以进一步阅读[服务代理](/zh-cn/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies)的内容。
+可以进一步阅读[服务代理](/zh-cn/docs/reference/networking/virtual-ips/)的内容。
 
 <!--
 ## Accessing the Service
@@ -360,7 +360,7 @@ IP 分配名称的 DNS 服务器。 这里我们使用 CoreDNS 集群插件（
 让我们运行另一个 curl 应用来进行测试：
 
 ```shell
-kubectl run curl --image=radial/busyboxplus:curl -i --tty
+kubectl run curl --image=radial/busyboxplus:curl -i --tty --rm
 ```
 ```
 Waiting for pod default/curl-131556218-9fnch to be running, status is Pending, pod ready: false