From 273d8f90eda6457cb6589ad78092dbcb530f4009 Mon Sep 17 00:00:00 2001 From: ximenchuifeng Date: Wed, 15 Jul 2026 00:43:30 +0800 Subject: [PATCH] docs(gitops): design disabling demo mongodb --- .../2026-07-15-disable-demo-mongodb-design.md | 50 +++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 docs/superpowers/specs/2026-07-15-disable-demo-mongodb-design.md diff --git a/docs/superpowers/specs/2026-07-15-disable-demo-mongodb-design.md b/docs/superpowers/specs/2026-07-15-disable-demo-mongodb-design.md new file mode 100644 index 0000000..a31ce01 --- /dev/null +++ b/docs/superpowers/specs/2026-07-15-disable-demo-mongodb-design.md @@ -0,0 +1,50 @@ +# Disable Demo MongoDB + +## Goal + +Temporarily exclude MongoDB from the default demo infrastructure deployment and remove the existing MongoDB workload and test data from the current demo cluster. + +## Repository Design + +- Remove only the `mongo` item from `sharedDatastores` in `environments/demo/infra-values.yaml`. +- Keep `sharedInfra.mongo` connection settings unchanged so MongoDB can be restored by adding the datastore item back. +- Do not modify the reusable `mixingx-infra` Helm chart. +- Do not modify Redis or RabbitMQ datastore entries. +- Keep the Audit Application disabled under `applications/demo/disabled/audit.yaml`. + +The Infra chart renders one StatefulSet and Service for every `sharedDatastores` item. Removing the demo MongoDB item therefore excludes `mongo-statefulset` and `mongo-service` from newly rendered demo manifests without introducing a new chart-level feature. + +## GitOps Flow + +1. Validate the updated demo values with Helm lint and template rendering. +2. Commit and push the `mixingx.deploy` `master` branch. +3. Update the `mixingx.hub` `mixingx-deploy` submodule pointer on `develop/v.1.0.1` and push it. + +The `mixingx-infra` Argo CD Application does not enable automated synchronization or pruning. Repository changes prevent MongoDB from being included in future default renders, but current cluster resources require an explicit cleanup operation. + +## Current Cluster Cleanup + +Target the demo cluster on `192.168.1.173`, namespace `mixingx`. + +Before deletion, inspect and record the exact MongoDB StatefulSet, Service, PVC, PV, StorageClass, and reclaim policy. Then delete only: + +- StatefulSet `mongo-statefulset` +- Service `mongo-service` +- PVC `data-mongo-statefulset-0` + +The PVC contains test data and does not need to be retained. If its PV reclaim policy is `Delete`, verify that the associated PV and Longhorn volume are removed. If automatic reclamation does not complete, stop and report the remaining storage object before any additional deletion. + +Do not delete the Infra Argo CD Application, Redis, RabbitMQ, their PVCs, or any unrelated Longhorn volume. + +## Verification + +- Helm output contains no `mongo-statefulset` or `mongo-service`. +- Helm output still contains the Redis and RabbitMQ StatefulSets and Services. +- The pushed deploy repository contains the values change and the Hub repository points to that deploy commit. +- The current cluster contains no MongoDB StatefulSet, Service, Pod, or PVC in namespace `mixingx`. +- Redis and RabbitMQ remain ready after cleanup. +- Audit remains excluded from the default demo Application manifests. + +## Restore Procedure + +To restore MongoDB later, re-add the original `mongo` item to `sharedDatastores`, commit and push the deploy repository, update the Hub submodule pointer, and synchronize the Infra Argo CD Application. A new empty PVC will be created because the previous test-data PVC is intentionally deleted.