Guides / Operate
Delete things safely
Read this before you tear down a project or anything large in it. Deletion is permanent. Etorm refuses some deletes that would leave dangling objects, but not all of them, so the order you delete in matters.
Delete in this order
- Delete what runs on a VPC first: load balancers, ingresses, databases and message brokers, and Compute processes (then their programs).
- Delete members next:
kubectl delete account laptop. Then services: DHCP and DNS. Then the VPC. - A VPC cannot be deleted while Accounts reference it (
409). Other things that point at a VPC are not checked: delete them first, or they are left waiting for a VPC that is gone. - Buckets:
kubectl delete bucket NAMEmakes every object unreadable at once. A Database or MessageBroker deletes its own bucket and processes with it. - Delete the project. The platform removes every object in it, then the project itself; this takes a moment.
- Delete the billing account last: it cannot be deleted while a project uses it.
Delete what a diagram built
When you delete a diagram, everything it created goes too, dependents first. To keep the objects, set spec.deletePolicy: Orphan before you delete it. The objects are then released and live on without a diagram.
Revoke access and tokens
Remove the grants and tokens that people and scripts no longer need.
kubectl ... delete apitoken <name> # revokes the token at once kubectl ... delete rolebinding <name> # removes a grant kubectl ... delete invitation <name> # revokes an unused invitation
The last owner of a billing account cannot be removed, so add another owner first.
What deletion does to usage
Usage is metered for objects while they are Ready, and deleting an object stops its metering. To see the month's usage, run kubectl --context etorm get usages. Nothing is invoiced.