Available in:  Ultimate/EE

Included in extensions:  Storage Integration

The module lifecycle stage: Experimental

The module has requirements for installation

How to explicitly enable or disable the module…

You may explicitly enable or disable the module in one of the following ways:

  • Via Deckhouse web UI. In the “System” → “System Management” → “Deckhouse” → “Modules” section, open the csi-mind-ustor module and enable (or disable) the “Module enabled” toggle. Save changes.

    Example:

    Module enable/disable interface

  • Via Deckhouse CLI (d8).

    Use the d8 system module enable command for enabling, or d8 system module disable command for disabling the module (you need Deckhouse CLI (d8), configured to work with the cluster).

    Example of enabling the module:

    d8 system module enable csi-mind-ustor

  • Using ModuleConfig csi-mind-ustor.

    Set spec.enabled to true or false in ModuleConfig csi-mind-ustor (create it if necessary).

    Example of a manifest to enable module csi-mind-ustor:

    apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: csi-mind-ustor
spec:
  enabled: true

How to configure the module…

You can configure the module in one of the following ways:

  • Via Deckhouse web UI.

    In the “System” → “System Management” → “Deckhouse” → “Modules” section, open the csi-mind-ustor module and enable the “Advanced Settings” toggle. Fill in the required fields in the “Configuration” tab or specify the module settings in YAML format on the “YAML” tab, without the top-level settings key. Save the changes.

    Example:

    Module settings interface

    You can also edit the ModuleConfig object csi-mind-ustor on the “YAML” tab in the module settings window (“System” → “System Management” → “Deckhouse” → “Modules”, open the module csi-mind-ustor) by specifying the schema version in the spec.version parameter and the necessary module parameters in the spec.settings section.

  • Via Deckhouse CLI (d8) (requires Deckhouse CLI (d8) configured to work with the cluster).

    Edit the existing ModuleConfig csi-mind-ustor (for more details on configuring Deckhouse Platform, see the documentation) by executing the following command:

    d8 k edit mc csi-mind-ustor

    Make the necessary changes in the spec.settings section. If necessary, specify the schema version in the spec.version parameter. Save the changes.

    You can also create a manifest file for ModuleConfig csi-mind-ustor using the example below. Fill in the spec.settings section with the required module parameters. If necessary, specify the schema version in the spec.version parameter.

    Apply the manifest using the following command (indicate the manifest file name):

    d8 k apply -f <FILENAME>

    Example of a manifest for ModuleConfig csi-mind-ustor:

    apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: csi-mind-ustor
spec:
  version: 1
  enabled: true
  settings: # Module parameters from the "Parameters" section below.

How to change the module release channel…

To change the module release channel, follow the steps in How do I change the release channel for a module?.

Requirements

To the Deckhouse Platform version: 1.72 and above.

Parameters

Schema version: 1

  • settings
    object
    • settings.clusterID
      string

      Identifier of the Kubernetes cluster in the names of uStor images.

      Set it when one uStor installation serves several Kubernetes clusters, so that the images of each cluster are kept apart. Leave it empty when the uStor installation serves one cluster.

      Default: ‘’

    • settings.logLevel
      string
      Log verbosity level of the module components.

      Default: INFO

      Allowed values: ERROR, WARN, INFO, DEBUG, TRACE

    • settings.storageClassLabelIgnoredPrefixes
      array of strings

      Prefixes of label keys that are not copied from a MindUstorStorageClass to its StorageClass.

      The module also skips the labels whose keys start with app.kubernetes.io/managed-by, app.kubernetes.io/instance, kubernetes.io/, k8s.io/ or storage.deckhouse.io/managed-by.

      The default prefixes cover the labels that GitOps tools (Argo CD, Flux, Rancher Fleet) add to resources, so that these tools do not change the labels of a StorageClass that the module manages.

      Default: [ "argocd.argoproj.io/", "kustomize.toolkit.fluxcd.io/", "helm.toolkit.fluxcd.io/", "fleet.cattle.op/" ]