ambacti
Explore workflows

STORAGE CLEANUP REVIEW · Workflow idea

Make room in a shared image library without losing a version you still need.

Review stored image versions, keep the latest 10 tags for each image with the latest tag always preserved, and list older candidates for cleanup. Give an administrator the proposed removals and retention context to verify against deployment and recovery needs before any deletion or storage cleanup takes place.

Make it yours See how it works ↓
A Roman aqueduct taking shape from architectural sketch to marble.
A little structure. A clearer outcome.
Starts with
Stored image versions for review
Produces
A proposed cleanup list with retained versions, candidates for removal, and status information for an administrator.
Category
Reviews & approvals

01 / The starting point

A clear request.
A useful direction.

Image names, version tags, and relevant retention information from an organization’s shared image library

“Identify versions outside the agreed retention window, preserve the latest 10 tags and latest tag, and hold deletion and cleanup for administrator approval.”
An example request · Make it specific to your team.

02 / The work

5 tasks.
One useful outcome.

Helps operations teams review accumulated image versions and plan storage cleanup with a clear retention record.

  1. Confirm the image library and owner

    Verify the intended environment, its administrator, and the purpose of the proposed cleanup.

  2. Review version tags and retention

    List image versions and apply the agreed rule to preserve the latest 10 tags for each image, including the latest tag.

  3. Prepare candidates for removal

    Show older versions as proposals and retain enough context for an administrator to check dependencies and recovery needs.

  4. Approve destructive changes

    Require an authorized administrator to approve the exact images and tags before deletion, and confirm any required maintenance window.

  5. Verify cleanup and notify the owner

    After approval, check the resulting inventory and share a clear success, cancellation, or failure update.

03 / The result

Something useful.
Something to build on.

A proposed cleanup list with retained versions, candidates for removal, and status information for an administrator.

AmbactiWorkflow folio · 5 steps

Review container image retention

Reviews & approvals · Example outcome

The handoff

A proposed cleanup list with retained versions, candidates for removal, and status information for an administrator.

Keep in mind

An old-looking version may still support a deployment, rollback, investigation, or recovery. Confirm the latest 10 tags and latest tag are retained, check dependencies and backups, and require an authorized administrator to approve each destructive change and any maintenance activity before it runs.

04 / Make it yours

Set the brief.
Set the standard.

A few choices shape the work around your team.

Choose the environment and image owner

Select the shared image library, identify its administrator, and confirm who may request cleanup.

Set the retention policy

Define how many tags to preserve for each image; the example keeps 10 and always retains the latest tag.

Define approval, backup, and maintenance practices

Specify how administrators check dependencies, recovery copies, maintenance timing, and every proposed deletion.

Test with a non-production example

Review retained and removable tags, cancellation, and failure notifications without deleting production material.

Put your next idea to work.

Start with your brief. Make the process your own.

Explore more workflows ↗