text stringlengths 0 59.1k |
|---|
pod-0 1/1 Running 0 33s |
``` |
Or for more detail, use |
``` |
kubectl describe pod pod-0 |
``` |
You can see the attached/mapped volume on the node: |
``` |
$> lsblk |
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT |
... |
scinia 252:0 0 8G 0 disk /var/lib/kubelet/pods/135986c7-dcb7-11e6-9fbf-080027c990a7/volumes/kubernetes.io~scaleio/vol-0 |
``` |
## StorageClass and Dynamic Provisioning |
The ScaleIO volume plugin can also dynamically provision storage to a Kubernetes cluster. |
The ScaleIO dynamic provisioner plugin can be used with a `StorageClass` and is identified as `kubernetes.io/scaleio`. |
### ScaleIO StorageClass |
The ScaleIO dynamic provisioning plugin supports the following StorageClass parameters: |
| Parameter | Description | |
|-----------|-------------| |
| gateway | address to a ScaleIO API gateway (required)| |
| system | the name of the ScaleIO system (required)| |
| protectionDomain| the name of the ScaleIO protection domain (required)| |
| storagePool| the name of the volume storage pool (required)| |
| storageMode| the storage provision mode: `ThinProvisioned` (default) or `ThickProvisioned`| |
| secretRef| reference to the name of a configuered Secret object (required)| |
| readOnly| specifies the access mode to the mounted volume (default `false`)| |
| fsType| the file system to use for the volume (default `ext4`)| |
The following shows an example of ScaleIO `StorageClass` configuration YAML: |
File [sc.yaml](sc.yaml) |
``` |
kind: StorageClass |
apiVersion: storage.k8s.io/v1 |
metadata: |
name: sio-small |
provisioner: kubernetes.io/scaleio |
parameters: |
gateway: https://localhost:443/api |
system: scaleio |
protectionDomain: pd01 |
storagePool: sp01 |
secretRef: sio-secret |
fsType: xfs |
``` |
Note the `metadata:name` attribute of the StorageClass is set to `sio-small` and will be referenced later. Again, remember to update other parameters to reflect your environment setup. |
Next, deploy the storage class file. |
``` |
$> kubectl create -f examples/volumes/scaleio/sc.yaml |
$> kubectl get sc |
NAME TYPE |
sio-small kubernetes.io/scaleio |
``` |
### PVC for the StorageClass |
The next step is to define/deploy a `PersistentVolumeClaim` that will use the StorageClass. |
File [sc-pvc.yaml](sc-pvc.yaml) |
``` |
kind: PersistentVolumeClaim |
apiVersion: v1 |
metadata: |
name: pvc-sio-small |
spec: |
storageClassName: sio-small |
accessModes: |
- ReadWriteOnce |
resources: |
requests: |
storage: 10Gi |
``` |
Note the `spec:storageClassName` entry which specifies the name of the previously defined StorageClass `sio-small` . |
Next, deploy the PVC file. This step will cause the Kubernetes ScaleIO plugin to create the volume in the storage system. |
``` |
$> kubectl create -f examples/volumes/scaleio/sc-pvc.yaml |
``` |
You verify that a new volume created in the ScaleIO dashboard. You can also verify the newly created volume as follows. |
``` |
kubectl get pvc |
NAME STATUS VOLUME CAPACITY ACCESSMODES AGE |
pvc-sio-small Bound k8svol-5fc78518dcae 10Gi RWO 1h |
``` |
###Pod for PVC and SC |
At this point, the volume is created (by the claim) in the storage system. To use it, we must define a pod that references the volume as done in this YAML. |
File [pod-sc-pvc.yaml](pod-sc-pvc.yaml) |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.