AOAdedoyin Ogunsolainadehorizon.hashnode.dev路Sep 10 路 2 min read饾棜饾椂饾榿饾棦饾椊饾榾: Argo CD + Kubernetes ClusterIt was interesting to see Argo CD implement a GitOps workflow, with the manifests stored in my Git repository. Argo CD continuously performed drift detection, comparing the live state of the Kuberne00
AOAdedoyin Ogunsolainadehorizon.hashnode.dev路Sep 3 路 4 min readCrashLoopBackOff Prod-Anatomy and 10-category Kubernetes Error mapEvents are one of my first troubleshooting stops when a Pod isn't behaving as expected. I can inspect them with: kubectl describe pod <pod-name> Or kubectl get events -n --sort-by=.lastTimestamp E20
AOAdedoyin Ogunsolainadehorizon.hashnode.dev路Sep 2 路 5 min readSolving ImagePullBackOff, CrashLoopBackOff and OOMKilled Pod-Status in K8sThe real Kubernetes troubleshooting skill isn't memorizing error names, it's knowing which layer to check next based on the symptom in front of you. kubectl describe pod <pod-name> + Events is one of 10
AOAdedoyin Ogunsolainadehorizon.hashnode.dev路Aug 31 路 6 min readScaling the AWS Infratructure I Built Using Modules, Multi-Env, and a Self-Provisioned State BackendA while back I built a secure VPC project for a company that needed employees to reach internal Linux servers on AWS without exposing anything to the open internet (View 馃憠 Here). It worked well as 10
AOAdedoyin Ogunsolainadehorizon.hashnode.dev路Aug 31 路 4 min readDiagnosing a Production-Like Resource Incident on AWS EC2 Ubuntu ServerThe idea Instead of just reading about high CPU or memory usage, I wanted to recreate the scenario myself: spike the resources, watch the system struggle, find the offending process, kill it, and conf00
