From d0df184af493dd48cf78edd1861d477d058676c1 Mon Sep 17 00:00:00 2001 From: eding Date: Sun, 6 Sep 2026 00:24:52 +0200 Subject: [PATCH] docs: record cluster removal requirements --- docs/operations.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/operations.md b/docs/operations.md index 8eddc6e..986fe20 100644 --- a/docs/operations.md +++ b/docs/operations.md @@ -34,6 +34,22 @@ go run . bootstrap --config --mode=rebuild --yes The rebuild replaces Terraform-managed Talos VMs only. It does not manage or delete TrueNAS datasets or unrelated infrastructure. +## Planned Cluster Removal + +There is currently no `maidn cluster remove` or `maidn uninstall` command. +Do not substitute direct Terraform or Kubernetes deletion for a supported +workflow. A future remove command must require the named-cluster confirmation, +limit its Terraform scope to Maidn Talos VMs, and leave external storage and +shared infrastructure under their respective operator procedures. + +The command must handle partial removal and retry safely: verify each VM's +actual Proxmox state, accept already-absent Maidn VMs, report API timeouts as +incomplete rather than successful removal, and leave a sanitized removal +record in the isolated workspace. It must not delete shared network bridges, +TrueNAS datasets, SOPS identities, or unrelated infrastructure. Until that +command exists, an operator must use the authorized recovery procedure and +resolve Proxmox API failures before retrying bootstrap. + ## OpenBao And Webhooks After a rebuild or an OpenBao restart, refresh Kubernetes auth and reseed the