【k8s】存储 pvc 参数列表

相关文章：
【K8s】初识PV和PVC
【k8s】存储 pv 参数列表
【k8s】存储 pvc 参数列表

1. pv概述

2. 参数列表

[root@paas-controller-3:/home/ubuntu]$ kubectl explain pvc.spec
KIND:     PersistentVolumeClaim
VERSION:  v1

RESOURCE: spec <Object>

DESCRIPTION:
     Spec defines the desired characteristics of a volume requested by a pod
     author. More info:
     https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims

     PersistentVolumeClaimSpec describes the common attributes of storage
     devices and allows a Source for provider-specific attributes

FIELDS:
   accessModes  <[]string>
     AccessModes contains the desired access modes the volume should have. More
     info:
     https://kubernetes.io/docs/concepts/storage/persistent-volumes#access-modes-1

   dataSource   <Object>
     This 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.

   dataSourceRef        <Object>
     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 allows any non-core object, as
     well as PersistentVolumeClaim objects.
     * While DataSource ignores disallowed values (dropping them), DataSourceRef
     preserves all values, and generates an error if a disallowed value is
     specified. (Alpha) Using this field requires the AnyVolumeDataSource
     feature gate to be enabled.

   resources    <Object>
     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

   selector     <Object>
     A label query over volumes to consider for binding.

   storageClassName     <string>
     Name of the StorageClass required by the claim. More info:
     https://kubernetes.io/docs/concepts/storage/persistent-volumes#class-1

   volumeMode   <string>
     volumeMode defines what type of volume is required by the claim. Value of
     Filesystem is implied when not included in claim spec.

   volumeName   <string>
     VolumeName is the binding reference to the PersistentVolume backing this
     claim.

• selector
  通过该标签，选定符合条件的pv
  注意：pvc没有亲和性参数