RousselTMLEARNING

TP · DevOps: From Discovery to Expertise

Final project: a complete DevOps chain from commit to production

What you will learn in this TP
  • Chain CI, security and GitOps
  • Verify and roll back automatically
  • Measure the chain with DORA

Introduction #

What you will learn in this section
  • Chain CI, security and GitOps
  • Verify and roll back automatically
  • Measure the chain with DORA

Context. You present an end-to-end delivery chain for a new service to your management. Each step reuses a course lab; the goal is to chain them with no manual action between the commit and the cluster.

Prerequisites: a GitHub account, Docker, kubectl and kind; having completed the Git, CI/CD, GitOps and DevSecOps labs  ·  Estimated time: 120 min

A commit on main reaches production in minutes, verified, traceable and reversible.

Hands-on #

Guided steps, with their solution.

  1. 1. Two repositories

    Why? Separating code and deployment description gives separate permissions and histories.

    Create shop-api (code, Dockerfile, tests, workflow) and shop-deploy (Kustomize manifests base and overlays/staging, overlays/production). Protect main on both.
  2. 2. CI pipeline

    Why? The pipeline applies the CI/CD chapter lessons: fail fast, build once, secure.

    In shop-api, write a workflow: lint and tests, Gitleaks and Trivy, build and push to GHCR tagged with the SHA, SBOM and keyless Cosign signature.
  3. 3. Automatic deployment repository update

    Why? CI only needs to write to Git: it holds no cluster access.

    Add a job that updates the staging tag in shop-deploy with kustomize edit set image and pushes the commit (limited-scope token or GitHub App).
  4. 4. GitOps deployment

    Why? Argo CD applies every commit of the deployment repository and fixes any drift.

    On a kind cluster with Argo CD (GitOps lab), create two Applications shop-staging and shop-production pointing to the overlays, with automatic sync.
  5. 5. Verify and promote

    Why? Production receives exactly the image validated in staging, through a reviewed pull request.

    After staging syncs, run a smoke test; if it passes, automatically open a pull request copying the same tag to the production overlay.
  6. 6. Incident and rollback

    Why? A Git rollback is fast, traced and needs no cluster access.

    Ship a version returning 500 errors on /health, see the staging smoke test fail (no promotion), then simulate a production incident and roll back with git revert in shop-deploy. Write a short post-mortem.
  7. 7. Measure

    Why? DORA metrics show whether the chain delivers on its promise.

    Deploy five small changes and compute deployment frequency, commit-to-production lead time, failure rate and restore time (DORA lab method). Present the result and the next improvement.

Difficulty level : ●●●●○ (4/5)

My progress

  • ⏱ Estimated time : ≈ 2 h

Sign in to track your progress and take notes. Sign in

💬 Questions about this lesson

No questions yet: be the first to ask for help or share your configuration.

Ask a question about this lesson →

Recommended Articles

End-to-end CI/CD (1/5): principles and anatomy of a pipeline

Understand end-to-end CI/CD: continuous integration, continuous delivery and continuous deploymen...

End-to-end CI/CD (5/5): GitHub Actions, GitLab CI, Jenkins and Argo CD in practice

Compare and use CI/CD tools: GitHub Actions, GitLab CI, Jenkins, Argo CD and Flux; a complete pip...

Infrastructure as Code and GitOps: Terraform, Ansible and Argo CD

Manage infrastructure as code: declarative or imperative, Terraform (providers, state, plan, modu...

DevSecOps: securing the software supply chain end to end

Integrate security into the DevOps pipeline: shift-left, threat modeling, secret detection, SAST,...

Measuring DevOps performance: DORA metrics, SPACE and continuous improvement

Measure and improve delivery performance: the DORA metrics (deployment frequency, lead time, chan...

DevOps best practices: culture, CI/CD, infrastructure as code and measurement

DevOps best practices: culture and collaboration, continuous integration and delivery, trunk-base...

End-to-end CI/CD (4/5): deployment strategies and rollback

Deploy without downtime and without risk: recreate, rolling update, blue/green, canary, feature f...

Git for DevOps: branches, code reviews and versions

Organize work with Git in a DevOps approach: trunk-based development or GitFlow, short-lived bran...

The CALMS framework: the 5 pillars of DevOps

Discover the CALMS framework, the essential foundation for a successful DevOps transformation, th...

Support us

♥ SUPPORT US

Support RousselTM Learning

Courses, articles, labs and certificates stay free with no intrusive ads. A voluntary contribution, of any amount you choose, pays for hosting, lab environments and new content.

Contribute with PayPal Any amount · card or PayPal accountLearn more
QR code PayPal
Or scan this QR code with your phone

Thank you, every contribution counts!