Installing DataCore Puls8

Explore this Page

Overview

This guide outlines the steps to set up the Helm repository, install DataCore Puls8 with default configurations, and apply customizations based on your specific requirements. Helm provides a streamlined method for installing and managing DataCore Puls8 on a Kubernetes cluster.

Before proceeding with the installation, ensure you have met all Prerequisites.

Installing DataCore Puls8 using Helm

To perform an installation of DataCore Puls8:

  1. Install the DataCore Puls8 Helm Chart with the default configuration. The chart is now publicly available via an OCI-compliant registry, you can install it directly using the following command:
    Copy
    Install the DataCore Puls8 Helm Chart
    helm install puls8 -n puls8 --create-namespace oci://docker.io/datacoresoftware/puls8

    This command deploys the following DataCore Puls8 storage components within the puls8 namespace:

    • Local PV Hostpath
    • Local PV LVM
    • Local PV ZFS
    • Replicated PV Mayastor

    You can customize the installation and adjust advanced options:

    • Disabling Storage Engines - By default, DataCore Puls8 Helm chart installs both Local Storage and Replicated Storage are installed. You can disable specific storages by setting the corresponding options to false in your Helm chart configuration values:
      Copy
      Disable Storages
      openebs.engines.replicated.mayastor.enabled: false
      openebs.engines.local.lvm.enabled: false
      openebs.engines.local.zfs.enabled: false

      Adjust these values based on which storage you want to exclude. If not set, all storages will be deployed by default.

      Copy
      Example: Helm Install Without Replicated Storage
      helm install puls8 -n puls8 --create-namespace oci://docker.io/datacoresoftware/puls8 \
        --set openebs.engines.replicated.mayastor.enabled=false
    • If your Kubernetes cluster already contains the CustomResourceDefinitions (CRDs) for CSI VolumeSnapshots, you can skip their creation by adding the following flag:
      Copy
      Flag to Skip CSI VolumeSnapshot CRDs Creation
      --set openebs.openebs-crds.csi.volumeSnapshots.enabled=false
    • Customize Installation Options - Provide custom configuration during installation by using the --set <configuration values> flag or by supplying a custom values file with the -f <file name> option.
  2. Modify the Kubelet Directory (If Required).

For Kubernetes distributions that use a non-standard Kubelet directory, update the directory path during installation by using the --set flag.

Kubelet Directory Paths for Different Storage Types
Copy
For Replicated PV Mayastor
--set openebs.mayastor.csi.node.kubeletDir=<your-directory-path>
Copy
For Local PV LVM
--set openebs.lvm-localpv.lvmNode.kubeletDir=<your-directory-path>
Copy
For Local PV ZFS
--set openebs.zfs-localpv.zfsNode.kubeletDir=<your-directory-path>
Kubelet Directory Paths for Specific Kubernetes Distributions

If you are using any of the following Kubernetes distributions, update the Kubelet directory accordingly:

  • MicroK8s: Change /var/lib/kubelet/ to /var/snap/microk8s/common/var/lib/kubelet/
  • k0s: Change /var/lib/kubelet/ to /var/lib/k0s/kubelet/
  • RancherOS: Change /var/lib/kubelet/ to /opt/rke/var/lib/kubelet/

3. Check the installed Helm chart and review its status. Run the following command to confirm installation and review the chart’s deployment status:

Copy
Command to List Installed Helm Charts
helm ls -n puls8
Copy
Sample Output
NAME     NAMESPACE   REVISION  UPDATED                                   STATUS     CHART           APP VERSION
puls8    puls8       1         2025-05-25 09:13:00.903321318 +0000 UTC   deployed   puls8-4.3.0     4.3.0

Next Steps

With DataCore Puls8 successfully installed, complete the following post-installation steps to ensure a fully functional setup:

Once the installation is verified, proceed with the following actions to get the most value from your deployment:

  • Configure Storage - Set up and validate Local Storage and Replicated Storage configurations.
  • Deploy Workloads - Create Persistent Volume Claims (PVCs) and bind them to applications.

Learn More