fix(build): default Kaniko and init images to Harbor via Helm values
Build and Deploy Platform / build-and-deploy (push) Successful in 14m57s
Build and Deploy Platform / build-and-deploy (push) Successful in 14m57s
User-app builds no longer pull gcr.io/docker.io directly when build.images is configured in values.yaml, fixing ImagePullBackOff on clusters without upstream registry access. Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
@@ -75,6 +75,11 @@ REGISTRY_PASSWORD=registry_secret
|
||||
# Build
|
||||
BUILD_NAMESPACE=cloudhost-builds
|
||||
BUILD_SERVICE_ACCOUNT=kaniko-builder
|
||||
# Kaniko job images — defaults pull from Harbor proxy-cache when unset.
|
||||
# KANIKO_IMAGE=registry.abrban.com/proxy-gcr/kaniko-project/executor:v1.23.2
|
||||
# BUILD_ALPINE_IMAGE=registry.abrban.com/proxy-dockerhub/library/alpine:3.19
|
||||
# BUILD_ALPINE_GIT_IMAGE=registry.abrban.com/proxy-dockerhub/alpine/git:2.43.0
|
||||
# BASE_IMAGE_REGISTRY=registry.abrban.com/proxy-dockerhub/library
|
||||
|
||||
# Platform
|
||||
# Public URL(s) of the frontend — used for CORS and to derive the platform/preview
|
||||
|
||||
Reference in New Issue
Block a user