学習を始める→
ホーム/ロードマップ/Cloud Infrastructure & SRE Engineering

Cloud Platform & Site Reliability Engineering (SRE)

Design, automate, and operate high-availability cloud platforms. Learn how Linux namespaces isolate processes, how Kubernetes schedules pods, how Terraform declares infrastructure, and how eBPF observability catches production latency spikes.

Total Effort:~390 Hours
Pace:34 Weeks (~12h/wk)
Rigor:Systems Intensive
"You Are Here" Progress Tracker
0 of 2 Nodes Mastered
•
0% Complete
01
Phase 1Operating System Internals

Linux Kernel Internals & Container Virtualization

cgroups v2, network namespaces, overlay filesystems, systemd, and building containers from scratch in bash.

1Learner Experience Window
⚡The Wall of Abstraction

What you're experiencing: "Linux Namespaces & Process Isolation"

You used Docker for years without knowing what it does. Now, digging into `/proc`, `unshare`, and `iptables` rules feels dizzyingly low-level.

What your internal monologue sounds like right now:
“Containers aren't mini virtual machines? They're just regular processes with restricted kernel views!”
“Looking at `strace` output and seeing system calls demystified why my permission errors were happening.”
Neurobiology of this stage

You are gaining root-level confidence in the operating system. You no longer fear Linux configuration files, memory limits, or kernel panics.

⚠️ Pitfall to dodge:
  • Running containers as root user in production without dropped Linux capabilities.
  • Ignoring memory limits and watching the Linux OOM-killer silently terminate critical backend processes.
Sanity Check & Breakthrough Tactic
Build a container runtime from scratch using `unshare`, `chroot`, and `cgroups` in a 50-line bash script. It will dissolve all container mystery.
Remember: Discomfort is evidence of synaptic adaptation.Keep coding →
Linux & OS•Intermediate

Linux Internals: Namespaces, cgroups v2 & System Calls

Process isolation (PID, Mount, NET, IPC), resource quotas, memory cgroups, and strace debugging.

⏱️ ~35h•2 Elite Resources
Orchestration•Advanced

Kubernetes Architecture: Control Plane & Reconciliation Loops

API server, etcd consensus, kube-scheduler, kubelet, and declarative state reconciliation.

⏱️ ~45h•2 Elite Resources
Capstone Checkpoint⏱️ ~30h Portfolio Spec
Advanced

Capstone: Production Multi-Node Kubernetes Cluster with GitOps (ArgoCD)

Provision a highly available 3-node Kubernetes cluster from virtual machines. Configure TLS certificates with cfssl, set up Cilium CNI with eBPF data path, deploy ingress-nginx, and establish a declarative GitOps pipeline with ArgoCD.

Required Proof-of-Competence Deliverables:
Encrypted etcd multi-member cluster configuration with automated backup cron
Cilium CNI deployed in kube-proxy replacement mode utilizing eBPF
ArgoCD GitOps application tracking a GitHub repository with automated sync and rollback policies