Lab & Completion

What You Will Produce

On your own kind cluster: display names on in staging and then in production, each through a pull request and proven on the users’ path - five sign-ups and a sign-in, with their times. A colleague’s merged change that broke something, found from its symptoms, proven and fixed through Git. A decision on your AI agent’s proposal, with its reason. Another team’s manifest, judged without this platform’s checks. And docs/handover.md in your repository - with make capstone-check proving criteria 1-7, and the evidence for 8-10 in the handover itself.

Before You Start

The baseline from Chapter 00 must be clean:

flux --context kind-sre-control-plane get kustomizations -A          # every row READY=True and SUSPENDED=False
kubectl --context kind-sre-control-plane get pods -A --no-headers | grep -vE 'Running|Completed'   # prints nothing
make smoke-test                     # 9/9

You need gh (signed in), jq and yq, Chapters 16-22 done, and an afternoon: three to four hours, most of it yours to plan.

Your fork must be newer than this chapter - make capstone-fault and make capstone-check come with it. Open your fork on GitHub, click Sync fork → Update branch, then git switch main && git pull. Check that it has them before you start - make help | grep capstone lists both targets; if it lists none, the sync did not reach your main.

The Lab in Three Parts

  • A. Verify - the baseline, the times of the users’ path before anything changes, and the colleague’s pull request.
  • B. The Change - staging, then production, each proven; whatever breaks on the way; the AI agent’s proposal. Goals only - no commands.
  • C. Hand Over - the handover in Git, make capstone-check, the baseline.

Open the lab →

Done When

  • A3’s times were written down before A4 ran
  • display names are on in staging and in production, each through its own merged pull request - staging’s first (B1-B4)
  • the users’ path is proven in both environments: five sign-ups with a display name and a sign-in that returns it, each under a second (B2, B4)
  • the colleague’s change is found, its cause proven by its symptom, and fixed through Git (B5)
  • the AI agent’s proposal is decided, with a reason (B3)
  • another team’s manifest is judged in the handover: what can break, what you would check first, the smallest first change (C1)
  • docs/handover.md is on main, and make capstone-check prints 7 of 7 proven. - criteria 1-7; 8-10 are the handover’s evidence (C1-C2)
  • every criterion is graded in the handover - proven, with a hint (which), or not proven yet