AICR build/CI registry egress
AICR build/CI registry egress
Generated by
tools/registry-inventory— do not edit by hand. Runmake registry-docsto regenerate.
Every package/container registry AICR’s builds and CI reach out to, extracted from the
structured build/CI sources (recipes/registry.yaml, .settings.yaml, .goreleaser.yaml /
.ko.yaml, Dockerfiles, .github Actions, tools/setup-tools). This host-level summary is
the browsable companion to the CODEOWNER-gated allowlist that gates these hosts in CI
(tools/registry-inventory/registry-allowlist.yaml). Transitive chart-rendered image
pulls are inventoried separately in the BOM (docs/user/container-images.md); the full
per-record inventory (image refs, pins, provenance) is produced by make registry-inventory.
Distinct hosts (26)
Not statically gated
These egress surfaces are known but not host-gated — the inventory is a floor, not a ceiling:
- tests/uat/lib/phases.sh (helm-diff plugin + workload images assembled from shell vars)
- kwok/scripts/*.sh (in-cluster registry/gitea/karpenter side-loads)
- pkg/**/*.go Sigstore endpoint constants (fulcio/rekor/tuf/oidc) — see pkg/defaults/sigstore.go
- GitHub workflow inline
image:and docker/login-action registry inputs - tools/setup-tools: best-effort only — URLs built from shell vars are reported as warnings, not records
- GitHub Actions per-OWNER trust: all
uses:collapse to hostgithub-actions, so a new third-party action owner is not gated (only SHA-pinning is enforced, by TestExternalActionsArePinned)