🐳 DevOps
📚 Documentation
Click a picture to open the full guide and its video:
Docker
Containers, Images, Volumes and Compose
Docker Compose
Git for Beginners
Git
Kubernetes
Run a Cluster and Its Workloads
Terraform
State, Import, Drift and Safe Changes
Terraform Modules
K9s
Popeye
Helm
Charts, Releases and Safe Upgrades
Kustomize
Git for Sysadmins and Operations
Docker Troubleshooting Playbook
kubectl Day-to-Day
Git Recovery
Docker Incident Runbooks
Proxmox VE
Install and Run It
Proxmox VE Web Interface
A Tour of the Screens You Use Every Day
Kubernetes on Proxmox
A Three-Node Cluster with kubeadm
Moving from VMware to Proxmox VE
Because "it works in staging" is the most dangerous phrase in IT.
Why did the DevOps engineer bring a ladder to work?
Because he heard the CI/CD pipeline needed a step up!
Because he heard the CI/CD pipeline needed a step up!
Core Principles
- Infrastructure as Code — Treat your servers like cattle, not pets
- Continuous Everything — CI, CD, and even continuous deployment
- Monitoring and Observability — You can't fix what you can't see
- Shift Left — Catch problems early (like security in code review)
- Immutable Builds — Rebuild and redeploy, don't patch in place
⚠️ Common Anti-Pattern: kubectl apply -f --force — Because sometimes you just want to break things faster.
⚠️ Pro Tip: Never tag a production image latest and call it a version. Pin your tags.
Coming Soon
- GitOps with ArgoCD and Flux
- Observability stack (Prometheus, Grafana, Loki)
- Blue/green deployments
- Chaos engineering for fun and profit
How many DevOps engineers does it take to change a lightbulb?
None — it's automated in the pipeline!
None — it's automated in the pipeline!