Known Issues in DataCore Puls8 v4.3

Default etcd Image Repository Override

The default etcd image repository configured in the Replicated PV Mayastor chart points to an incorrect location. This may cause installation failures or prevent Replicated PV Mayastor components from starting.

Workaround: Override the etcd repository during DataCore Puls8 installation:

--set openebs.mayastor.etcd.image.repository=openebs/etcd

Velero Uninstall Removes DataCore Puls8 Namespace and Components

When Velero is enabled via kubectl puls8, using the velero uninstall -n puls8 command is not recommended. This command attempts to delete the entire Puls8 namespace, expecting it to be used exclusively by Velero, and removes all Puls8 components.

Workaround: Instead of using the Velero CLI uninstall command, run the following command to safely remove only Velero-specific components:

kubectl puls8 velero uninstall --release-name puls8 --chart-name oci://registry-1.docker.io/datacoresoftware/puls8 -n puls8

Backup Hangs When Namespace Contains Replicated Volumes and Local Volumes

When backing up a namespace with a mix of Replicated PV Mayastor and Local PV Hostpath / Local PV LVM volumes, the Velero backup job includes all PVCs. Since Local PV LVM does not support CSI snapshot restore end-to-end, the backup may remain in the WaitForPluginAction state.

Workaround: Avoid creating Local PV Hostpath / Local PV LVM PVCs in the same namespace as Replicated PV Mayastor volumes. Alternatively, use a label selector during backup (Example: --selector backup=true) to limit the backup to specific resources.