You have just joined cigales.cloud as a senior developer in the Cicada Sense team. In your first week, you are asked to help manage cicada-sense, the world's leading community-driven cicada tracker, and keep it stable while new product requests are already coming.
The team is not starting from zero. Your predecessors left a production-ready application with a solid codebase, automated tests, container images, and a Helm chart. The product is live, the traffic is real, and one part is still missing: a delivery process that is safe, repeatable, and ready for change.
Step by step, you will work on the same decisions as a real team: make the integration flow safer, prepare the GitOps repository, automate releases, and move the same artifacts across environments without losing control of production.
You will do all of that in the Hoverkraft way: an opinionated platform engineering approach that helps teams spend less time on glue work and more time on the application, the delivery flow, and the operations choices behind each step.
Instead, as a learner, you should understand the delivery model proposed and implement it by yourself:
- start from a working multi-application repository
- add CI that validates pull requests and
main - prepare the
argocd-app-of-appsGitOps repository for the application - add CD that prepares releases and promotes the same built artifacts to review apps, UAT, and production
At the end of the workshop, learners should be able to reproduce the following workflow on their own organization without depending on the snapshot folders.
flowchart LR
code(Cicada Sense Codebase) -->|commit| CI(Github Actions) -->|release| GitOps(GitOps Source Of Truth)
GitOps --> review(Review Apps)
GitOps --> UAT
GitOps --> PROD
The application delivery part of the workshop is split across four numbered guides: Step 05, Step 06, Step 07, and Step 08.
- Step 05: bootstrap the learner repository from the baseline and confirm it works locally
- Step 06: add the GitHub Actions CI workflow
- Step 07: create and initialize the GitOps source-of-truth repository and add
cicada-senseto it - Step 08: add release preparation and deployment workflows in the application repository
The steps/ folder in this repository contains reference snapshots, in case you get lost or hit an unexpected issue.
They show the expected state for each stage, but you won't learn much by copying them blindly.
Learners should:
- work in their own
cicada-senseGitHub repository in their organization - use the Hoverkraft docs to understand the contract
- implement the changes and commit them in the dedicated repository
- compare with the snapshots only when they need to verify their results
Start with the step guide that matches your current stage:
- Step 05: 05-start.md - clone the prepared baseline and understand the repository shape
- Step 06: 06-add-ci.md - implement CI in GitHub Actions
- Step 07: 07-add-cd-gitops-repository.md - prepare the GitOps delivery repository and scaffold
cicada-sense - Step 08: 08-add-cd-application-repository.md - implement release and deployment workflows
Reference snapshot for the external GitOps repository used in Step 07:
steps/07-add-cd-gitops-repository- Step 07 snapshot for the externalargocd-app-of-appsrepository scaffolded forcicada-sense