Manila CSI Operator

Learn about configurations >

• default-storage-class | boolean

  When true, annotates the Manila StorageClass as the cluster-wide default (storageclass.kubernetes.io/is-default-class: "true"). Only one StorageClass should be the default in a cluster.

• kubelet-dir | string

  Default: /var/lib/kubelet

  Absolute path to the kubelet working directory on worker nodes. Manila CSI's node plugin forwards CSI volume operations to the NFS CSI node plugin's UNIX socket, which the NFS CSI driver places at "<kubelet-dir>/plugins/csi-nfsplugin/csi.sock". This option must match the value configured on the csi-driver-nfs charm so the two plugins can find each other.

  The default "/var/lib/kubelet" matches stock Kubernetes and Charmed Kubernetes deployments. Distributions that relocate the kubelet root must override it: for MicroK8s use "/var/snap/microk8s/common/var/lib/kubelet", for k0s use "/var/lib/k0s/kubelet", and so on. Changing this option triggers a Helm upgrade of the Manila CSI release.

• manila-share-type | string

  Default: cephfsnfstype

  Name of the OpenStack Manila share type used when this StorageClass provisions a new share. A Manila share type is an admin-defined template on the OpenStack side that selects which storage backend handles the share (CephFS, NetApp, generic LVM, ...) and applies extra-spec settings such as snapshot support, replication and availability-zone pinning.

  Share type names are arbitrary strings chosen by the OpenStack operator when Manila is deployed; common examples are "cephfsnfstype", "cephfs-nfs", "default", or "generic". Run openstack share type list against the target cloud to discover valid values.

  When left empty (the default), the share type parameter is omitted from the StorageClass and Manila falls back to the deployment's configured default share type (default_share_type in manila.conf). Set this option only if the target Manila deployment has no default share type, or if you need to pin provisioning to a specific non-default backend.

• reclaim-policy | string

  Default: Retain

  PersistentVolume reclaim policy for the Manila StorageClass. "Retain" keeps the underlying Manila share after a PVC is deleted. "Delete" removes the Manila share when the PVC is deleted.

• uninstall-helm-on-remove | boolean

  When true, remove the helm snap from the unit when the charm is removed. Set to false (default) when other co-located charms on the same machine also depend on the helm snap.