The sds-replicated-volume module: configuration

Requirements

To the Kubernetes version: 1.31 and above.

To the Deckhouse Platform version: 1.72 and above.

To the versions of other modules:

• sds-node-configurator: 0.6.1 and above.

Conversions

The module is configured using the ModuleConfig resource, the schema of which contains a version number. When you apply an old version of the ModuleConfig schema in a cluster, automatic transformations are performed. To manually update the ModuleConfig schema version, the following steps must be completed sequentially for each version:

• Updates from version 1 to 2:

  Need to remove the .enableThinProvisioning parameter.

Parameters

Schema version: 2

• settings

  object
  • settings.backup

    object

    Module backup settings
    • settings.backup.enabled

      boolean

      Module backup state

      Default: true

    • settings.backup.retentionCount

      integer

      Number of backups to keep

      Default: 7

    • settings.backup.schedule

      string

      Backup schedule

      Default: 0 3 * * *

  • settings.dataNodes

    object

    Settings for Linstor on nodes with data

    Default: {}

    • settings.dataNodes.nodeSelector

      object

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

      Nodes that match the selector get the storage.deckhouse.io/sds-replicated-volume-node: "" label. Module components, including the LINSTOR satellite and the CSI node, run on nodes with this label.

      The default value kubernetes.io/os: linux selects all Linux nodes. A custom value replaces the default one and is not merged with it.

      Caution! Set this parameter when enabling the module. If you change it later, including disabling the module and enabling it again with a different selector, the nodes that have already been selected keep the storage.deckhouse.io/sds-replicated-volume-* labels and module components keep running on them. The labels are not removed and the data is not moved to other nodes.

      To remove the module from such a node, follow the FAQ section Example of removing resources from a node without removing the node itself, then remove the labels from the node manually.

      Default: { "kubernetes.io/os": "linux" }

  • settings.drbdPortRange

    object

    Settings for DRBD TCP ports

    Default: {}

    • settings.drbdPortRange.maxPort

      integer

      DRBD ports range end

      Default: 7999

    • settings.drbdPortRange.minPort

      integer

      DRBD ports range start

      Default: 7000

  • settings.logLevel

    string

    Module log level

    Default: INFO

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

  • settings.newControlPlane

    boolean

    When true, use the new control-plane as a backend for the module. Once switched to true, reverting back to false is prohibited.

    Enabling it is only allowed on Deckhouse development builds; on any release channel the setting is rejected and ignored.

    Default: false

  • settings.registryScheme

    string

    Deprecated parameter. Remove it from ModuleConfig for Deckhouse with version greater than 1.57.

    Default: https

  • settings.storageClassLabelIgnoredPrefixes

    array of strings

    List of label-key prefixes that MUST NOT be propagated from a ReplicatedStorageClass to the managed Kubernetes StorageClass.

    The controller treats this list as a complement to a built-in (system) list and drops any ReplicatedStorageClass label whose key starts with any prefix from either list.

    Matching is literal strings.HasPrefix (Go semantics): an entry without a trailing / matches by substring, NOT by full label key. For example, team would drop every key starting with team (team, team-id, team.example.com/...). To restrict matching to a specific subdomain, end the entry with / (e.g. argocd.argoproj.io/). To target an exact label key, write the full key and be aware it also matches keys whose name extends it (e.g. app.kubernetes.io/managed-by also drops app.kubernetes.io/managed-by-foo).

    Note that kubernetes.io/ in the system list matches only labels whose key literally starts with kubernetes.io/; reserved subdomains such as topology.kubernetes.io/zone or node.kubernetes.io/* are NOT covered by default — add them here explicitly if your environment requires it.

    The defaults cover labels typically added by GitOps tooling (Argo CD, Flux, Rancher Fleet) so that their reconcilers do not fight the storage controller over labels on the managed StorageClass.

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