podman: production images do not use the registry mirror #462

Nytt ärende

Öppen

öppnade 2026-09-08 23:04:26 +00:00 av supernaut · 0 kommentarer

supernaut kommenterad

2026-09-08 23:04:26 +00:00

Ägare

podman_registry_mirrors is empty (ansible/roles/podman/defaults/main.yml), so registries-mirrors.conf.j2 is never rendered. registry_mirror_images covers five images consumed only by the CI smoke test. Production pulls go straight to docker.io, and node-exporter, blackbox-exporter and alertmanager pull from quay.io, which the principles document does not list as a touchpoint.

Decide between enabling podman_registry_mirrors for docker.io and quay.io, or repointing each consuming role at the local registry as the renovate role already does. Extend registry_mirror_images to every production image. Update the principles document to name quay.io until it is gone.

`podman_registry_mirrors` is empty (`ansible/roles/podman/defaults/main.yml`), so `registries-mirrors.conf.j2` is never rendered. `registry_mirror_images` covers five images consumed only by the CI smoke test. Production pulls go straight to docker.io, and node-exporter, blackbox-exporter and alertmanager pull from quay.io, which the principles document does not list as a touchpoint. Decide between enabling `podman_registry_mirrors` for docker.io and quay.io, or repointing each consuming role at the local registry as the renovate role already does. Extend `registry_mirror_images` to every production image. Update the principles document to name quay.io until it is gone.

supernaut lade till detta till projektet Bitborg Infrastructure

2026-09-08 23:04:52 +00:00

supernaut lade till etiketterna

2026-09-08 23:05:24 +00:00

Logga in för att delta i denna konversation.