Skip to content
sec/atlas
knowledge base · devops

DevOps foundations, mapped.

The ground DevOps and DevSecOps stand on: Linux, Git, containers, pipelines, releases, infrastructure as code, Kubernetes, observability and reliability.

$ click a card for details · ctrl+k to search

learning map

Topics are laid out by level, from foundations to advanced. Arrows point from a prerequisite to what builds on it. Select a topic to preview it, or follow the highlighted next step.

Your next step

0 of 10 studied
start this topic

01 Foundations

The ideas everything else builds on.

02 Practitioner

Apply the controls and make them work in practice.

03 Advanced

Design, scale and operate at depth.

  • studied
  • ready to study
  • prerequisites missing

from commit to healthy production

Foundations, delivery, provisioning and operations: every piece has a place in the loop. Each chip opens the matching topic.

  1. 01foundations

    the ground everything stands on

    Linux, processes and networkingbranches, pull requests and ownershipimages and containers

    gate: you can reproduce, inspect and explain a service from the shell

  2. 02deliver

    from commit to production

    the delivery loop and its principlesfast, reliable pipelinescanary, blue/green and flags

    gate: every change ships through the same automated, reversible path

  3. 03provision

    what it all runs on

    infrastructure described as coderunning containers across a cluster

    gate: environments are rebuilt from code, not repaired by hand

  4. 04operate

    healthy in production, learning from failure

    metrics, logs, traces and alertsSLOs, error budgets and incidentspostmortems and toil reduction

    gate: you know when users are hurting before they tell you

topics

Linux and networking essentials
Containers, clouds and pipelines all run on Linux and talk over TCP/IP. When something breaks at 3 a.m., these fundamentals are what let you find out why.
technique· stage: foundations
Git workflows and code review
Every change enters production through version control. How you branch, review and merge decides how fast you can ship and how safely you can undo.
technique· stage: foundations
Containers and images
A container packages an application with its dependencies and runs it isolated from the host. A good image is small, deterministic and runs as a non-root user.
technique· stage: foundations
The delivery lifecycle
DevOps is the practice of shortening the loop between an idea and learning how it behaves in production, while keeping each step safe. The pipeline is how that loop is made repeatable.
concept· stage: deliver
CI pipelines that stay fast
A pipeline people trust is fast, deterministic and clear when it fails. A slow or flaky one trains the team to ignore it.
technique· stage: deliver
Release strategies and rollback
Deploying and releasing are different. You can put code in production dark, then turn it on gradually and turn it off in seconds if it misbehaves.
practice· stage: deliver
Infrastructure as code
When infrastructure is code, a change has a diff, a reviewer, a history and a way back. When it is clicks in a console, nobody can say what exists or why.
technique· stage: provision
Kubernetes fundamentals
Kubernetes runs containers across a cluster and keeps them in the state you declared. Learn the few objects that matter and the settings that stop one bad pod from taking everything down.
technique· stage: provision
Observability: metrics, logs and traces
Monitoring tells you something is wrong; observability lets you ask why. Three signals, a few golden metrics and alerts on symptoms cover most needs.
technique· stage: operate
Reliability: SLOs, error budgets and incidents
Perfect reliability is infinitely expensive and nobody needs it. SRE turns "be reliable" into a number you can budget, alert on and trade against new features.
concept· stage: operate