- Why Halvard cannot deploy without Priya
- Your brief
- Starter repository and local cluster
Replace a hand-run deploy with a GitOps pipeline
Halvard ships its API by running a Jenkins job that one engineer understands, and nobody can say what is in production. Rebuild delivery as GitHub Actions for build and Argo CD for sync, with Helm values per environment, a canary rollout and a rollback you have actually rehearsed.
PCREATED BYPrepmeetsProject studio, Prepmeets
THE CHALLENGE → YOUR OUTCOME
Real context. Work that matters.
Halvard has one engineer who deploys, no record of what is live, and a board asking about SOC 2. You rebuild delivery as GitOps on a local kind cluster that stands in for both environments: CI builds and signs an immutable tag, Argo CD reconciles the declared state, a canary decides on real metrics, and a failed deploy reverts itself. You hand back the pipeline, the drill results and an honest note on what it will cost the team in habit changes.
What’s at stake
Your responsibility: Work as the platform engineer—investigate the requirements, implement your approach and verify the result.Halvard grew out of a two-person prototype and the deploy script grew with it. Today Priya runs `deploy.sh` two or three times a week, usually after standup, and it works. She is also the only person who knows that staging needs the migration run first, that the `latest` tag means "whatever we pushed most recently", and which three deployments in production have been edited by hand.
Success means: Cluster state declared in Git and reconciled automatically, a promotion path that is a reviewed pull request, a canary that aborts on a real metric, and a rollback that takes one revert and under two minutes — with the drill evidence to show it rather than a diagram claiming it. Explain the decisions and checks behind your implementation.
WHAT YOU’LL BUILD
01Kubernetes
02Argo CD
03GitOps
Halvard order API delivery pipeline
INCLUDED WITH YOUR PROJECT
A workspace, not just a document.
Your brief, a Jira-style task board and an interview studio—all in one place.
A look inside your workspace
Start with the full project brief
Build step by step Track your progress Own your interview story
Know where you’re heading.
- 01Why Halvard cannot deploy without Priya
- 02Your brief
- 03Starter repository and local cluster
- 04Two loops that never touch
- 05Five build phases
- 06Drift, canary and rollback drills
- 07What you hand over
- 08Submission and cleanup
Practise explaining your decisions
Which decision mattered most in your solution, and how did you verify it?
Use your own implementation to connect Situation, Task, Action and Result into one interview story.
Before you begin · tools & running costs
Prerequisites: Your own accounts and access to Argo CD, Helm 3, GitHub Actions, Argo Rollouts, Prometheus.
Additional costs: Cloud and tool usage in your own accounts may incur charges. Set a budget and clean up after testing.
Work in your own accounts and repositories. Never share credentials or confidential data.
What’s included
Project brief, target-design guidance, assigned tasks, resource guidance and interview prompts. Detailed requirements become part of your purchased workspace.
P
MEET YOUR PROJECT EXPERT
Prepmeets
Project studio, PrepmeetsWe are the team that builds Prepmeets. Between us we have run cloud platforms, delivery pipelines, analytics teams and AI governance programmes in banks, hospitals, retailers and government departments, and these projects are the work we used to hand to new joiners in their first fortnight. Every one of them is a real scenario with the client’s name changed, scoped to a week of evenings, and reviewed by the person who originally did the job.
View verified expert profile Expert review is an optional paid service, separate from project access.
£19.90Start this project