hanzoai/ingress
2
0
Fork 0
mirror of https://github.com/hanzoai/ingress.git synced 2026-10-20 15:07:40 +00:00
Code Issues Packages Projects Releases Wiki Activity

ci: drop the deploy job — kubectl is not in the job image, and CD owns the rollout

Browse Source 
The run went red on a step that has never once succeeded:

    /var/run/act/workflow/0: line 2: kubectl: command not found
    exitcode 127

Jobs run in catthehacker/ubuntu:act-24.04, which carries no kubectl and no
cluster credentials. Meanwhile the work beneath it was green — `test` 8/8,
`docker` and `build-amd64` both successful — so a rollout that could never run
was the only thing failing the pipeline.

It would be wrong even with kubectl present: cd.hanzo.ai reconciles this
DaemonSet from the pin in hanzoai/universe and its selfHeal reverts a CI-side
patch on the next poll. Which tag runs is a reviewed change to that pin; CI ends
at "the image exists and resolves". The same removal was made in
hanzoai/playground and hanzoai/superbase for the same two reasons.

Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in:
zeekay
2026-08-01 23:56:20 -07:00
co-authored by Hanzo Dev
parent 2c76945f3c
commit 3fc4d34868
1 changed files with 15 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/workflows/ci.yml
+15 -10
View File
@@ -87,13 +87,18 @@ jobs:
platforms: "linux/amd64"
secrets: inherit
deploy:
if: github.ref == 'refs/heads/main'
needs: docker
runs-on: [self-hosted, linux, amd64]
environment: production
steps:
- name: Rolling restart ingress DaemonSet
run: |
kubectl rollout restart daemonset/hanzo-ingress -n hanzo
kubectl rollout status daemonset/hanzo-ingress -n hanzo --timeout=120s
# The `deploy` job that used to live here is gone on purpose. It ran
# `kubectl rollout restart daemonset/hanzo-ingress` and failed every time with
#
# /var/run/act/workflow/0: line 2: kubectl: command not found
# exitcode '127'
#
# because jobs run in catthehacker/ubuntu:act-24.04, which has no kubectl and no
# cluster credentials. So the whole run went red on a step that had never once
# succeeded, while the tests and the image build beneath it were green.
#
# It was futile even with kubectl present: cd.hanzo.ai reconciles this DaemonSet
# from the pin in hanzoai/universe, and its selfHeal reverts a CI-side patch on
# the next poll. Rollout is a reviewed tag pin there, never a CI side effect —
# CI's job ends at "the image exists and resolves". Same removal already made in
# hanzoai/playground and hanzoai/superbase for the same two reasons.