Parent: #739
Depends on: BOM tooling issue (will link once filed)
Summary
Add a user-facing docs page that publishes the full container image inventory for AICR — explicit pins, implicit chart-default images, and the registries spanned.
Motivation
Customers performing security review or planning private-registry mirrors today have to manually render Helm charts to discover what AICR deploys. A published inventory removes that burden and reduces support load.
Proposed content
Add docs/reference/container-images.md (or similar) covering:
- Per-component image table — for each of the 23 components: chart host, chart name, pinned version, runtime image registries, link to upstream chart.
- Explicit vs implicit — explanation of which images are pinned in AICR vs inherited from chart defaults, and the trade-offs (upgrade flow vs reproducibility).
- Registry list — every public registry AICR can pull from, with rationale for each (NGC, ghcr.io, gcr.io, ECR, quay.io, registry.k8s.io, cr.kgateway.dev, Docker Hub).
- How to enumerate yourself — pointer to
make bom once available.
Success criteria
- Page is auto-generated or kept in sync via the BOM tooling (no manual list to drift).
- Linked from
docs/user/component-catalog.md and the security/integrator sections.
- Passes lychee link check.
Parent: #739
Depends on: BOM tooling issue (will link once filed)
Summary
Add a user-facing docs page that publishes the full container image inventory for AICR — explicit pins, implicit chart-default images, and the registries spanned.
Motivation
Customers performing security review or planning private-registry mirrors today have to manually render Helm charts to discover what AICR deploys. A published inventory removes that burden and reduces support load.
Proposed content
Add
docs/reference/container-images.md(or similar) covering:make bomonce available.Success criteria
docs/user/component-catalog.mdand the security/integrator sections.