138ab7306e
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
Four consecutive Kaniko pushes failed with `dial tcp 208.122.204.172:443: connect: connection refused` while zot and Traefik were both healthy and my laptop reached the same URL fine. Measured from a pod in the same namespace, with the same labels the build Job carries: 14 of 24 requests to https://registry.threesix.ai/v2/ succeeded, and 8 of 8 succeeded against Traefik's ClusterIP with the same SNI. So the flaky leg is pod -> the cluster's own public address, and the build was taking it for both the clone and the push. The Job now carries hostAliases pinning git.threesix.ai and registry.threesix.ai to Traefik's ClusterIP, read from the Service at release time. The image is still named registry.threesix.ai/hush/api:SHA — the route changes, the reference does not, and the kubelet pull path is untouched. No retry loop: a retry would have made a 40% failure rate invisible instead of fixed. docs/DEPLOY.md no longer duplicates the Job YAML. That duplicate is why the push guard drifted onto the wrong remote, and a second copy of a spec nobody runs is worth less than a pointer to the one that runs. |
||
|---|---|---|
| .. | ||
| alerts-check.sh | ||
| format-logs.py | ||
| install-mcp.sh | ||
| logs.sh | ||
| release.sh | ||
| smoke.sh | ||