Add support for HPE Storage using the helm chart provided by HP

What does this MR do and why?

This MR will add a new unit that will allow workload cluster to use HPE Storage class. The unit was tested with HPE Alletra 9000 and the tests was done using Kubevirt and HPE as storage class for VMs.

Related reference(s)

Closes #4110 (closed)

Test coverage

The values provided in the workload cluster are defined bellow:

units:

  hpe-csi-driver-init:
    enabled: true
  hpe-csi-driver:
    enabled: true
  hpe-csi-driver-backends:
    enabled: true
  hpe-csi-storageclasses:
    enabled: true

hpe_storage_csi:
  helm_values:
    disable:
      nimble: true
      primera: true
      alletra6000: true
      alletra9000: false
      alletraStorageMP: true
      b10000FileService: true
    disableNodeConformance: true
    disableHostDeletion: true
    disablePreInstallHooks: false
  hpe_backends:
    my-backend:
      serviceName: alletra9000-csp-svc
      servicePort: "8080"
      backend: 192.168.1.110:443
      username: 3paradm
      password: 3pardata
      snapshot_class_enabled: true
  hpe_storageclasses:
    hpe-gold:
      parameters:
        accessProtocol: fc
        cpg: cpg_ssd_raid6_k8svirtpoc # change
        snapCpg: cpg_ssd_raid6_k8svirtpoc # change
        provisioningType: reduce # change
        csi.storage.k8s.io/fstype: xfs # change
        hostSeesVLUN: "true" # change
        csi.storage.k8s.io/controller-expand-secret-name: my-backend
        csi.storage.k8s.io/controller-expand-secret-namespace: hpe-storage
        csi.storage.k8s.io/controller-publish-secret-name: my-backend
        csi.storage.k8s.io/controller-publish-secret-namespace: hpe-storage
        csi.storage.k8s.io/node-publish-secret-name: my-backend
        csi.storage.k8s.io/node-publish-secret-namespace: hpe-storage
        csi.storage.k8s.io/node-stage-secret-name: my-backend
        csi.storage.k8s.io/node-stage-secret-namespace: hpe-storage
        csi.storage.k8s.io/provisioner-secret-name: my-backend
        csi.storage.k8s.io/provisioner-secret-namespace: hpe-storage
        description: "Volume created by using a custom Secret with the HPE CSI Driver for Kubernetes"

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon	Meaning	Available values
☁️	Infra Provider	capd, capo, capm3
🚀	Bootstrap Provider	kubeadm (alias kadm), rke2, okd, ck8s
🐧	Node OS	ubuntu, suse, na, leapmicro
🛠️	Deployment Options	Deployment option list and description
🎬	Pipeline Scenarios	Available scenario list and description
🟢	Enabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by mgmt: or wkld: to be applied only to a specific cluster type
🔴	Disabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by mgmt: or wkld: to be applied only to a specific cluster type
🏗️	Target platform	Can be used to select specific deployment environment Available platform list and description
⚡	Pipeline control	autorun, manual or blocking. Can be used to override global config and start a deployment pipeline the required way

• 🎬 preview ☁️ capd 🚀 kadm 🐧 ubuntu

• 🎬 preview ☁️ capo 🚀 rke2 🐧 suse

• 🎬 preview ☁️ capm3 🚀 rke2 🐧 ubuntu

• ☁️ capd 🚀 kadm 🛠️ light-deploy 🐧 ubuntu

• ☁️ capd 🚀 rke2 🛠️ light-deploy 🐧 suse

• ☁️ capo 🚀 rke2 🐧 suse

• ☁️ capo 🚀 rke2 🐧 leapmicro

• ☁️ capo 🚀 kadm 🐧 ubuntu

• ☁️ capo 🚀 kadm 🐧 ubuntu 🟢 neuvector,mgmt:harbor

• ☁️ capo 🚀 rke2 🎬 rolling-update 🛠️ ha 🐧 ubuntu

• ☁️ capo 🚀 kadm 🎬 wkld-k8s-upgrade 🐧 ubuntu

• ☁️ capo 🚀 rke2 🎬 rolling-update-no-wkld 🛠️ ha 🐧 suse

• ☁️ capo 🚀 rke2 🎬 sylva-upgrade 🛠️ ha 🐧 ubuntu

• ☁️ capo 🚀 rke2 🎬 sylva-upgrade-from-1.6.x 🛠️ ha,misc 🐧 ubuntu

• ☁️ capo 🚀 rke2 🛠️ ha,misc 🐧 ubuntu

• ☁️ capo 🚀 rke2 🛠️ misc 🐧 ubuntu 🟢 mgmt:harbor 🔴 neuvector

• ☁️ capo 🚀 rke2 🛠️ ha,misc,openbao🐧 suse

• ☁️ capo 🚀 rke2 🐧 suse 🎬 upgrade-from-prev-tag

• ☁️ capm3 🚀 rke2 🐧 suse

• ☁️ capm3 🚀 kadm 🐧 ubuntu

• ☁️ capm3 🚀 ck8s 🐧 ubuntu

• ☁️ capm3 🚀 kadm 🎬 rolling-update-no-wkld 🛠️ ha,misc 🐧 ubuntu

• ☁️ capm3 🚀 rke2 🎬 wkld-k8s-upgrade 🛠️ ha 🐧 suse

• ☁️ capm3 🚀 kadm 🎬 rolling-update 🛠️ ha 🐧 ubuntu

• ☁️ capm3 🚀 rke2 🎬 upgrade-from-prev-release-branch 🛠️ ha 🐧 suse

• ☁️ capm3 🚀 rke2 🛠️ misc,ha 🐧 suse

• ☁️ capm3 🚀 rke2 🎬 sylva-upgrade 🛠️ ha,misc 🐧 suse

• ☁️ capm3 🚀 kadm 🎬 rolling-update 🛠️ ha 🐧 suse

• ☁️ capm3 🚀 ck8s 🎬 rolling-update 🛠️ ha 🐧 ubuntu

• ☁️ capm3 🚀 rke2|okd 🎬 no-update 🐧 ubuntu|na

• ☁️ capm3 🚀 rke2 🐧 suse 🎬 upgrade-from-release-1.5

• ☁️ capm3 🚀 rke2 🐧 suse 🎬 upgrade-to-main

• ☁️ capm3 🚀 rke2🎬 rolling-update-no-wkld 🛠️ ha,misc 🐧 ubuntu 🏗️ real-bmh

• ☁️capm3 🚀rke2 🏗️real-bmh 🎬nightly 🛠️ha 🐧suse

Global config for deployment pipelines

• autorun pipelines
• allow failure on pipelines
• record sylvactl events

Notes:

• Enabling autorun will make deployment pipelines to be run automatically without human interaction
• Disabling allow failure will make deployment pipelines mandatory for pipeline success.
• if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.