Modern Delivery And Platforms / DevOps And Platform Foundations
CI/CD And GitOps
Understand how pipelines and GitOps work together to make change safer, traceable, and repeatable.
Understand how pipelines and GitOps work together to make change safer, traceable, and repeatable.
Use the brief to sharpen a real cloud upskill conversation: what is the decision, what evidence matters, and what should remain human-led?
Capture one design rule you would reuse when reviewing an AI workload, assistant, or operating model.
Executive note
The Core Idea
CI/CD and GitOps are practices for managing change. CI checks whether a change is healthy. CD moves approved change toward users. GitOps uses Git as the source of desired state and lets a reconciler apply that state to the environment.
Together, they help teams release with less manual coordination and more evidence.
Section 2 of 7
Plain-English Vocabulary
- CI: Continuous Integration. Build, test, and validate changes frequently.
- CD: Continuous Delivery or Deployment. Prepare or automatically release validated changes.
- Pipeline: an automated workflow for build, test, package, and deploy steps.
- Artifact: the packaged output, such as a container image or manifest.
- GitOps: a model where environment state is declared in Git and applied by a controller such as Flux or Argo CD.
Section 3 of 7
Realistic Scenario
A team changes a service. CI runs tests and builds a container image. A release pipeline updates the image tag in a deployment repository. Flux notices the Git change and updates the Kubernetes cluster to match.
The important part is traceability. The team can see which code commit produced which image and which GitOps commit changed production state.
Section 4 of 7
Why It Matters
Manual releases often rely on memory and privileged access. CI/CD and GitOps make release intent visible, reviewable, and repeatable.
For business teams, this reduces release anxiety. It also creates a better audit trail: what changed, who approved it, when it deployed, and how it behaved.
Section 5 of 7
Common Misunderstandings
- CI/CD is not a guarantee that code is good; it automates checks that teams define.
- GitOps is not only for Kubernetes, but Kubernetes makes it especially natural.
- Automation does not remove approvals; it can make approvals clearer and more consistent.
- Faster release does not mean reckless release.
Section 6 of 7
Recommended Practices
- Keep build artifacts immutable.
- Separate application code, content, and infrastructure when ownership differs.
- Use automated validation before merge.
- Make rollback or forward-fix paths explicit.
Section 7 of 7
How To Talk About This With IT
Ask: "Which Git commit, pipeline run, artifact, and environment change prove what is currently running?"