Local PV (device) provisioner leaves a stale BDC in the following case:

• On PVC request, creates a BDC
• If the system doesn't have a matching BD, then PVC request keeps retrying, and so does the NDM operator that keeps retrying
• Now if the user deletes the PVC, then Local PV (device) provisioner doesn't get the trigger to process delete, as there was no PVC.

This causes the stale BDC

FEATURE REQUEST

Implement BDD test using ginkgo and gomega which will provision jiva volume in openebs namespace.
Steps:

1. Create volume ,write some data
2. Create snapshot and
3. Create a clone volume using the snapshot
4. Delete the source volume and clone volume.

Refer openebs/maya#1183 for more details about related to StorageClass changes.

Ref: https://v2.docusaurus.io/docs/migrating-from-v1-to-v2/

FEATURE REQUEST:

• Write unit-test cases for the methods that are newly added or modified in the file: scope/probe/kubernetes/reporter.go.
• The test-cases have to be written in scope/probe/kubernetes/reporter_test.go.
• Ensure that the test cases are not too complicated. Follow the guidelines https://github.com/openebs/openebs/blob/master/contribute/CONTRIBUTING-TO-DEVELOPER-DOC.md

README can be added with various badges like code coverage, go report, license, etc.