Correct bugs

This commit is contained in:
Guangze GAO
2020-05-23 18:00:51 +08:00
parent cb84e91c70
commit f849accf5f
@@ -70,7 +70,7 @@ Currently, expanding volume is only available with those storage provisioners:
In order to enable this feature, we should set feature gate `ExpandPersistentVolumes` true and turn on the `PersistentVolumeClaimResize` admission plugin. Once `PersistentVolumeClaimResize` has been enabled, resizing will be allowed by a Storage Class whose `allowVolumeExpansion` field is set to true. In order to enable this feature, we should set feature gate `ExpandPersistentVolumes` true and turn on the `PersistentVolumeClaimResize` admission plugin. Once `PersistentVolumeClaimResize` has been enabled, resizing will be allowed by a Storage Class whose `allowVolumeExpansion` field is set to true.
--> -->
为了启用此功能,我们应该将功能门 `ExpandPersistentVolumes` 设置为 true 并打开 `PersistentVolumeClaimResize` 准入插件。 一旦启用了 `PersistentVolumeClaimResize`,则其对应的 `allowVolumeExpansion` 字段设置为 true 的存储类将允许调整大小。 为了启用此功能,我们应该将特性开关 `ExpandPersistentVolumes` 设置为 true 并打开 `PersistentVolumeClaimResize` 准入插件。 一旦启用了 `PersistentVolumeClaimResize`,则其对应的 `allowVolumeExpansion` 字段设置为 true 的存储类将允许调整大小。
<!-- <!--
Unfortunately, dynamically expanding volume through the Container Storage Interface (CSI) and Kubernetes is unavailable, even though the underlying storage providers have this feature. Unfortunately, dynamically expanding volume through the Container Storage Interface (CSI) and Kubernetes is unavailable, even though the underlying storage providers have this feature.
@@ -118,7 +118,7 @@ This diagram depicts a kind of high-level Kubernetes archetypes integrated with
* Red arrows present gRPC to call against Volume Driver * Red arrows present gRPC to call against Volume Driver
--> -->
* 引入了三个新的外部组件以分离 Kubernetes 和存储提供程序逻辑 * 引入了三个新的外部组件以解耦 Kubernetes 和存储提供程序逻辑
* 蓝色箭头表示针对 API 服务器进行调用的常规方法 * 蓝色箭头表示针对 API 服务器进行调用的常规方法
* 红色箭头显示 gRPC 以针对 Volume Driver 进行调用 * 红色箭头显示 gRPC 以针对 Volume Driver 进行调用