Yushiro FURUKAWA
committed by
Kubernetes Prow Robot
Kubernetes Prow Robot
parent
0268ed0c18
commit
b05129acc3
@@ -176,8 +176,8 @@ whatever reclaim policy they were assigned at creation.
|
||||
{{< feature-state for_k8s_version="v1.11" state="beta" >}}
|
||||
|
||||
<!--
|
||||
Persistent Volumes can be configured to be expandable. This feature when set to `true`,
|
||||
allows the users to resize the volume by editing the corresponding PVC object.
|
||||
Persistent Volumes can be configured to be expandable. This feature when set to `true`,
|
||||
allows the users to resize the volume by editing the corresponding PVC object.
|
||||
|
||||
The following types of volumes support volume expansion, when the underlying
|
||||
Storage Class has the field `allowVolumeExpansion` set to true.
|
||||
@@ -646,7 +646,7 @@ OpenStack 的内部驱动程序已经被弃用。请使用 [OpenStack 的外部
|
||||
-->
|
||||
`diskformat`: `thin`, `zeroedthick` 和 `eagerzeroedthick`。默认值: `"thin"`。
|
||||
|
||||
<!--
|
||||
<!--
|
||||
2. Create a StorageClass with a disk format on a user specified datastore.
|
||||
-->
|
||||
2. 在用户指定的数据存储上创建磁盘格式的 StorageClass。
|
||||
@@ -942,8 +942,8 @@ parameters:
|
||||
When `kind` is `shared`, all unmanaged disks are created in a few shared
|
||||
storage accounts in the same resource group as the cluster. When `kind` is
|
||||
`dedicated`, a new dedicated storage account will be created for the new
|
||||
unmanaged disk in the same resource group as the cluster. When `kind` is
|
||||
`managed`, all managed disks are created in the same resource group as
|
||||
unmanaged disk in the same resource group as the cluster. When `kind` is
|
||||
`managed`, all managed disks are created in the same resource group as
|
||||
the cluster.
|
||||
-->
|
||||
* `storageaccounttype`：Azure 存储帐户 Sku 层。默认为空。
|
||||
@@ -985,12 +985,12 @@ parameters:
|
||||
group are searched to find one that matches `skuName` and `location`. If a
|
||||
storage account is provided, it must reside in the same resource group as the
|
||||
cluster, and `skuName` and `location` are ignored.
|
||||
* `secretNamespace`: the namespace of the secret that contains the Azure Storage
|
||||
* `secretNamespace`: the namespace of the secret that contains the Azure Storage
|
||||
Account Name and Key. Default is the same as the Pod.
|
||||
* `secretName`: the name of the secret that contains the Azure Storage Account Name and
|
||||
Key. Default is `azure-storage-account-<accountName>-secret`
|
||||
* `readOnly`: a flag indicating whether the storage will be mounted as read only.
|
||||
Defaults to false which means a read/write mount. This setting will impact the
|
||||
Defaults to false which means a read/write mount. This setting will impact the
|
||||
`ReadOnly` setting in VolumeMounts as well.
|
||||
-->
|
||||
* `skuName`：Azure 存储帐户 Sku 层。默认为空。
|
||||
@@ -1003,9 +1003,9 @@ parameters:
|
||||
* `readOnly`：指示是否将存储安装为只读的标志。默认为 false，表示 读/写 挂载。 该设置也会影响VolumeMounts中的 `ReadOnly` 设置。
|
||||
|
||||
<!--
|
||||
During storage provisioning, a secret named by `secretName` is created for the
|
||||
mounting credentials. If the cluster has enabled both
|
||||
[RBAC](/docs/reference/access-authn-authz/rbac/) and
|
||||
During storage provisioning, a secret named by `secretName` is created for the
|
||||
mounting credentials. If the cluster has enabled both
|
||||
[RBAC](/docs/reference/access-authn-authz/rbac/) and
|
||||
[Controller Roles](/docs/reference/access-authn-authz/rbac/#controller-roles),
|
||||
add the `create` permission of resource `secret` for clusterrole
|
||||
`system:controller:persistent-volume-binder`.
|
||||
@@ -1014,7 +1014,7 @@ add the `create` permission of resource `secret` for clusterrole
|
||||
为 `system:controller:persistent-volume-binder` 的 clusterrole 添加 `secret` 资源的 `create` 权限。
|
||||
|
||||
<!--
|
||||
In a multi-tenancy context, it is strongly recommended to set the value for
|
||||
In a multi-tenancy context, it is strongly recommended to set the value for
|
||||
`secretNamespace` explicitly, otherwise the storage account credentials may
|
||||
be read by other users.
|
||||
-->
|
||||
|
||||
@@ -5,28 +5,28 @@ content_template: templates/concept
|
||||
|
||||
{{% capture overview %}}
|
||||
|
||||
<!--
|
||||
<!--
|
||||
This page describes the maximum number of volumes that can be attached
|
||||
to a Node for various cloud providers.
|
||||
-->
|
||||
|
||||
此页面描述了各个云供应商可关联至一个节点的最大卷数。
|
||||
|
||||
<!--
|
||||
<!--
|
||||
Cloud providers like Google, Amazon, and Microsoft typically have a limit on
|
||||
how many volumes can be attached to a Node. It is important for Kubernetes to
|
||||
respect those limits. Otherwise, Pods scheduled on a Node could get stuck
|
||||
waiting for volumes to attach.
|
||||
-->
|
||||
|
||||
谷歌、亚马逊和微软等云供应商通常对可以关联到节点的卷数量进行限制。
|
||||
谷歌、亚马逊和微软等云供应商通常对可以关联到节点的卷数量进行限制。
|
||||
Kubernetes 需要尊重这些限制。 否则，在节点上调度的 Pod 可能会卡住去等待卷的关联。
|
||||
|
||||
{{% /capture %}}
|
||||
|
||||
{{% capture body %}}
|
||||
|
||||
<!--
|
||||
<!--
|
||||
## Kubernetes default limits
|
||||
|
||||
The Kubernetes scheduler has default limits on the number of volumes
|
||||
@@ -36,7 +36,7 @@ that can be attached to a Node:
|
||||
## Kubernetes 的默认限制
|
||||
|
||||
The Kubernetes 调度器对关联于一个节点的卷数有默认限制：
|
||||
<!--
|
||||
<!--
|
||||
<table>
|
||||
<tr><th>Cloud service</th><th>Maximum volumes per Node</th></tr>
|
||||
<tr><td><a href="https://aws.amazon.com/ebs/">Amazon Elastic Block Store (EBS)</a></td><td>39</td></tr>
|
||||
@@ -51,7 +51,7 @@ The Kubernetes 调度器对关联于一个节点的卷数有默认限制：
|
||||
<tr><td><a href="https://azure.microsoft.com/en-us/services/storage/main-disks/">Microsoft Azure Disk Storage</a></td><td>16</td></tr>
|
||||
</table>
|
||||
|
||||
<!--
|
||||
<!--
|
||||
## Custom limits
|
||||
|
||||
You can change these limits by setting the value of the
|
||||
@@ -72,7 +72,7 @@ The limit applies to the entire cluster, so it affects all Nodes.
|
||||
|
||||
此限制应用于整个集群，所以它会影响所有节点。
|
||||
|
||||
<!--
|
||||
<!--
|
||||
## Dynamic volume limits
|
||||
-->
|
||||
|
||||
@@ -80,7 +80,7 @@ The limit applies to the entire cluster, so it affects all Nodes.
|
||||
|
||||
{{< feature-state state="beta" for_k8s_version="v1.12" >}}
|
||||
|
||||
<!--
|
||||
<!--
|
||||
Kubernetes 1.11 introduced support for dynamic volume limits based on Node type as an Alpha feature.
|
||||
In Kubernetes 1.12 this feature is graduating to Beta and will be enabled by default.
|
||||
|
||||
@@ -102,7 +102,7 @@ Kubernetes 1.11 引入了基于节点类型的动态卷限制的支持作为 Alp
|
||||
- Azure Disk
|
||||
- CSI
|
||||
|
||||
<!--
|
||||
<!--
|
||||
When the dynamic volume limits feature is enabled, Kubernetes automatically
|
||||
determines the Node type and enforces the appropriate number of attachable
|
||||
volumes for the node. For example:
|
||||
@@ -110,7 +110,7 @@ volumes for the node. For example:
|
||||
|
||||
启用动态卷限制功能后，Kubernetes 会自动确定节点类型并确保节点上可关联的卷数目合规。 例如：
|
||||
|
||||
<!--
|
||||
<!--
|
||||
* On
|
||||
<a href="https://cloud.google.com/compute/">Google Compute Engine</a>,
|
||||
up to 128 volumes can be attached to a node, [depending on the node
|
||||
|
||||
@@ -6,7 +6,7 @@ weight: 20
|
||||
|
||||
{{% capture overview %}}
|
||||
|
||||
<!--
|
||||
<!--
|
||||
This document describes the concept of `VolumeSnapshotClass` in Kubernetes. Familiarity
|
||||
with [volume snapshots](/docs/concepts/storage/volume-snapshots/) and
|
||||
[storage classes](/docs/concepts/storage/storage-classes) is suggested.
|
||||
@@ -19,7 +19,7 @@ with [volume snapshots](/docs/concepts/storage/volume-snapshots/) and
|
||||
|
||||
{{% capture body %}}
|
||||
|
||||
<!--
|
||||
<!--
|
||||
## Introduction
|
||||
|
||||
Just like `StorageClass` provides a way for administrators to describe the "classes"
|
||||
@@ -31,7 +31,7 @@ way to describe the "classes" of storage when provisioning a volume snapshot.
|
||||
|
||||
就像 `StorageClass` 为管理员提供了一种在配置卷时描述存储“类”的方法，`VolumeSnapshotClass` 提供了一种在配置卷快照时描述存储“类”的方法。
|
||||
|
||||
<!--
|
||||
<!--
|
||||
## The VolumeSnapshotClass Resource
|
||||
|
||||
Each `VolumeSnapshotClass` contains the fields `snapshotter` and `parameters`,
|
||||
@@ -66,18 +66,18 @@ snapshotter: csi-hostpath
|
||||
parameters:
|
||||
```
|
||||
|
||||
<!--
|
||||
<!--
|
||||
### Snapshotter
|
||||
|
||||
Volume snapshot classes have a snapshotter that determines what CSI volume plugin is
|
||||
used for provisioning VolumeSnapshots. This field must be specified.
|
||||
-->
|
||||
|
||||
|
||||
### 快照生成器（Snapshotter）
|
||||
|
||||
卷快照类具有一个快照生成器，用于确定配置 VolumeSnapshot 的 CSI 卷插件。 必须指定此字段。
|
||||
|
||||
<!--
|
||||
<!--
|
||||
## Parameters
|
||||
|
||||
Volume snapshot classes have parameters that describe volume snapshots belonging to
|
||||
|
||||
@@ -29,7 +29,7 @@ Kubernetes 抽象出 `Volume` 对象来解决这两个问题。
|
||||
Familiarity with [Pods](/docs/user-guide/pods) is suggested.
|
||||
-->
|
||||
|
||||
阅读本文前建议您熟悉一下 [Pods](/docs/user-guide/pods)。
|
||||
阅读本文前建议您熟悉一下 [Pods](/docs/user-guide/pods)。
|
||||
|
||||
{{% /capture %}}
|
||||
|
||||
@@ -473,7 +473,7 @@ It mounts a directory and writes the requested data in plain text files.
|
||||
-->
|
||||
|
||||
`downwardAPI` 卷用于使 downward API 数据对应用程序可用。
|
||||
这种卷类型挂载一个目录并在纯文本文件中写入请求的数据。
|
||||
这种卷类型挂载一个目录并在纯文本文件中写入请求的数据。
|
||||
|
||||
{{< note >}}
|
||||
|
||||
@@ -1149,7 +1149,7 @@ guide](https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner).
|
||||
|
||||
您可以在 Kubernetes 之外单独运行静态驱动以改进对 local 卷的生命周期管理。
|
||||
请注意，此驱动不支持动态配置。
|
||||
有关如何运行外部 `local` 卷驱动的示例，请参考
|
||||
有关如何运行外部 `local` 卷驱动的示例，请参考
|
||||
[local 卷驱动用户指南](https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner)。
|
||||
|
||||
{{< note >}}
|
||||
@@ -1502,7 +1502,7 @@ means that a RBD volume can be pre-populated with data, and that data can
|
||||
be "handed off" between Pods.
|
||||
-->
|
||||
|
||||
`rbd` 卷允许将 [Rados 块设备](http://ceph.com/docs/master/rbd/rbd/) 卷挂载到您的 Pod 中.
|
||||
`rbd` 卷允许将 [Rados 块设备](http://ceph.com/docs/master/rbd/rbd/) 卷挂载到您的 Pod 中.
|
||||
不像 `emptyDir` 那样会在删除 Pod 的同时也会被删除，`rbd` 卷的内容在删除 Pod 时会被保存，卷只是被卸载掉了。
|
||||
这意味着 `rbd` 卷可以被预先填充数据，并且这些数据可以在 Pod 之间"传递"。
|
||||
|
||||
@@ -1734,7 +1734,7 @@ You must create VMDK using one of the following methods before using with Pod.
|
||||
Choose one of the following methods to create a VMDK.
|
||||
-->
|
||||
|
||||
#### 创建 VMDK 卷
|
||||
#### 创建 VMDK 卷
|
||||
|
||||
选择下列方式之一创建 VMDK。
|
||||
|
||||
@@ -2086,7 +2086,7 @@ persistent volume:
|
||||
- `volumeAttributes`：一个字符串到字符串的映射表，用来设置卷的静态属性。
|
||||
该映射必须与 CSI 驱动程序返回的 `CreateVolumeResponse` 中的 `volume.attributes` 字段的映射相对应；[CSI 规范](https://github.com/container-storage-interface/spec/blob/master/spec.md#createvolume) 中有相应的定义。
|
||||
该映射通过`ControllerPublishVolumeRequest`、`NodeStageVolumeRequest`、和 `NodePublishVolumeRequest` 中的 `volume_attributes` 字段传递给 CSI 驱动。
|
||||
|
||||
|
||||
<!--
|
||||
- `controllerPublishSecretRef`: A reference to the secret object containing
|
||||
sensitive information to pass to the CSI driver to complete the CSI
|
||||
@@ -2098,7 +2098,7 @@ persistent volume:
|
||||
- `controllerPublishSecretRef`：对包含敏感信息的 secret 对象的引用；该敏感信息会被传递给 CSI 驱动来完成 CSI `ControllerPublishVolume` 和 `ControllerUnpublishVolume` 调用。
|
||||
此字段是可选的；在不需要 secret 时可以是空的。
|
||||
如果 secret 对象包含多个 secret，则所有的 secret 都会被传递。
|
||||
|
||||
|
||||
<!--
|
||||
- `nodeStageSecretRef`: A reference to the secret object containing
|
||||
sensitive information to pass to the CSI driver to complete the CSI
|
||||
@@ -2118,7 +2118,7 @@ persistent volume:
|
||||
secret is required. If the secret object contains more than one secret, all
|
||||
secrets are passed.
|
||||
-->
|
||||
|
||||
|
||||
- `nodePublishSecretRef`：对包含敏感信息的 secret 对象的引用，以传递给 CSI 驱动来完成 CSI ``NodePublishVolume` 调用。
|
||||
此字段是可选的，如果不需要 secret，则可能是空的。
|
||||
如果 secret 对象包含多个 secret，则传递所有 secret。
|
||||
@@ -2308,9 +2308,9 @@ Its values are:
|
||||
[Linux kernel documentation](https://www.kernel.org/doc/Documentation/filesystems/sharedsubtree.txt)
|
||||
-->
|
||||
* `HostToContainer` - 此卷挂载将会感知到主机后续针对此卷或其任何子目录的挂载操作。
|
||||
|
||||
|
||||
换句话说，如果主机在此挂载卷中挂载任何内容，容器将能看到它被挂载在那里。
|
||||
|
||||
|
||||
类似的，配置了 `Bidirectional` 挂载传播选项的 Pod 如果在同一卷上挂载了内容，挂载传播设置为 `HostToContainer` 的容器都将能看到这一变化。
|
||||
|
||||
该模式等同于 [Linux 内核文档](https://www.kernel.org/doc/Documentation/filesystems/sharedsubtree.txt) 中描述的 `rslave` 挂载传播选项。
|
||||
|
||||
Reference in New Issue
Block a user