You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -86,16 +86,11 @@ PersistentVolumeClaimSpec 描述存储设备的常用参数,并支持通过 so
86
86
87
87
<!--
88
88
- **resources** (ResourceRequirements)
89
+
89
90
resources represents the minimum resources the volume should have. If RecoverVolumeExpansionFailure feature is enabled users are allowed to specify resource requirements that are lower than previous value but must still be higher than capacity recorded in the status field of the claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#resources
90
91
91
92
<a name="ResourceRequirements"></a>
92
93
*ResourceRequirements describes the compute resource requirements.*
Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
99
94
-->
100
95
-**resources** (ResourceRequirements)
101
96
@@ -106,7 +101,48 @@ PersistentVolumeClaimSpec 描述存储设备的常用参数,并支持通过 so
106
101
107
102
<aname="ResourceRequirements"></a>
108
103
**ResourceRequirements 描述计算资源要求。**
109
-
104
+
105
+
-**resources.claims** ([]ResourceClaim)
106
+
107
+
<!--
108
+
*Set: unique values will be kept during a merge*
109
+
110
+
Claims lists the names of resources, defined in spec.resourceClaims, that are used by this container.
111
+
112
+
This is an alpha field and requires enabling the DynamicResourceAllocation feature gate.
*ResourceClaim references one entry in PodSpec.ResourceClaims.*
127
+
128
+
- **resources.claims.name** (string), required
129
+
130
+
Name must match the name of one entry in pod.spec.resourceClaims of the Pod where this field is used. It makes that resource available inside a container.
Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
dataSource field can be used to specify either: * An existing VolumeSnapshot object (snapshot.storage.k8s.io/VolumeSnapshot) * An existing PVC (PersistentVolumeClaim) If the provisioner or an external controller can support the specified data source, it will create a new volume based on the contents of the specified data source. If the AnyVolumeDataSource feature gate is enabled, this field will always have the same contents as the DataSourceRef field.
185
+
dataSource field can be used to specify either: * An existing VolumeSnapshot object (snapshot.storage.k8s.io/VolumeSnapshot) * An existing PVC (PersistentVolumeClaim) If the provisioner or an external controller can support the specified data source, it will create a new volume based on the contents of the specified data source. When the AnyVolumeDataSource feature gate is enabled, dataSource contents will be copied to dataSourceRef, and dataSourceRef contents will be copied to dataSource when dataSourceRef.namespace is not specified. If the namespace is specified, then dataSourceRef will not be copied to dataSource.
dataSourceRef specifies the object from which to populate the volume with data, if a non-empty volume is desired. This may be any local object from a non-empty API group (non core object) or a PersistentVolumeClaim object. When this field is specified, volume binding will only succeed if the type of the specified object matches some installed volume populator or dynamic provisioner. This field will replace the functionality of the DataSource field and as such if both fields are non-empty, they must have the same value. For backwards compatibility, both fields (DataSource and DataSourceRef) will be set to the same value automatically if one of them is empty and the other is non-empty. There are two important differences between DataSource and DataSourceRef: * While DataSource only allows two specific types of objects, DataSourceRef
167
-
allows any non-core object, as well as PersistentVolumeClaim objects.
168
-
* While DataSource ignores disallowed values (dropping them), DataSourceRef
169
-
preserves all values, and generates an error if a disallowed value is
170
-
specified.
171
-
(Beta) Using this field requires the AnyVolumeDataSource feature gate to be enabled.
205
+
dataSourceRef specifies the object from which to populate the volume with data, if a non-empty volume is desired. This may be any object from a non-empty API group (non core object) or a PersistentVolumeClaim object. When this field is specified, volume binding will only succeed if the type of the specified object matches some installed volume populator or dynamic provisioner. This field will replace the functionality of the dataSource field and as such if both fields are non-empty, they must have the same value. For backwards compatibility, when namespace isn't specified in dataSourceRef, both fields (dataSource and dataSourceRef) will be set to the same value automatically if one of them is empty and the other is non-empty. When namespace is specified in dataSourceRef, dataSource isn't set to the same value and must be empty. There are three important differences between dataSource and dataSourceRef:
* While dataSource only allows two specific types of objects, dataSourceRef
220
+
allows any non-core object, as well as PersistentVolumeClaim objects.
221
+
* While dataSource ignores disallowed values (dropping them), dataSourceRef
222
+
preserves all values, and generates an error if a disallowed value is
223
+
specified.
224
+
* While dataSource only allows local objects, dataSourceRef allows objects
225
+
in any namespaces.
226
+
(Beta) Using this field requires the AnyVolumeDataSource feature gate to be enabled. (Alpha) Using the namespace field of dataSourceRef requires the CrossNamespaceVolumeDataSource feature gate to be enabled.
APIGroup is the group for the resource being referenced. If APIGroup is not specified, the specified Kind must be in the core API group. For any other third-party types, APIGroup is required.
259
+
260
+
- **dataSourceRef.namespace** (string)
261
+
262
+
Namespace is the namespace of resource being referenced Note that when a namespace is specified, a gateway.networking.k8s.io/ReferenceGrant object is required in the referent namespace to allow that namespace's owner to accept the reference. See the ReferenceGrant documentation for details. (Alpha) This field requires the CrossNamespaceVolumeDataSource feature gate to be enabled.
263
+
-->
264
+
-**dataSourceRef.apiGroup** (string)
265
+
266
+
apiGroup 是正被引用的资源的组。如果 apiGroup 未被指定,则指定的 kind 必须在核心 API 组中。
0 commit comments