abrban/cloud-host
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Push Kaniko artifacts via harbor-core for Harbor UI visibility.
Build and Deploy Platform / build-and-deploy (push) Failing after 12m36s
Details

Browse Source 
Add REGISTRY_PUSH_URL config, route CI Kaniko to harbor-core, and document dual-host kaniko auth for core push plus registry base-image pull.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
keyhan
2026-07-11 11:43:05 +03:30
parent ec72ee4fca
commit fec9ec386f
5 changed files with 37 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/build-deploy.yaml
+2 -2
View File
@@ -14,8 +14,8 @@ concurrency:
env:
# PULL_REGISTRY: kubelet pulls via k3s mirror → harbor-core (matches registry-pull-secret)
PULL_REGISTRY: registry.abrban.com
# PUSH_REGISTRY: kaniko pushes directly to harbor-registry (internal, no TLS)
PUSH_REGISTRY: harbor-registry.cloudhost.svc.cluster.local:5000
# PUSH_REGISTRY: kaniko pushes via harbor-core (Harbor UI metadata + blob storage)
PUSH_REGISTRY: harbor-core.cloudhost.svc.cluster.local
PROJECT: abrban
BUILD_NS: cloudhost-builds
GITEA_HOST: gitea-http.gitea.svc.cluster.local:3000