Skip to content

status

The status section is optional and controls the content of the Markdown README generated by imglife status.

status:
client_zone: |
## Team information
This report is updated daily by the platform-images pipeline.
Last manual review: 2026-04-01.
Contact [#platform-images](slack://...) for questions.
FieldTypeRequiredDescription
client_zonestringnoFree-form Markdown block appended at the end of the generated README

The client_zone is a freeform Markdown block injected at the end of the generated status report. Use it to add:

  • Team contact information
  • Pipeline schedule information
  • Links to dashboards or runbooks
  • Any other contextual notes
status:
client_zone: |
---
## About this report
Generated by [imglife](https://gitlab.com/imglife-project/imglife).
Pipeline runs daily at 06:00 UTC — see [base-images CI](https://gitlab.example.com/platform/base-images).
For questions, contact the **Platform Team** in `#platform-images`.

The block supports standard Markdown: headings, links, tables, code blocks, etc.

The status report produced by imglife status contains:

  1. Table of contents (auto-generated)
  2. Mirror images table — Tier 1 images synced from upstream
  3. Base images table — Tier 2 images built by your organisation
  4. Applicative images table — Tier 3 images registered by app teams
  5. Legend — emoji key for status indicators
  6. client_zone — your custom block (if configured)

Example table:

## Base images
| Image | Tag | Platforms | EOL | Status |
| ------ | --------------------------- | ------------ | ---------- | ------ |
| alpine | 3.21.3-core1.0.0 | amd64, arm64 | 2026-11-01 | ✅ |
| golang | 1.22.3-alpine3.21-core1.0.0 | amd64 | 2026-02-01 | ⚠️ |

Status indicators:

IconMeaning
OK
⚠️EOL within alert threshold (default: 30 days)
EOL expired
Terminal window
imglife status --output README.md

The output file is suitable for committing directly to a GitLab/Gitea repository where it renders in the web UI.