Installing from Bundled Helm Charts

Installing the Lightbits CSI Plugin

Installing in a Different Namespace

You can install the lb-csi-plugin in a different namespace (ex: lb-csi-ns) by creating a namespace yourself or using the shortcut to let Helm create a namespace for you:

Listing Installed Releases

Uninstalling the Lightbits CSI Plugin

Using A Custom Docker Registry

A custom Docker registry can be used as the source of the container image. Before "helm install" is run, a Secret of type docker-registry should be created with the proper credentials.

The secret has to be created in the same namespace where the workload gets deployed.

The imagePullSecrets Helm value can then be set to the name of the docker-registry Secret to cause the private Docker Registry to be used.

Both lb-csi-controller StatefulSet and lb-csi-node DaemonSet use images that might come from a private registry.

The pod authenticates with the registry using credentials stored in a Kubernetes secret called github-docker-registry, which is specified in spec.imagePullSecrets in the name field.

Custom Docker Registry Example: Github Packages

Github Packages can be used as a custom Docker registry.

First, a Github personal access token must be created. See the instructions for that here.

Second, the access token will be used to create the Secret:

To see how the secret is stored in Kubernetes, you can use this command:

Replace USERNAME with the GitHub username and ACCESSTOKEN with the personal access token.

We can now run "helm install" with the override value for imagePullSecrets. This is often used with an override value for an image so that a specific tag can be selected.