Install SUSE Storage Using Helm

Prerequisites

Kubernetes cluster: Ensure that each node fulfills the installation requirements.
Your workstation: Install Helm v3.0 or later.

This script can be used to check the environment for potential issues.

Installation

Note:

The initial settings can be found in customized using Helm options or by editing the deployment configuration file.

For Kubernetes v1.25 or earlier, if your cluster still enables Pod Security Policy admission controller, set the helm value enablePSP to true to install longhorn-psp PodSecurityPolicy resource which allows privileged Longhorn pods to start.

Add the Longhorn Helm repository:

helm repo add longhorn https://charts.longhorn.io

Fetch the latest charts from the repository:
```
helm repo update
```

Install SUSE Storage in the longhorn-system namespace.

 helm install longhorn longhorn/longhorn --namespace longhorn-system --create-namespace --version 1.7.0

To confirm that the deployment succeeded, run:

 kubectl -n longhorn-system get pod

The result should look like the following:

 NAME                                                READY   STATUS    RESTARTS   AGE
 longhorn-ui-b7c844b49-w25g5                         1/1     Running   0          2m41s
 longhorn-manager-pzgsp                              1/1     Running   0          2m41s
 longhorn-driver-deployer-6bd59c9f76-lqczw           1/1     Running   0          2m41s
 longhorn-csi-plugin-mbwqz                           2/2     Running   0          100s
 csi-snapshotter-588457fcdf-22bqp                    1/1     Running   0          100s
 csi-snapshotter-588457fcdf-2wd6g                    1/1     Running   0          100s
 csi-provisioner-869bdc4b79-mzrwf                    1/1     Running   0          101s
 csi-provisioner-869bdc4b79-klgfm                    1/1     Running   0          101s
 csi-resizer-6d8cf5f99f-fd2ck                        1/1     Running   0          101s
 csi-provisioner-869bdc4b79-j46rx                    1/1     Running   0          101s
 csi-snapshotter-588457fcdf-bvjdt                    1/1     Running   0          100s
 csi-resizer-6d8cf5f99f-68cw7                        1/1     Running   0          101s
 csi-attacher-7bf4b7f996-df8v6                       1/1     Running   0          101s
 csi-attacher-7bf4b7f996-g9cwc                       1/1     Running   0          101s
 csi-attacher-7bf4b7f996-8l9sw                       1/1     Running   0          101s
 csi-resizer-6d8cf5f99f-smdjw                        1/1     Running   0          101s
 instance-manager-b34d5db1fe1e2d52bcfb308be3166cfc   1/1     Running   0          114s
 engine-image-ei-df38d2e5-cv6nc                      1/1     Running   0          114s

To enable access to the UI, you will need to set up an Ingress controller. Authentication to the UI is not enabled by default. For information on creating an NGINX Ingress controller with basic authentication, refer to this section.
Access the UI using these steps.