From 80aa1e0dc512efcd3ed875fb43552e5244b62edd Mon Sep 17 00:00:00 2001 From: Arsolitt Date: Tue, 28 Apr 2026 17:02:14 +0300 Subject: [PATCH] docs(mongodb): clarify secret cleanup on uninstall Distinguish between operator-managed secrets reclaimed via the finalizer flow (e.g. internal-*-users) and Helm-managed secrets (credentials, user secrets, s3 backup creds) removed by helm uninstall. The previous wording was ambiguous and could mislead users about which cleanup path applies to which secret. Signed-off-by: Arsolitt --- packages/apps/mongodb/README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/packages/apps/mongodb/README.md b/packages/apps/mongodb/README.md index 4b67f4948..f746edaa5 100644 --- a/packages/apps/mongodb/README.md +++ b/packages/apps/mongodb/README.md @@ -37,10 +37,11 @@ Run `helm upgrade` after MongoDB is ready to populate the credentials secret wit ### Data lifecycle -When the MongoDB release is uninstalled, the operator reclaims: +When the MongoDB release is uninstalled, all storage and credentials are reclaimed: - All PVCs backing the replica set storage (via the `percona.com/delete-psmdb-pvc` finalizer on the `PerconaServerMongoDB` CR). -- Operator-managed user secrets associated with the cluster. +- Internal operator-managed secrets (e.g. `internal--users`) are deleted as part of the same finalizer flow. +- Helm-managed secrets (`-credentials`, `-user-*`, `-s3-creds`) are removed by the standard `helm uninstall`. If you need to retain data, take a backup before deletion. Refer to the [Percona Operator for MongoDB documentation](https://docs.percona.com/percona-operator-for-mongodb/) for backup/restore workflows.