Project challenges / verified progress
Engineering project paths

The engineering notebook

Beacon: ship it without fear

You can design and implement a zero-cloud-cost delivery path for Beacon: CI checks, supply-chain gates, digest promotion, Argo CD GitOps on kind, Kustomize overlays, progressive delivery, rollback runbooks and meaningful releases.

Before you begin

Prerequisites and setup

Prior knowledge: Basic Git and container concepts are helpful. The course explains continuous integration, artifact promotion, GitOps, deployment safety, and rollback using a prepared project; completing earlier courses is optional.

Tools, accounts, and cost: Start with a GitLab account and a project workspace for Beacon. Install Git and glab from https://docs.gitlab.com/cli/ (Windows: use PowerShell; macOS/Linux: follow the package-manager instructions), then run `glab auth login`, choose GitLab.com, and finish browser sign-in. Check with `glab auth status`. Add `.gitlab-ci.yml` at the project root. In GitLab, open Settings > CI/CD > Runners and confirm a runner is available; without one, jobs stay pending. In Settings > Merge requests > Merge checks, require successful pipelines before merging. You also need Go 1.22+, Docker, kind, and kubectl. Argo CD runs locally on kind, so no cloud account is needed.

Required course tool
GitLab CLI (glab)
Installation guide
Check it with glab --version.
Starting project
At `course-6-start`, Beacon already exists as a container image with Kubernetes manifests under `deploy/k8s/` and Terraform under `deploy/infra/`. Everything is still applied by hand. This course removes the hands: GitLab CI/CD builds evidence, GitOps reconciles the cluster, and releases become repeatable operations.
Estimated study time
about 15 hr 10 min across 9 stages.
Estimate sums each stage’s reading, implementation, and debugging time; your pace will vary.
Entry point
You may start here without completing earlier Vault paths. This prepared project snapshot includes the code described above; the listed knowledge, tools, and any cost notes still apply.

Your learning trail

0 / 9 complete

A verified submission confirms the project runs and prints the expected output. It does not grade code quality or award a credential. Course progress is saved in this browser, so it does not automatically transfer to another device.

System design

What you are building

Course 6 replaces hand-applied delivery with GitLab pipelines, immutable artifacts, GitOps reconciliation and release operations on a local kind cluster.

BEACON / THE PATH TO PRODUCTIONA commitone change, one authorTHE PIPELINE YOU OWNCIvet, race tests, buildGatesSBOM, scan, sign, attestConfig repothe digest, written downCanarya few users firstWHAT CLOSES THE LOOPArgo CDpulls, never pushed toRollbackmeasured in minutesanalysis rejects a bad canary without waking anyoneBUILD ONCE, PROMOTE A DIGEST, LET THE CLUSTER PULL

Stages

9 stages, in order

All lesson pages are readable, including locked stages. Locks apply only to verified project work: complete the previous stage before submitting the next one. Time labels are estimates for reading, implementation, and debugging; your pace will vary.

Phase 1Stages 1–20 of 2 stages verified

Trust the path

Separate integration, delivery and deployment, then make checks enforceable.

  • Trust the path first70 minutes (locked)

    What is a delivery pipeline actually for?

    You will be able to define CI, continuous delivery and continuous deployment in docs/delivery/pipeline.md.

    Fork the project repository to start working through the stages.

    Read what this stage covers
  • Make checks enforceable90 minutes (locked)

    How does the first GitLab pipeline prove Beacon still builds?

    You will be able to create .gitlab-ci.yml at the project root. GitLab reads this file automatically.

    Fork the project repository to start working through the stages.

    Read what this stage covers
Phase 2Stages 3–40 of 2 stages verified

Protect the artifact

Attach supply-chain evidence and promote one immutable digest.

  • Prove what you ship2 hours (locked)

    How does CI earn trust without storing long-lived secrets?

    You will be able to add a supply-chain pipeline that builds the image and produces an SBOM.

    Fork the project repository to start working through the stages.

    Read what this stage covers
  • Move the same bits90 minutes (locked)

    Why should environments receive the same image digest instead of rebuilding?

    You will be able to accept an OCI digest as the pipeline variable and never rebuild inside promotion jobs.

    Fork the project repository to start working through the stages.

    Read what this stage covers
Phase 3Stages 5–60 of 2 stages verified

Let Git drive the cluster

Use Argo CD and Kustomize so desired state is reviewed and reconciled.

  • Let the cluster pull2 hours (locked)

    Why does GitOps keep cluster credentials out of CI?

    You will be able to create an Argo CD Application manifest under deploy/gitops/.

    Fork the project repository to start working through the stages.

    Read what this stage covers
  • Shape manifests per place2 hours (locked)

    How can the same Kubernetes manifests fit dev, staging and production?

    You will be able to create a Kustomize base plus dev, staging and production overlays.

    Fork the project repository to start working through the stages.

    Read what this stage covers
Phase 4Stages 7–90 of 3 stages verified

Release and recover

Limit blast radius, recover from bad changes and make releases meaningful.

  • Release to a slice2 hours (locked)

    How do canaries and rollouts limit blast radius?

    You will be able to create an Argo Rollouts Rollout using argoproj.io/v1alpha1.

    Fork the project repository to start working through the stages.

    Read what this stage covers
  • Recover without guessing90 minutes (locked)

    What should happen when a release goes wrong?

    You will be able to write a rollback runbook under docs/delivery/rollback.md.

    Fork the project repository to start working through the stages.

    Read what this stage covers
  • Give releases meaning90 minutes (locked)

    How does a release tell users what changed and what promises now hold?

    You will be able to create a release job that accepts an explicit semantic version.

    Fork the project repository to start working through the stages.

    Read what this stage covers

Course overview

Beacon can be built, containerized, scheduled on Kubernetes and provisioned with infrastructure code, but every production move still depends on a human running the right commands in the right order. This course turns delivery into a controlled system with evidence, promotion, reconciliation and recovery.

What you will learn: CI pipelines, Software supply chain security, GitOps with Argo CD, Canary and progressive delivery, Rollback and release engineering. Build the project through cumulative challenges with beginner explanations and local verification.

Level
Complete beginner to independently building and operating the project
Format
9 cumulative stages. Every stage teaches the concept in full before any code, then gives you the thing to build and the run that proves it works
Official documentation