Push to apps-registry, the project that exists on this Harbor
The homelab pushes to a project called "homelab"; this cluster's is apps-registry. Harbor rejects a push to a missing project with "unauthorized: project homelab not found" — the word unauthorized sends you looking at the robot account, when the credentials were never the problem. Only the harbor_project default changes. The com/homelab and org/homelab paths in this repo are the library's own package and resource paths and have nothing to do with the registry; renaming those would break the library. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LEsTefWWifp4ikvhHF5s6N
This commit is contained in:
co-authored by
Claude Opus 5
parent
3e09eecbfe
commit
a9119d7b8e
@@ -23,7 +23,12 @@
|
||||
def call(Map config) {
|
||||
config.service_name = config.service_name ?: config.repo_name
|
||||
config.argo_app_name = config.argo_app_name ?: config.repo_name
|
||||
config.harbor_project = config.harbor_project ?: 'homelab'
|
||||
// The Harbor project images are pushed to. Named apps-registry on this
|
||||
// cluster, not the homelab's "homelab" — the project has to already
|
||||
// exist, and Harbor rejects a push to a missing one with
|
||||
// "unauthorized: project <name> not found", which reads like a
|
||||
// credentials problem rather than a missing project.
|
||||
config.harbor_project = config.harbor_project ?: 'apps-registry'
|
||||
// Cluster DNS, not the ingress hostname: this clone happens from a build
|
||||
// pod, so it is pod-to-pod traffic and has no business leaving the
|
||||
// cluster and coming back in through Contour.
|
||||
|
||||
Reference in New Issue
Block a user