Allow logging-stack images through the dockerhub remote #16
Reference in New Issue
Block a user
Delete Branch "benvin/logging-stack-docker-remotes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
The new centralized logging stack in argocd-apps (ClickHouse + Vector + NATS JetStream, PR unkin/argocd-apps#296) pulls all its container images through artifactapi instead of directly from upstream registries. The dockerhub remote is an allowlist (
patterns), so those repositories must be permitted before the images can be cached/served.What
Add to
config/remote_docker/dockerhub.yamlpatterns:^altinity/—altinity/clickhouse-operator,altinity/metrics-exporter(ClickHouse operator chart)^clickhouse/—clickhouse/clickhouse-server(DB pods + schema bootstrap Job)^library/nats—nats(JetStream server)^natsio/—natsio/nats-box(stream bootstrap Job),natsio/nats-server-config-reloader(NATS chart)^timberio/vector—timberio/vector(agent/aggregator/archiver/vm-ingest runtime + thevector testCI image)bitnami/kubectl(operator crdHook) is already covered by the existing^bitnami/.Dependency
Merge-before for unkin/argocd-apps#296 — that PR rewrites its image refs to
artifactapi.k8s.syd1.au.unkin.net/dockerhub/...and will not pull until these patterns are live.https://claude.ai/code/session_015ur3i7D2azsMAWTSVABApv