Available with limitations in:  Certified Core/CSE Lite (1.73), Certified Pro/CSE Pro (1.73)

Available without limitations in:  Ultimate/EE

Included in extensions:  Storage Integration

The module lifecycle stage: Generally available version

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-hpe 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-hpe

  • Using ModuleConfig csi-hpe.

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

    Example of a manifest to enable module csi-hpe:

    apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: csi-hpe
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-hpe 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-hpe on the “YAML” tab in the module settings window (“System” → “System Management” → “Deckhouse” → “Modules”, open the module csi-hpe) 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-hpe (for more details on configuring Deckhouse Platform, see the documentation) by executing the following command:

    d8 k edit mc csi-hpe

    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-hpe 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-hpe:

    apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: csi-hpe
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.arrayCACertificate
      string

      PEM bundle of the certificate authorities that sign the management API certificates of the HPE arrays (WSAPI of 3PAR, Primera and Alletra 9000; REST API of Nimble and Alletra 5000/6000). When set, the Container Storage Provider verifies the array certificate against it and refuses an array whose certificate is not signed by the bundle.

      When unset, the array certificate is not verified and the provider logs a warning at every login. Applies to both providers: Primera/3PAR (WSAPI) and Nimble/Alletra 5000/6000 (REST API on port 5392).

      Example: 

      arrayCACertificate: |
  -----BEGIN CERTIFICATE-----
  MIIB...
  -----END CERTIFICATE-----
    • settings.logLevel
      string
      The verbosity level of the module’s log output.

      Default: INFO

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

    • settings.nodeSelector
      object
      Specifies where shares can be mounted. Works the same way as the spec.nodeSelector parameter in Kubernetes Pods. If this parameter is omitted, HPE shares can be mounted on any node in the cluster running the Linux OS.

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

    • settings.storageClassLabelIgnoredPrefixes
      array of strings

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

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

      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.op/" ]