A Safe Terraform State Migration Playbook
Move Terraform state without gambling on production: back up, verify locks, map addresses, prove plan equivalence, and preserve a tested rollback path.
Read the article →Insights
Working notes on the platform changes that carry real operational risk: state migrations, cluster upgrades, rollback design, developer platforms, and cloud cost. Written by the engineers who do the work.
Move Terraform state without gambling on production: back up, verify locks, map addresses, prove plan equivalence, and preserve a tested rollback path.
Read the article →Upgrade EKS with explicit checks for skew, deprecated APIs, add-ons, disruption budgets, replacement nodes, canaries, observability, and rollback limits.
Read the article →Build recovery into CI/CD with immutable artifacts, deployment records, compatible database changes, progressive delivery, flags, drills, and evidence.
Read the article →A useful internal developer platform standardizes repeatable decisions while keeping ownership, evidence, and exceptions visible to engineering teams.
Read the article →A disciplined AWS cost review starts with billing dimensions, idle assets, transfer paths, commitments, and unit economics before instance resizing.
Read the article →Production-ready Kubernetes workloads need resource contracts, disruption control, safe shutdown, scaling evidence, observability, and tested recovery.
Read the article →Earlier posts preserved from the original Redmanh engineering blog, kept at their original URLs.
A practical introduction to routing multiple applications through Traefik as a Kubernetes ingress controller.
Read the article →An engineering archive walkthrough of provisioning the AWS infrastructure for a Kubernetes cluster with Terraform.
Read the article →