Configuration file dv.yaml

The dv.yaml file is a file used to define DataVolumes which are responsible for managing persistent storage associated with a Pod or VM. Data Volume functions to manage how data is stored and read by applications in the Kubernetes cluster. In the terminal/command prompt that you are using, run the syntax according to the operating system that your computer is using.

1. Windows operating system.

If the Windows operating system is used, you can use notepad++, or the text editor your computer uses.

1. Linux operating system.

If the Linux operating system is used then use the following command.

vim

vim dv.yaml

nano

nano dv.yaml

Add source code for the dv.yaml file.

apiVersion: cdi.kubevirt.io/v1beta1
kind: DataVolume
metadata:
  name: database-prod-dv 
  namespace: default 
  annotations:
    cdi.kubevirt.io/storage.bind.immediate.requested: "True"
spec:
  source:
    registry:
      url: docker://docker.io/shakir31/kubevirt-images:UBUNTU_22.04
  storage:
    storageClassName: storage-nvme-c1
    accessModes:
      - ReadWriteMany
    resources:
      requests:
        storage: 500Gi

The following is an explanation of the source code that will be used, so that it adapts to your needs.

Metadata

In the source code section, in the metadata section, there are names, namespaces and annotations. The name and namespace are the identities used to label the volume data that will be used, while the annotations are used to ensure that the Persistent Volume (PV) is immediately created and bound to the PVC as soon as the volume is requested without waiting for the Pod to start.

Adjust the name to the name of the data volume used, while in the namespace section adjust it to the namespace in the vcluster used in the Deka GPU Portal Service.

Metadata

Specs

In the source code section in the specs section there is source and storage. The source code points to the Docker registry address used to create a VM disk with the Linux operating system, namely Ubuntu 22.04. In the source code storage there is storageClassName, accessModes, and resources.

The storageClassName is used to identify the storage class used, namely storage-nvme-c1, so it is necessary to adjust the storage package selected via the Deka GPU Portal Service. For accessModes, which determines the volume access mode used, namely ReadWriteMany, which allows many Pods or VMs to access the same volume simultaneously. Resources are used to describe the amount of storage that will be used, so you need to adjust the amount of storage used according to the root disk you use in the Deka GPU Portal Service.

Specs

Use this command syntax to save the changes made to the dv.yaml file.

kubectl apply -f dv.yaml