Continuous Delivery for DevOps Engineers
Continuous delivery extends CI so that every passing change can be released to production safely and repeatably. It uses release strategies such as rolling, blue-green and canary deployments, automated promotion between environments, and GitOps, where the desired state lives in Git and a tool like Argo CD or Flux applies it to the cluster.
Stage: Source Control and CI/CD · Part of the DevOps Engineer roadmap · Last reviewed 19 November 2026
What to learn in Continuous Delivery
- Compare rolling, blue-green and canary releases and their trade-offs
- Promote one build artefact through staging to production
- Roll back a bad release quickly and safely
- Use feature flags to separate deploy from release
- Describe the GitOps pull model with Argo CD or Flux
- Add smoke tests and automated checks after deployment
Continuous Delivery interview questions
What is the difference between continuous delivery and continuous deployment?
Continuous delivery keeps every change in a releasable state, with production release triggered by a manual decision. Continuous deployment goes further and releases every passing change to production automatically, with no human approval step.
What is GitOps?
GitOps stores the desired state of infrastructure and applications in Git. An agent in the cluster, such as Argo CD, continuously compares the live state to Git and reconciles differences. Changes go through pull requests, giving history, review and easy rollback.
Where Continuous Delivery fits in the DevOps Engineer roadmap
Continuous Delivery belongs to the Source Control and CI/CD stage (intermediate level), which takes about 2 hours. The delivery pipeline.
Other units in this stage
Back to the full DevOps Engineer roadmap