DevOps, CI/CD and GitOps
The course is built around a single application that delegates take from commit to production over the length of the programme. Each module adds a stage: build, test, artefact, security scan, environment promotion, deployment, observability, rollback. By the end the pipeline is complete and the delegates built every part of it.
GitOps is taught as an operating model rather than a tool choice. Both ArgoCD and Flux are covered, along with the increasingly common pattern of running both — Flux for platform concerns like certificates, monitoring and ingress, ArgoCD for application delivery. Delegates learn to choose rather than to advocate.
Failure receives proper attention. GitOps introduces a specific and dangerous failure mode: a reconciler rejected by a validating webhook, a quota limit or a CRD version mismatch will leave the pipeline reporting success while the cluster silently ignores the change. Instrumenting for that class of failure is a module in its own right.
Measurement runs throughout. Delegates instrument DORA metrics against their own pipeline and use them to argue for specific improvements, because a DevOps practitioner who cannot quantify delivery performance cannot make a case for investment in it.
- ○ Lessons, videos and quizzes from ₹5,000
- 🔒 Lab recordings at ₹15,000
- 🔒 Certification exam at full payment
- ○ Optional real lab: ₹5,000 per month (after full payment)
| Responsible | XertApp |
|---|---|
| Last Update | 10/11/2026 |
| Completion Time | 1 day 13 hours 30 minutes |
| Members | 1 |
-
Module 1 — DevOps foundations (empty)5Lessons · 2 hr 30 min
-
The delivery problem DevOps was invented to solve
-
Flow, feedback and continuous improvement
-
DORA metrics: deployment frequency, lead time, change failure rate, restore time
-
Platform engineering and the internal developer platform
-
Team topologies and where DevOps responsibility sits
-
-
Module 2 — Version control practice (empty)6Lessons · 3 hr
-
Git internals worth understanding
-
Branching models: trunk-based, GitFlow and the trade-offs
-
Pull request workflow and review practice
-
Monorepo against polyrepo
-
Conventional commits and automated versioning
-
Repository structure for infrastructure and application code
-
-
Module 3 — Continuous integration (empty)7Lessons · 3 hr 30 min
-
Pipeline design and stage decomposition
-
GitHub Actions: workflows, runners and reusable actions
-
GitLab CI and pipeline configuration
-
Jenkins and declarative pipelines
-
Azure Pipelines and cloud-native CI options
-
Build caching and pipeline duration as a structural constraint
-
Matrix builds and parallelisation
-
-
Module 4 — Testing in the pipeline (empty)5Lessons · 2 hr 30 min
-
Test pyramid and what belongs in CI
-
Unit, integration and contract testing
-
Ephemeral environments for testing
-
Quality gates and failing fast
-
Flaky tests and how they erode trust in the pipeline
-
-
Module 5 — Artefacts and supply chain (empty)6Lessons · 3 hr
-
Container image build and registry strategy
-
Artefact versioning and immutability
-
Software bill of materials
-
Image signing and provenance attestation
-
Dependency scanning and vulnerability management
-
Supply chain security frameworks
-
-
Module 6 — Security in the pipeline (empty)6Lessons · 3 hr
-
Shifting security left without stopping delivery
-
Static and dynamic analysis in CI
-
Secret scanning and preventing credential leakage
-
Secrets management: Vault, cloud secret stores, external secrets
-
OIDC federation instead of long-lived credentials
-
Policy as code and admission control
-
-
Module 7 — GitOps principles (empty)6Lessons · 3 hr
-
The four GitOps principles
-
Pull-based against push-based delivery
-
Declarative desired state and continuous reconciliation
-
Repository structure for GitOps
-
Separating application code from deployment configuration
-
Secrets in a GitOps world: sealed secrets and external operators
-
-
Module 8 — ArgoCD (empty)6Lessons · 3 hr
-
Architecture and the Application abstraction
-
Applications, projects and ApplicationSets
-
Sync policies, waves and hooks
-
Multi-cluster management
-
RBAC and single sign-on integration
-
The web UI as a debugging tool
-
-
Module 9 — Flux (empty)6Lessons · 3 hr
-
The GitOps Toolkit and controller model
-
Source, Kustomize, Helm, Notification and Image Automation controllers
-
Kustomization and HelmRelease resources
-
Image automation and tag promotion
-
Bootstrapping and multi-tenancy
-
Choosing Flux, ArgoCD, or both
-
-
Module 10 — Deployment strategies (empty)6Lessons · 3 hr
-
Rolling, blue-green and canary deployment
-
Progressive delivery with Argo Rollouts and Flagger
-
Feature flags and decoupling deploy from release
-
Automated rollback triggers
-
Database migrations in a continuous delivery pipeline
-
Environment promotion and pull request gates for production
-
-
Module 11 — Observability and pipeline failure (empty)7Lessons · 3 hr 30 min
-
Metrics, logs and traces as three views of one system
-
Prometheus, Grafana and alerting design
-
Distributed tracing and OpenTelemetry
-
Instrumenting GitOps reconciliation failures
-
Detecting silent sync failures: webhook rejections, quota limits, CRD mismatches
-
Service level objectives and error budgets
-
Alert fatigue and what to page on
-
-
Module 12 — Operating the practice (empty)6Lessons · 3 hr
-
Incident response and blameless post-mortems
-
Change management that does not block delivery
-
Cost awareness in the pipeline
-
Measuring and improving DORA metrics
-
Building an internal developer platform incrementally
-
Introducing DevOps practice into a resistant organisation
-
-
Capstone (empty)3Lessons · 1 hr 30 min
-
Complete pipeline from commit to production with GitOps delivery
-
Progressive rollout with automated rollback
-
Instrumented observability including reconciliation failure alerting
-
Who should attend
Aimed at engineers responsible for how software gets from a repository into production.
- DevOps and platform engineers
- Software engineers taking on delivery responsibility
- Systems administrators moving into automation roles
- Site reliability engineers
- Release and build engineers modernising legacy pipelines
- Technical leads establishing delivery practice for a team
- Consultants implementing delivery pipelines for clients
Assumed knowledge: comfortable Linux command line, working Git, and familiarity with containers. Kubernetes experience is strongly recommended, since the GitOps modules assume it; delegates without it should take the AppSolWorld Kubernetes course first. Some scripting ability in any language is expected.
Delivery
Duration
40 hours, delivered as weekday evenings or weekend sessions.
Format
Live instructor-led online, with recordings available to delegates for the duration of the programme. On-site corporate delivery available on request.
Lab environment
Each delegate receives a Kubernetes cluster and CI/CD tooling for the duration of the course and for four weeks afterwards.
Included
Course notes, lab guides, exercise solutions and a certificate of completion.
How to enroll
Enrol and pay online on this page. The full fee is ₹15,000 (US$170). You can start with ₹5,000 (US$60) and pay the balance in instalments within 3 months. Pay by card, UPI or net banking, or by PayPal in US dollars. Go to payment. For corporate, on-site or one-to-one training, contact contact@appsolworld.com or call +91 92051 38405.