Set Up Rok Storage Class

This section will guide you through setting Rok storage class as your default storage class.

Important

If you set Rok as your default storage class, applications that request a PVC without specifying the storage class will run on Rok. In case of node failure, you will lose the Rok PVC. Rok will restore the Rok PVC from the latest snapshot, if one exists. However, the restored PVC will not contain data written to it after the latest snapshot. This may or may not be a problem, depending on your application’s replication policy, and its ability to recover a node quickly from a previous snapshot of the data, or after complete loss of a volume.

This part is optional. If you do not wish to set Rok as your default storage class you may proceed to the What’s Next section.

Procedure

  1. Modify the default storage class. Choose one of the following options, based on your cloud provider:

    root@rok-tools:~# kubectl annotate storageclass gp2 --overwrite \
    >         storageclass.kubernetes.io/is-default-class=false
    
    root@rok-tools:~# kubectl annotate storageclass default --overwrite \
    >         storageclass.kubernetes.io/is-default-class=false
    
    root@rok-tools:~# kubectl annotate storageclass standard --overwrite \
    >         storageclass.kubernetes.io/is-default-class=false
    
  2. Set Rok storage class as the default:

    root@rok-tools:~# kubectl annotate storageclass rok \
    >         storageclass.kubernetes.io/is-default-class=true
    root@rok-tools:~# kubectl annotate volumesnapshotclass rok \
    >         snapshot.storage.kubernetes.io/is-default-class=true
    

Summary

You have successfully set Rok storage class as your default storage class.

What’s Next

The next step is to deploy Arrikto Enterprise Kubeflow.