fix: Kaniko insecure-registry for Harbor (#193) #175

Merged

forgejo_admin merged 1 commit from 193-kaniko-insecure-registry into main

2026-03-27 03:16:20 +00:00

forgejo_admin commented

2026-03-27 03:03:36 +00:00

Owner

Summary

Kaniko probes HTTPS on port 443 before falling back to HTTP, causing a 90-second timeout against Harbor's HTTP-only in-cluster service. Adding insecure-registry tells Kaniko to skip the HTTPS probe and use HTTP directly.

Changes

.woodpecker.yaml: Added insecure-registry: harbor.harbor.svc.cluster.local to the build-and-push step settings, alongside the existing insecure: true

Test Plan

CI pipeline on this branch completes build-and-push without 90s HTTPS probe delay
Merge to main and verify full push-to-Harbor pipeline succeeds
No regressions in test step

Review Checklist

Passed automated review-fix loop
No secrets committed
No unnecessary file changes
Commit messages are descriptive

Closes forgejo_admin/pal-e-platform#193
pal-e-platform — bootstrap repo where the issue lives

## Summary Kaniko probes HTTPS on port 443 before falling back to HTTP, causing a 90-second timeout against Harbor's HTTP-only in-cluster service. Adding `insecure-registry` tells Kaniko to skip the HTTPS probe and use HTTP directly. ## Changes - `.woodpecker.yaml`: Added `insecure-registry: harbor.harbor.svc.cluster.local` to the build-and-push step settings, alongside the existing `insecure: true` ## Test Plan - [ ] CI pipeline on this branch completes build-and-push without 90s HTTPS probe delay - [ ] Merge to main and verify full push-to-Harbor pipeline succeeds - [ ] No regressions in test step ## Review Checklist - [ ] Passed automated review-fix loop - [ ] No secrets committed - [ ] No unnecessary file changes - [ ] Commit messages are descriptive ## Related Notes - Closes forgejo_admin/pal-e-platform#193 - `pal-e-platform` — bootstrap repo where the issue lives

forgejo_admin added 1 commit

2026-03-27 03:03:36 +00:00

fix: add insecure-registry to skip Kaniko HTTPS probe timeout

ci/woodpecker/pr/woodpecker Pipeline was successful

Details

8830157d87

Kaniko probes HTTPS on port 443 before falling back to HTTP, causing 90s
timeout against Harbor's HTTP-only service. The insecure-registry setting
tells Kaniko to use HTTP directly.

Refs: forgejo_admin/pal-e-platform#193

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>