阅读中文版本

Environment Teardown Automation Workflow

Automate the removal of unused environments and resources so cost and risk do not accumulate from forgotten infrastructure.

Overview

Ensure unused environments and resources are removed automatically.

This workflow is reusable across teams and environments; adapt the commands to your tooling while keeping the sequence and checkpoints intact.

Environment and prerequisites

• Resource inventory
• Ownership metadata
• A teardown mechanism

Procedure

1. Detect unused environments

Identify environments with no recent activity and no declared owner.

Expected state: Idle resources are visible.

2. Notify owners before removal

Give owners notice and a chance to declare the environment needed.

Expected state: Owners can save legitimate environments.

3. Tear down on a schedule

Remove environments that remain unused after the notice period.

Expected state: Idle infrastructure is removed.

4. Report the savings and risk reduction

Track removed resources and the cost and exposure reduced.

Expected state: Teardown value is visible.

# find idle preview environments
kubectl get ns -l env=preview -o json | jq -r '.items[] | select(.metadata.creationTimestamp)'

Verification

Confirm idle environments are removed after notice and that recent savings are reported.

Decision points

Delete automatically or require approval?

• Delete after notice for non-prod
• Require approval always

Recommendation: Auto-delete idle non-production after notice; require approval for production.

How long is idle?

• Match cost and rebuild time
• A fixed short window

Recommendation: Set the idle window from rebuild cost versus savings.

Common failures

• Forgotten environments cost money and add attack surface.
• Deleting without notice disrupts work.
• No reporting hides the value of cleanup.