testing on the new images!

README.md

@@ -12,7 +12,7 @@ Builds and pushes a multi-architecture Docker image using a remote Buildx builde
 jobs:
   build:
     name: Build Image
-    runs-on: ubuntu-amd64
+    runs-on: runner-slim-amd64
     steps:
       - uses: actions/checkout@v4
       - uses: https://git.ivanch.me/ivanch/pipeline-actions/build-and-push@main
@@ -60,7 +60,7 @@ Validates a kubeconfig, installs kubectl, and applies Kubernetes manifest(s) tha
 jobs:
   deploy:
     name: Apply Manifests (internal)
-    runs-on: ubuntu-amd64
+    runs-on: runner-slim-amd64
     needs: build
     steps:
       - uses: https://git.ivanch.me/ivanch/pipeline-actions/kubectl-apply@main
@@ -87,7 +87,7 @@ jobs:
 jobs:
   restart:
     name: Rollout Restart (internal)
-    runs-on: ubuntu-amd64
+    runs-on: runner-slim-amd64
     needs: apply
     steps:
       - uses: https://git.ivanch.me/ivanch/pipeline-actions/deploy-restart@main
@@ -109,7 +109,7 @@ SSH into a remote host and run `docker compose pull` + `docker compose up -d --f
 jobs:
   deploy:
     name: SSH Deploy (internal)
-    runs-on: ubuntu-amd64
+    runs-on: runner-slim-amd64
     needs: build
     steps:
       - uses: https://git.ivanch.me/ivanch/pipeline-actions/ssh-deploy@main
@@ -141,6 +141,7 @@ jobs:
 ## Rules
 
 - Every job **must** have a `name:` field (e.g. `name: Build Image`, `name: Deploy (internal)`). Named jobs make the Gitea Actions UI and run logs readable — unnamed jobs show up as the raw job ID (`build`, `deploy`, …). The templates above all include `name:`.
+- Default to `runs-on: runner-slim-amd64` (or `runner-slim-arm64`) as the default runner label. If further development/build binaries are required (or an Ubuntu-based environment is needed), use `runner-full-amd64` (or `runner-full-arm64`).
 - Pin composite action refs to `@main` until version tags are created.
 
 Consumer repositories need these secrets configured in Gitea: