text stringlengths 0 59.1k |
|---|
The official [VSAN policy documentation](https://pubs.vmware.com/vsphere-65/index.jsp?topic=%2Fcom.vmware.vsphere.virtualsan.doc%2FGUID-08911FD3-2462-4C1C-AE81-0D4DBC8F7990.html) describes in detail about each of the individual storage capabilities that are supported by VSAN. The user can specify these storage capabi... |
The policy settings can be one or more of the following: |
* *hostFailuresToTolerate*: represents NumberOfFailuresToTolerate |
* *diskStripes*: represents NumberofDiskStripesPerObject |
* *objectSpaceReservation*: represents ObjectSpaceReservation |
* *cacheReservation*: represents FlashReadCacheReservation |
* *iopsLimit*: represents IOPSLimitForObject |
* *forceProvisioning*: represents if volume must be Force Provisioned |
__Note: Here you don't need to create persistent volume it is created for you.__ |
1. Create Storage Class. |
Example 1: |
```yaml |
kind: StorageClass |
apiVersion: storage.k8s.io/v1beta1 |
metadata: |
name: fast |
provisioner: kubernetes.io/vsphere-volume |
parameters: |
diskformat: zeroedthick |
hostFailuresToTolerate: "2" |
cachereservation: "20" |
``` |
[Download example](vsphere-volume-sc-vsancapabilities.yaml?raw=true) |
Here a persistent volume will be created with the Virtual SAN capabilities - hostFailuresToTolerate to 2 and cachereservation is 20% read cache reserved for storage object. Also the persistent volume will be *zeroedthick* disk. |
The official [VSAN policy documentation](https://pubs.vmware.com/vsphere-65/index.jsp?topic=%2Fcom.vmware.vsphere.virtualsan.doc%2FGUID-08911FD3-2462-4C1C-AE81-0D4DBC8F7990.html) describes in detail about each of the individual storage capabilities that are supported by VSAN and can be configured on the virtual d... |
You can also specify the datastore in the Storageclass as shown in example 2. The volume will be created on the datastore specified in the storage class. |
This field is optional. If not specified as shown in example 1, the volume will be created on the datastore specified in the vsphere config file used to initialize the vSphere Cloud Provider. |
Example 2: |
```yaml |
kind: StorageClass |
apiVersion: storage.k8s.io/v1beta1 |
metadata: |
name: fast |
provisioner: kubernetes.io/vsphere-volume |
parameters: |
diskformat: zeroedthick |
datastore: VSANDatastore |
hostFailuresToTolerate: "2" |
cachereservation: "20" |
``` |
[Download example](vsphere-volume-sc-vsancapabilities-with-datastore.yaml?raw=true) |
__Note: If you do not apply a storage policy during dynamic provisioning on a VSAN datastore, it will use a default Virtual SAN policy.__ |
Creating the storageclass: |
``` bash |
$ kubectl create -f examples/volumes/vsphere/vsphere-volume-sc-vsancapabilities.yaml |
``` |
Verifying storage class is created: |
``` bash |
$ kubectl describe storageclass fast |
Name: fast |
Annotations: <none> |
Provisioner: kubernetes.io/vsphere-volume |
Parameters: diskformat=zeroedthick, hostFailuresToTolerate="2", cachereservation="20" |
No events. |
``` |
2. Create Persistent Volume Claim. |
See example: |
```yaml |
kind: PersistentVolumeClaim |
apiVersion: v1 |
metadata: |
name: pvcsc-vsan |
annotations: |
volume.beta.kubernetes.io/storage-class: fast |
spec: |
accessModes: |
- ReadWriteOnce |
resources: |
requests: |
storage: 2Gi |
``` |
[Download example](vsphere-volume-pvcsc.yaml?raw=true) |
Creating the persistent volume claim: |
``` bash |
$ kubectl create -f examples/volumes/vsphere/vsphere-volume-pvcsc.yaml |
``` |
Verifying persistent volume claim is created: |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.