Cheat sheet & self-check

Pick an answer to see if you got it, and why.

1. Q1. In Gitea Actions, what actually executes the jobs?

   1. AGitea itself
   2. Bact_runner, which polls Gitea for jobs and runs them in containers
   3. CThe Git client
   4. DArgo CD
   Show answer

   B. Gitea queues jobs; runners pick them up, just as GitHub-hosted or self-hosted runners do for GitHub.

   From lesson 10 · Hands-on lab: Gitea Actions on your own Kubernetes

2. Q2. Why does the lab's image workflow push only from main?

   1. ARegistries reject branches
   2. BBranches still build and test, but only reviewed, merged code becomes a deployable image (tagged with its commit SHA)
   3. CIt's faster
   4. DGitea requires it
   Show answer

   B. An if: condition on the push step keeps feature branches from publishing images.

   From lesson 10 · Hands-on lab: Gitea Actions on your own Kubernetes

3. Q3. Why is the lab's Docker-in-Docker setup 'lab only'?

   1. AIt's slow
   2. Bdind runs privileged, which gives jobs far more access to the node than production CI should have
   3. CIt doesn't work on k3s
   4. DIt needs a licence
   Show answer

   B. Production runners should build images rootless (BuildKit, Buildah) on isolated, ephemeral runners.

   From lesson 10 · Hands-on lab: Gitea Actions on your own Kubernetes