OffNet Newsroom

Daily topic roundup

Automation / DevOps / IaC

Wednesday, August 19, 2026 · 8 stories, curated & summarized — click any story for the source.

Jeremy Schneider explains that Kubernetes relies on cgroups v2 memory.stat (current-inactive_file) to calculate container_memory_working_set_bytes for pod eviction. For PostgreSQL, this metric is misleading because it reflects file cache rather than actual resident memory usage, failing to predict Out-Of-Memory crashes. The author recommends abandoning this metric for Postgres workloads in favor of more accurate indicators of memory pressure.

  • K8s eviction logic uses container_memory_working_set_bytes, which is inaccurate for Postgres memory reporting.
  • The metric tracks inactive file cache, not resident memory, hiding true OOM risk from DBAs.
  • Setting requests < limits with this metric can lead to unexpected pod kills for database workloads.
  • Use alternative metrics provided in the author's analysis to monitor actual Postgres memory pressure.
TRADE-OFFPostgres Memory MetricsK8s Working SetTracks inactive file cacheSkewed by Postgres cachingMasks real OOM riskActual Resident MemoryReflects true usagePredicts crashes accuratelyBetter eviction signalsvs

AWS has extended its open-source IAM Policy Autopilot tool to accept Terraform plan files as input, enabling deterministic policy generation for infrastructure-as-code deployments. Previously limited to application source code, the tool now analyzes the plan to produce scoped-down IAM policies targeting the specific CRUD operations required by the resources. This update allows engineers to generate policies that reference exact resource ARNs instead of wildcards, streamlining the creation of least-privilege access rules for AWS infrastructure.

  • Terraform plan files are now valid inputs for IAM Policy Autopilot alongside application source code.
  • Policies generated from plans are scoped to specific CRUD functions needed by the infrastructure resources.
  • Output policies use explicit resource ARNs rather than wildcard permissions to enforce least privilege.
  • This reduces manual effort in writing IAM policies and simplifies troubleshooting access issues for IaC.
CHECKLISTWhat matters hereTerraform plan files are now valid inputs for IAM Policy Autopilot…Policies generated from plans are scoped to specific CRUD functions…Output policies use explicit resource ARNs rather than wildcard…This reduces manual effort in writing IAM policies and simplifies…

Asana utilized OpenAI Codex to modernize its legacy testing infrastructure, a task originally estimated to require five years of engineering effort. The entire migration was completed in just two weeks at a cost of approximately $12,000. This case highlights the potential for AI coding assistants to drastically accelerate large-scale refactoring and system replacement projects. The move demonstrates a significant reduction in both time-to-deployment and financial expenditure for complex engineering initiatives.

  • AI coding tools can compress multi-year engineering roadmaps into weeks.
  • Cost efficiency is substantial, with this project costing only $12K.
  • Legacy system replacement is a viable candidate for AI-assisted refactoring.
  • Speed gains are critical for maintaining competitive engineering velocity.

AWS has updated Console-to-Code to support 32 services, a significant jump from the original six, allowing more manual workflows to be converted into infrastructure as code. The tool now records actions across different regions and browser tabs without resetting the capture list, preserving context for complex deployments. This enhancement aims to help DevOps engineers and cloud architects automate multi-region infrastructure setups more reliably.

  • Service coverage grows from 6 to 32 AWS services for IaC generation
  • Cross-region and cross-tab recording prevents action list fragmentation
  • Consolidated action list maintains context for multi-region deployments
  • Available immediately in all commercial AWS Regions
THE SHIFTConsole-to-Code Service Expansion6INITIAL SERVICES32CURRENT SERVICESMajor coverage expansion for IaC automation

CYBERTEC's PG Operator simplifies deploying highly available PostgreSQL clusters on Kubernetes by reducing complex configurations to a small YAML manifest. The approach automates leader election, streaming replicas, and automatic failover, verified end-to-end using Minikube with Kubernetes 1.30 and Operator version 0.9.2. This method allows practitioners to spin up a production-ready, fault-tolerant database environment with minimal manual wiring.

  • CYBERTEC PG Operator handles HA logic including leader election and streaming replicas automatically.
  • Deployments require only a 14-line YAML file, significantly reducing configuration overhead.
  • Validated on Minikube with Kubernetes 1.30, CPO 0.9.2, and PostgreSQL 18.4.
  • Automatic failover and health checks are managed by the operator without manual intervention.

Gabriele Bartolini and Rob Kenefeck detail a walkthrough for deploying OpenBao on Kubernetes using CloudNativePG as the storage backend. The architecture relies entirely on open-source CNCF projects, ensuring no vendor lock-in. Authentication is handled exclusively through TLS client certificates via the DatabaseRole CRD, eliminating passwords from the stack.

  • Eliminates password management by enforcing TLS client certificate authentication via DatabaseRole CRD.
  • Maintains zero vendor lock-in by using only CNCF projects: Kubernetes, CloudNativePG, and OpenBao.
  • Provides a validated recipe for integrating HashiCorp-style secret management with PostgreSQL on K8s.
  • Co-authored with ControlPlane, offering practical insights for production-grade deployments.

Running flyway validate checks that local migration files have not changed since they were applied, but it does not verify the current database schema matches those files. The tool recomputes checksums for local SQL files and compares them against stored records in the flyway_schema_history table. A green status only confirms file integrity, not that the live database reflects the expected state.

  • Validate checks file integrity, not database state consistency.
  • Checksums are stored in flyway_schema_history per migration version.
  • A green result does not prove the database matches your migrations.
  • Do not assume schema parity based solely on validate output.

Sam Newman draws parallels between progressive collapse in civil engineering, exemplified by the Ronan Point disaster, and cascading failures in modern distributed systems like AWS outages. He outlines key resilience strategies for software leaders to prevent such catastrophic events. The approach focuses on strengthening individual components, isolating failures effectively, and reducing unnecessary interconnections. These principles aim to limit the blast radius of any single point of failure.

  • Apply civil engineering concepts like progressive collapse to distributed system design.
  • Strengthen critical components to withstand unexpected load or failure.
  • Isolate failures to prevent them from propagating across the system.
  • Reduce interconnections to limit the scope of potential cascading outages.
  • Use real-world examples like Ronan Point and AWS outages for practical context.
↑