Files
cloud-host/gitops/k3s/registries.yaml
T
keyhan ec72ee4fca Fix app image pulls and Harbor kubelet auth for user workloads.
Route k3s registry mirrors through harbor-core ClusterIP with hostname-only auth keys, use HTTP EXT_ENDPOINT so OAuth tokens work on port 80, extend deploy readiness timeout, and harden Kaniko build/dockerfile fallbacks.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-10 18:38:05 +03:30

18 lines
675 B
YAML

# k3s containerd registry config — apply on each node at /etc/rancher/k3s/registries.yaml
# Proxy-cache only works through harbor-core (not harbor-registry or Traefik /v2/ alone).
#
# Apply: ./scripts/apply-k3s-registries.sh
# Harbor EXT_ENDPOINT should be http://registry.abrban.com so OAuth realm uses HTTP
# (kubelet mirror hits harbor-core on :80; https://<clusterIP>:443 times out).
mirrors:
registry.abrban.com:
endpoint:
- http://harbor-core.cloudhost.svc.cluster.local # use ClusterIP on single-node (see script)
configs:
registry.abrban.com:
auth:
username: harbor_registry_user
password: REPLACE_WITH_REGISTRY_CREDENTIAL_PASSWORD