Алексей Артамонов ae7c232409 fix(qdrant): anchor PVC ordinal so cleanup never deletes a sibling's data ...

The post-delete hook selected PVCs with an unanchored name prefix
(qdrant-storage-<release>-). Because release names are qdrant-<app>, deleting
release "qdrant-test" matched not only its own PVC
(qdrant-storage-qdrant-test-0) but also a sibling "qdrant-test-2"'s PVC
(qdrant-storage-qdrant-test-2-0) in the same namespace — irreversibly deleting
the sibling's data (or wedging it in Terminating via pvc-protection).

Anchor the ordinal with grep -E "...-[0-9]+$" so only the release's own
data PVCs match. A release name that is a prefix of a sibling no longer
collides.

- cleanup-pvc.yaml: grep -E with anchored "-[0-9]+$".
- tests: assert the anchored selector and add a notMatchRegex guard against
  regressing to the unanchored prefix.
- e2e: gate the post-delete wait on a NotFound result specifically, so a
  transient API/auth error is not misread as "PVC reclaimed".

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Алексей Артамонов <alexeyartamonov1987@gmail.com>

2026-06-30 14:17:14 +03:00

..

certmanager_test.yaml

refactor(qdrant): switch CA and leaf private keys to ECDSA P-256

2026-05-27 11:20:26 +03:00

cleanup_pvc_test.yaml

fix(qdrant): anchor PVC ordinal so cleanup never deletes a sibling's data

2026-06-30 14:17:14 +03:00

qdrant_test.yaml

feat(qdrant): trigger pod restart on TLS Secret rotation via Reloader annotation

2026-05-27 11:20:26 +03:00