titan/atlas-iac
3
0
Fork 0
Code Issues Pull Requests 9 Actions Packages Projects Releases Wiki Activity

fix(harbor): mark harbor-core insecure so skopeo pushes over HTTP

Browse Source 
skopeo derived the token realm as HTTPS and got 'HTTP response to HTTPS client'.
A registries.conf with insecure=true for harbor-core:80 makes the registry AND
its token request use HTTP.
This commit is contained in:
jenkins 2026-08-25 14:21:15 -03:00
parent 4f5fc44013
commit e7ac6351a6
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
services/harbor/hermes-agent-base-mirror-job.yaml
View File

@ -108,6 +108,11 @@ spec:
src="docker://nousresearch/hermes-agent@sha256:9c841866021c54c4596849f6135717e8a4d52ba510b7f52c50aef1de1a283973"
dst="docker://harbor-core.harbor.svc.cluster.local:80/mirror/hermes-agent@sha256:9c841866021c54c4596849f6135717e8a4d52ba510b7f52c50aef1de1a283973"
pw="$(cat /vault/secrets/harbor-admin-password)"
# harbor-core serves the registry + token service over plain HTTP on
# :80; mark it insecure so skopeo (and the token request it derives
# from the auth challenge) use HTTP instead of defaulting to HTTPS.
printf '[[registry]]\nlocation = "harbor-core.harbor.svc.cluster.local:80"\ninsecure = true\n' > /tmp/registries.conf
export CONTAINERS_REGISTRIES_CONF=/tmp/registries.conf
exec skopeo copy --all \
--src-tls-verify=true \
--dest-tls-verify=false \