This feature is actively developed. It might significantly change in the future.

The module is guaranteed to work only in the following cases:

In all other cases, the module may work, but its full functionality is not guaranteed.

The module is not enabled by default in any bundles.

How to explicitly enable the module…

Note that the configOverrides parameter of the InitConfiguration resource is used when installing Deckhouse, not ModuleConfig.

Set the linstorEnabled: true or linstorEnabled: false in the configOverrides parameter to explicitly enable or disable the module when installing Deckhouse.

Use the linstor section of the configOverrides parameter to configure the module when installing Deckhouse.

Set the spec.enabled module parameter to true or false to explicitly enable or disable the module.

Example of enabling the linstor module:

apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: linstor
spec:
  enabled: true

Example of disabling the linstor module:

apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: linstor
spec:
  enabled: false

The module is configured using the ModuleConfig custom resource named linstor (learn more about setting up Deckhouse…).

Example of the ModuleConfig/linstor resource for configuring the module:

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

Parameters

Schema version: 1

  • dataNodesobject

    Settings for Linstor on nodes with data

    • dataNodes.nodeSelectorobject

      The same as in the Pods spec.nodeSelector parameter in Kubernetes.

      If parameter is omitted, Linstor nodes will be placed on all nodes.

      Caution! Changing this parameter does not result in data redistribution. If node with data no longer matches the nodeSelector, data on that node will become inaccessible.