Remove Tailscale + K3s deploy from GitHub Actions #20

Open
opened 2026-05-28 00:01:46 +00:00 by coilysiren · 0 comments
Owner

Problem

.github/workflows/build-and-publish.yml runs a deploy job that joins the tailnet via Tailscale OIDC and shells k3s ctr / kubectl into kai-server. GitHub Actions should no longer touch K3s or the tailnet in any circumstance — pull-side update already covers redeploys.

Proposal

  • Delete the deploy job entirely (Tailscale join, image sideload, rollout).
  • The same job's report status to datastore step also POSTs to the tailnet-internal api host; it goes with the rest of the job. A public-endpoint replacement (or removal) is out of scope for this issue — file separately if still wanted.
  • Keep the test job.
  • After merge, Kai unsets the repo's TS_CLIENT_ID / TS_AUDIENCE (and DATASTORE_TOKEN if no longer needed) and removes the federated identity entry from coilysiren/infrastructure/terraform/tailscale-oidc/.
  • The AGENTS.md "Post-push follow-up" section and infrastructure/docs/k3s-deploy-notes.md references to this workflow may need a follow-up edit.

Acceptance

  • Workflow has no Tailscale, K3s, or tailnet-internal HTTP steps.
  • test job still runs on every push to main.
**Problem** `.github/workflows/build-and-publish.yml` runs a `deploy` job that joins the tailnet via Tailscale OIDC and shells `k3s ctr` / `kubectl` into kai-server. GitHub Actions should no longer touch K3s or the tailnet in any circumstance — pull-side update already covers redeploys. **Proposal** - Delete the `deploy` job entirely (Tailscale join, image sideload, rollout). - The same job's `report status to datastore` step also POSTs to the tailnet-internal `api` host; it goes with the rest of the job. A public-endpoint replacement (or removal) is out of scope for this issue — file separately if still wanted. - Keep the `test` job. - After merge, Kai unsets the repo's `TS_CLIENT_ID` / `TS_AUDIENCE` (and `DATASTORE_TOKEN` if no longer needed) and removes the federated identity entry from `coilysiren/infrastructure/terraform/tailscale-oidc/`. - The AGENTS.md "Post-push follow-up" section and `infrastructure/docs/k3s-deploy-notes.md` references to this workflow may need a follow-up edit. **Acceptance** - Workflow has no Tailscale, K3s, or tailnet-internal HTTP steps. - `test` job still runs on every push to `main`.
Sign in to join this conversation.
No labels
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/backend#20
No description provided.