Adds the ^oauth2-proxy/ pattern to the quay.io remote so the
artifactapi caching proxy will serve quay.io/oauth2-proxy/oauth2-proxy.
Needed so the arrproxy oauth2-proxy sidecar can pull the real upstream
quay.io address via the rke2 registries.yaml mirror.
Rackspace (syd.mirror.rackspace.com) never synced Fedora 44: it serves
releases/43 but 404s on releases/44/.../repomd.xml, breaking dnf makecache
for F44 through the caching proxy. Repoint to gsl-syd.mm.fcix.net, a
Sydney-local FCIX tier-1 mirror that is fully synced for F44 (releases +
updates + Packages, verified 200, ~25ms), using the standard
/fedora/linux layout root.
The k8up operator (deployed via the k8up-system app) and its restic
backup/prune/check jobs both run ghcr.io/k8up-io/k8up, which the
containerd mirror only serves when the image path is allowlisted.
- Add ^k8up-io/ to the ghcr remote patterns
Adds a valkey helm remote and allowlists the operator/exporter images so the
valkey-operator install in argocd-apps resolves everything through artifactapi.
- Add config/remote_helm/valkey.yaml proxying https://valkey.io/valkey-helm
- Add valkey to the virtual/helm member list
- Allow ^valkey-io/ on the ghcr remote (operator image ghcr.io/valkey-io/valkey-operator)
- Allow ^oliver006/redis_exporter on dockerhub (Valkey metrics exporter)
The k8up backup operator will be installed via ArgoCD, which pulls charts
through the artifactapi virtual helm proxy. That proxy resolves only the
remotes listed as members, so the upstream k8up repo must be registered.
- Add config/remote_helm/k8up.yaml pointing at https://k8up-io.github.io/k8up
- Register k8up as a member of the virtual helm repository
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.