Skip to content

fix(ci): install kubectl on deploy-gke runner#26

Merged
kimo-ice merged 1 commit intomainfrom
fix/deploy-gke-install-kubectl
Apr 17, 2026
Merged

fix(ci): install kubectl on deploy-gke runner#26
kimo-ice merged 1 commit intomainfrom
fix/deploy-gke-install-kubectl

Conversation

@ggonzalez94
Copy link
Copy Markdown
Member

@ggonzalez94 ggonzalez94 commented Apr 17, 2026

Summary

  • Every deploy-gke run since PR ci: move workflows to ARC runners #19 (move to arc-runner-set) has been failing at the Verify rollouts step with kubectl: command not found — including the v0.2.0 release on 2026-04-16 (run 24501278705).
  • The helm upgrade succeeds before the failure, so prod rolls forward, but the failure silently skips: rollout verification, external health check, and the paid x402 smoke test.
  • Root cause: google-github-actions/get-gke-credentials@v3 writes a KUBECONFIG but does not install kubectl. The ubuntu-latest image had it pre-installed; the arc-runner-set image does not.
  • Fix: add one step (azure/setup-kubectl@v4) before Get GKE credentials.

The Verify rollouts step calls `kubectl rollout status`, but the
`arc-runner-set` image does not ship kubectl. Every deploy-gke run
since PR #19 (which moved the job from ubuntu-latest to the ARC
runner) has failed at that step with `kubectl: command not found`,
including the v0.2.0 release on 2026-04-16. The helm upgrade itself
succeeded in those runs, so production rolled forward, but every
subsequent step (rollout verification, health check, paid smoke)
was skipped.

Add an explicit `azure/setup-kubectl@v4` step so kubectl is available
for the verification path.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@ggonzalez94 ggonzalez94 requested a review from kimo-ice as a code owner April 17, 2026 00:22
@kimo-ice kimo-ice merged commit 4834008 into main Apr 17, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants