mirror of
https://github.com/hanzo-ml/katib.git
synced 2026-09-24 00:31:27 +00:00
zeekayandHanzo Dev
c03b78648a
ns kubeflow runs ghcr.io/kubeflow/* images — upstream, and on :latest — even though this fork exists and carries our commits. It runs them because nothing here ever published an alternative: the repo has upstream .github/workflows (which do not run on our estate) and no .hanzo lane at all, so there was no hanzo image to point at. Builds exactly the images the cluster consumes, no more. Building artifacts nothing deploys is how a pipeline rots unnoticed. ⚠️ The hanzo-ml ORG HAS NO ACTIONS SECRETS — hanzoai carries GHCR_USER, GHCR_TOKEN, GH_PAT, OCI_*, KMS_*; hanzo-ml carries none. So this BUILDS unconditionally (which proves the fork still compiles — the thing most worth knowing) and PUSHES only when a token is present, emitting a ::warning:: when it is not. Until the org gets credentials the run is honestly green with "built but not published" in the log, rather than the cluster silently serving upstream forever. To finish: give hanzo-ml GHCR_USER/GHCR_TOKEN (KMS-sourced, per policy), then repoint the ns kubeflow deployments at ghcr.io/hanzoai/<image>:sha-<sha7>. Also note the repo is a PULL MIRROR on the forge, so Actions were off entirely (has_actions=false); enabled now, and the sync interval cut 8h -> 10m so a push is picked up in minutes. Co-authored-by: Hanzo Dev <[email protected]>