mirror of
https://github.com/TECHNOFAB11/zfs-localpv.git
synced 2025-12-12 06:20:11 +01:00
chore(doc): adding raw block volume details in README
also added detailed upgrade steps. Signed-off-by: Pawan <pawan@mayadata.io>
This commit is contained in:
parent
654f363b5d
commit
34cc65df00
3 changed files with 117 additions and 4 deletions
74
docs/raw-block-volume.md
Normal file
74
docs/raw-block-volume.md
Normal file
|
|
@ -0,0 +1,74 @@
|
|||
There are some specialized applications that require direct access to a block device because, for example, the file system layer introduces unneeded overhead. The most common case is databases, which prefer to organize their data directly on the underlying storage. Raw block devices are also commonly used by any software which itself implements some kind of storage service (software defined storage systems).
|
||||
|
||||
As it becomes more common to run database software and storage infrastructure software inside of Kubernetes, the need for raw block device support in Kubernetes becomes more important.
|
||||
|
||||
To provisione the Raw Block volume, we should create a storageclass without any fstype as Raw block volume does not have any fstype.
|
||||
|
||||
```yaml
|
||||
apiVersion: storage.k8s.io/v1
|
||||
kind: StorageClass
|
||||
metadata:
|
||||
name: zfspv-block
|
||||
allowVolumeExpansion: true
|
||||
parameters:
|
||||
poolname: "zfspv-pool"
|
||||
provisioner: zfs.csi.openebs.io
|
||||
```
|
||||
|
||||
Now we can create a pvc with volumeMode as Block to request for a Raw Block Volume :-
|
||||
|
||||
```yaml
|
||||
kind: PersistentVolumeClaim
|
||||
apiVersion: v1
|
||||
metadata:
|
||||
name: block-claim
|
||||
spec:
|
||||
volumeMode: Block
|
||||
storageClassName: zfspv-block
|
||||
accessModes:
|
||||
- ReadWriteOnce
|
||||
resources:
|
||||
requests:
|
||||
storage: 5Gi
|
||||
```
|
||||
|
||||
Now we can deploy the application using the above PVC, the ZFS-LocalPV driver will attach a Raw block device at the given mount path. We can provide the device path using volumeDevices in the application yaml :-
|
||||
|
||||
```yaml
|
||||
apiVersion: apps/v1
|
||||
kind: Deployment
|
||||
metadata:
|
||||
name: fiob
|
||||
spec:
|
||||
replicas: 1
|
||||
selector:
|
||||
matchLabels:
|
||||
name: fiob
|
||||
template:
|
||||
metadata:
|
||||
labels:
|
||||
name: fiob
|
||||
spec:
|
||||
containers:
|
||||
- resources:
|
||||
name: perfrunner
|
||||
image: openebs/tests-fio
|
||||
imagePullPolicy: IfNotPresent
|
||||
command: ["/bin/bash"]
|
||||
args: ["-c", "while true ;do sleep 50; done"]
|
||||
volumeDevices:
|
||||
- devicePath: /dev/xvda
|
||||
name: storage
|
||||
volumes:
|
||||
- name: storage
|
||||
persistentVolumeClaim:
|
||||
claimName: block-claim
|
||||
```
|
||||
|
||||
As requested by application, a Raw block volume will be visible to it at the path /dev/xvda inside the pod.
|
||||
|
||||
```
|
||||
volumeDevices:
|
||||
- devicePath: /dev/xvda
|
||||
name: storage
|
||||
```
|
||||
Loading…
Add table
Add a link
Reference in a new issue