text stringlengths 0 59.1k |
|---|
Name: pvc-83295256-f8e0-11e6-8263-005056b2349c |
Labels: <none> |
StorageClass: fast |
Status: Bound |
Claim: default/pvcsc001 |
Reclaim Policy: Delete |
Access Modes: RWO |
Capacity: 2Gi |
Message: |
Source: |
Type: vSphereVolume (a Persistent Disk resource in vSphere) |
VolumePath: [datastore1] kubevols/kubernetes-dynamic-pvc-83295256-f8e0-11e6-8263-005056b2349c.vmdk |
FSType: ext3 |
No events. |
``` |
__Note: VMDK is created inside ```kubevols``` folder in datastore which is mentioned in 'vsphere' cloudprovider configuration. |
The cloudprovider config is created during setup of Kubernetes cluster on vSphere.__ |
3. Create Pod which uses Persistent Volume Claim with storage class. |
See example: |
```yaml |
apiVersion: v1 |
kind: Pod |
metadata: |
name: pvpod |
spec: |
containers: |
- name: test-container |
image: registry.k8s.io/test-webserver |
volumeMounts: |
- name: test-volume |
mountPath: /test-vmdk |
volumes: |
- name: test-volume |
persistentVolumeClaim: |
claimName: pvcsc001 |
``` |
[Download example](vsphere-volume-pvcscpod.yaml?raw=true) |
Creating the pod: |
``` bash |
$ kubectl create -f examples/volumes/vsphere/vsphere-volume-pvcscpod.yaml |
``` |
Verifying pod is created: |
``` bash |
$ kubectl get pod pvpod |
NAME READY STATUS RESTARTS AGE |
pvpod 1/1 Running 0 48m |
``` |
### Storage Policy Management inside kubernetes |
#### Using existing vCenter SPBM policy |
Admins can use the existing vCenter Storage Policy Based Management (SPBM) policy to configure a persistent volume with the SPBM policy. |
__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/v1 |
metadata: |
name: fast |
provisioner: kubernetes.io/vsphere-volume |
parameters: |
diskformat: zeroedthick |
storagePolicyName: gold |
``` |
[Download example](vsphere-volume-spbm-policy.yaml?raw=true) |
The admin specifies the SPBM policy - "gold" as part of storage class definition for dynamic volume provisioning. When a PVC is created, the persistent volume will be provisioned on a compatible datastore with maximum free space that satisfies the "gold" storage policy requirements. |
Example 2: |
```yaml |
kind: StorageClass |
apiVersion: storage.k8s.io/v1 |
metadata: |
name: fast |
provisioner: kubernetes.io/vsphere-volume |
parameters: |
diskformat: zeroedthick |
storagePolicyName: gold |
datastore: VSANDatastore |
``` |
[Download example](vsphere-volume-spbm-policy-with-datastore.yaml?raw=true) |
The admin can also specify a custom datastore where he wants the volume to be provisioned along with the SPBM policy name. When a PVC is created, the vSphere Cloud Provider checks if the user specified datastore satisfies the "gold" storage policy requirements. If yes, it will provision the persistent volume on u... |
#### Virtual SAN policy support inside Kubernetes |
Vsphere Infrastructure(VI) Admins will have the ability to specify custom Virtual SAN Storage Capabilities during dynamic volume provisioning. You can now define storage requirements, such as performance and availability, in the form of storage capabilities during dynamic volume provisioning. The storage capability r... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.