Skip to content

Latest commit

 

History

History
53 lines (44 loc) · 1.9 KB

README.md

File metadata and controls

53 lines (44 loc) · 1.9 KB
Raw

An operator to deploy oVirt's CSI driver

This operator is meant to be installed and controlled by the Cluster Storage Operator

Container Image: https://quay.io/repository/ovirt/csi-driver-operator

This operator will deploy and watch oVirt csi driver components:

  • OvirtCSIOperator - the main operator object
  • StatefulSet of the csi controller
  • DaemonSet of the csi node
  • RBAC objects (ServiceAccount, ClusterRoles, RoleBindings)

Manual Installation

  1. The storage class is created automatically by the operator and the used ovirt storage domain is taken from the installation storage domain for openshift. So if this is not the desired ovirt storage domain (e.g. because for openshift you used storage domain "vmstore" and for the data of openshift workloads you want to use a storage domain named "data"), you have to create the storage class before installing the operator in the following way:
cat << EOF | oc create -f -
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: ovirt-csi-sc
  annotations:
    storageclass.kubernetes.io/is-default-class: "true"
provisioner: csi.ovirt.org
parameters:
  storageDomainName: "YOUR-STORAGE-DOMAIN"
  thinProvisioning: "true"
reclaimPolicy: Delete
allowVolumeExpansion: true
volumeBindingMode: Immediate
EOF
  1. Deploy the operator from manifests/ directory(needs jq tool):
curl -s https://api.github.com/repos/openshift/ovirt-csi-driver-operator/contents/manifests \
 | jq '.[].download_url' \
 | xargs curl -Ls \
 | oc create -f -

Development

  • everyday standard
make build verify
  • create a container image tagged quay.io/ovirt/ovirt-csi-driver-operator:latest
make image
  • To test your modified CSI driver operator on a test cluster follow Docs