liquidmetal-dev / liquidmetal-dev/flintlock
Resource cleanup ADR
Open
Nobody has claimed this yet.
adr-required
area/reconciliation
kind/documentation
lifecycle/stale
priority/important-longterm
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 73
- Avg merge
- 17h 24m
- Merged PRs (30d)
- 30
Description
We need to decide how we handle unused images, network interfaces.
When a microvm is deleted the snapshots will be deleted. This may leave a container image unused. What should we do with these unused images? A couple of options:
1. Do nothing
2. Delete them after X days
3. Delete them as soon as they become unused.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the microVM deletion lifecycle and how snapshots, container images, and network interfaces are handled; done means recording a decided cleanup policy in the resource-cleanup ADR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100