Terraform

Catching Terraform Drift in CI Before a Manual Change Reaches Production

by
Catching Terraform Drift in CI Before a Manual Change Reaches Production

By KP  |  TZoneLabs  |  DevOps & Cloud Engineering Someone changed a security group in the console to unblock themselves during an incident, and it never made it back into the .tf file. Terraform doesn’t know that happened until the next apply either quietly reverts it or, worse, doesn’t touch it because nothing in the … Read more

Structuring Terraform Modules and Remote State: What Actually Scales Past One Environment

by
Structuring Terraform Modules and Remote State: What Actually Scales Past One Environment

By KP  |  TZoneLabs  |  DevOps & Cloud Engineering A single main.tf with every resource for every environment works for the first few weeks of a project. It stops working the day you need a second environment, and by the time a team is running terraform plan against a 2,000-line file, nobody wants to touch … Read more

A Killed CI Job Left a Terraform State Lock Behind, and It Blocked Every Pipeline for 40 Minutes

by
A Killed CI Job Left a Terraform State Lock Behind, and It Blocked Every Pipeline for 40 Minutes

By KP  |  TZoneLabs  |  DevOps & Cloud Engineering Every terraform plan across three separate pipelines started failing with the same message: Error acquiring the state lock. Nothing was running. The lock had been held by a CI job that got killed by a pipeline timeout forty minutes earlier, and it never got the chance … Read more

Your EKS Nodes Run Out of IPs, Not CPU: A Practical Guide to VPC CNI Warming and Prefix Delegation

by
Your EKS Nodes Run Out of IPs, Not CPU: A Practical Guide to VPC CNI Warming and Prefix Delegation

By KP  |  TZoneLabs  |  DevOps & Cloud Engineering Most engineers size EKS nodes by CPU and memory. We did too — until one day a pod sat in Pending, the node had plenty of compute free, and the events said something about failing to assign an IP. That was our introduction to the quietest … Read more