dragonflydb / dragonflydb/dragonfly-operator

Expose the ability to configure persistentVolumeClaimRetentionPolicy

Open
#340 2 comments 1 reaction 0 assignees View on GitHub
enhancement good first issue help wanted
Dominant language
Go
Stars
357
Forks
111
PR merge metrics
No merged PRs in 30d

Description

The DragonflyDB operator leaves around the PVCs when a user deletes the Dragonfly resource. This is because when it deletes the StatefulSet, Kubernetes leaves the PVCs as the persistentVolumeClaimRetentionPolicy field of the StatefulSet defaults to Retain

Can you please expose the ability to set this to Delete on both `whenDeleted` and `whenScaled` ? The default can still be Retain but it would be nice to be able to set it to avoid having to write logic to clean up PVCs.

This functionality used to be behind a feature gate, but it's in GA as of 1.32 so no reason not to expose/support it, its not going anywhere.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.