admin/cozystack
1
0 Fork 0
mirror of https://github.com/cozystack/cozystack.git synced 2026-11-08 21:14:56 +09:00
Code Issues Packages Projects Releases Wiki Activity

docs(mongodb): clarify secret cleanup on uninstall

Browse Source 
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 <arsolitt@gmail.com>
This commit is contained in:
Arsolitt committed 2026-04-28 17:01:22 +03:00
1 parent 63239c1617
commit 80aa1e0dc5
1 file changed
+3 -2
Download Patch File Download Diff File Expand all files Collapse all files
packages/apps/mongodb/README.md
+3 -2
View File
@@ -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-<release>-users`) are deleted as part of the same finalizer flow.
- Helm-managed secrets (`<release>-credentials`, `<release>-user-*`, `<release>-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.