DevOps Professional · Module 6: Governance, cost and change control
Ownership: From Untagged to Accountable
Unowned resources are decisions nobody made: waste nobody defends, risks nobody patches, incidents nobody leads. Inventory finds them, remediation assigns or deletes them, and admission stops new ones from arriving untagged.
10 min reading
Objectives
- Explain what ownership promises: a named human answers for the resource
- Find untagged and unowned fixtures with inventory queries
- Write the remediation plan: tag, assign, verify, or delete
- Keep ownership fresh with admission defaults and scheduled audits
Why this matters
A third of the lab estate runs workloads nobody claims: old experiments, departed teammates' scaffolds, duplicated fixtures from three migrations. They consume quota, confuse incident response (whose is this), and one of them holds a stale credential with broad rights. Nobody created a problem on purpose; ownership simply had no process, so entropy accumulated owners' absence. The L66 lab remediates fixtures; this lesson makes the remediation a standing practice.
Concepts
Ownership means a named human (or a tiny named group) who answers for the resource: its cost, its patches, its incidents, its deletion. Every resource carries owner, purpose and expiry labels from birth; labels are set at creation by templates and admission defaults, not by later archaeology. Untagged inventory is queried on schedule: no owner, expired purpose, owner departed. Each finding gets one of three verdicts: assign (a human claims it with a purpose), fix-and-keep, or delete with a backup where the data matters.
Remediation runs as a plan, not as a purge. Notify owners with a deadline, default-assign team leads for the ambiguous, quarantine the unclaimed (restricted network, no secrets) before deleting, and keep the deletion log with restore windows for state. Surprise deletions teach teams to hide resources; announced remediation with a path to claim teaches labeling. The fixture remediation quotes each verdict with its evidence.
Freshness beats heroics. Admission defaults require owner labels on create; expiry labels force periodic re-justification; scheduled audits catch drift. The untagged rate is a platform metric on a dashboard, trending down, reviewed alongside cost. Heroes who clean quarterly are celebrated once; the process that prevents the mess ships daily.
Worked example
A fixture estate holds thirty resources, nine unclaimed. The learner queries the untagged, notifies (simulated), assigns four with purposes, quarantines three, deletes two with logged restore windows. The remediation plan records each verdict with evidence, and admission defaults land so the next audit finds fewer.
Common wrong move
Deleting first and asking later. The unclaimed resource that ran the quarterly report nobody documented becomes an incident with no restore path. Quarantine before delete, log everything, restore windows always.
Quick check
An optional 4-question self-check. Answers never leave your device, are not stored, and never count toward any assessment.
Lesson feedback
No published feedback yet.
Log in and complete the lesson to leave feedback.
Exercise
Remediate a fixture estate with untagged resources: query, verdict each (assign, quarantine or delete with restore window), and land admission defaults.
Pass criteria
The record shows the untagged inventory, each verdict with evidence, the deletion log with restore windows, and the admission defaults.