Tag
54 articles tagged #DevOps.
P.01A runbook people follow at 3 a.m. is short, starts with a check, and ends with a decision. Here is the template we use, with a worked example.
P.02Cron jobs fail in three specific ways in production: overlapping runs, missed runs after downtime, and silent failures nobody notices. Here's how to close all three.
P.03Rotate a secret safely by provisioning the new value, running it alongside the old one, confirming every consumer, then revoking. Here's the runbook.
P.04Trunk-based development wins on speed and CI/CD fit for most teams. Git Flow still earns its keep for versioned software. The verdict, by criterion.
P.05MikroTik patched three RouterOS bugs after CISA confirmed active exploitation of two: which CVEs to prioritize and how to check your router for compromise.
P.06Cloudflare logged 13 incidents between August 7 and 14, touching R2, Durable Objects, and Workers KV. What that means for building on one edge provider.
P.07Kubernetes 1.37 shipped August 26 with 67 enhancements. What actually graduated to stable, what's worth testing in beta, and what to leave alone for now.
P.08Argo Rollouts replaces a Deployment with a controller that shifts traffic gradually and rolls back on bad metrics. Real manifests, plain Deployment to canary.
P.09Every rolling deploy drops a few requests and the errors look like client noise. The shutdown sequence, the race behind it, and the code that fixes it.
P.10macOS 27 deprecates hdiutil and points disk image work at diskutil image. The subcommand mapping, what's missing, and updating a DMG build without breaking CI.
P.11Deployment frequency, lead time, change failure rate, time to restore. What each measures, the tiers that separate elite teams, and where teams misuse them.
P.12A log line that's just a sentence is fine until you search a million at 2am. How structured logging works, threading a correlation ID, and what to skip.
P.13The keyv attack poisoned 2,234 package versions in a day, and it won't be the last. The checklist for install scripts, provenance, lockfiles, and CI tokens.
P.14One checkout request touches five services and nobody knows which is slow. How trace IDs, spans, and context propagation fix that, with OpenTelemetry code.
P.15An SLA is a promise with a penalty. An SLO is the internal target that keeps you inside it. An error budget is what's left. The math, on a real example.
P.16Four philosophies for one problem: moving a schema from what it is to what it should be, safely, in a team. How they differ and which fits your stack.
P.17Kubernetes 1.36 shipped 70 enhancements with no headline rewrite, just years of work reaching stable. What changes for platform teams, and what to skip.
P.18A unit-pricing bug sent some AWS customers cost projections in the billions on July 16. Invoices were fine; automation wired to those estimates wasn't.
P.19Trusted publishing lets GitHub Actions and GitLab CI publish via short-lived OIDC tokens instead of a stored npm token. The setup, and the May 2026 change.
P.20Platform engineering has its own hiring cluster now, distinct from DevOps, SRE, and cloud architecture. How to screen for product thinking over ticket-taking.
P.21npm v12 blocks preinstall, install, and postinstall scripts, Git dependencies, and remote tarballs unless allowed. What breaks, and how to migrate.
P.22Chaos engineering injects failure into a running system to find weaknesses before an outage does. What it involves, what tools help, and when to skip it.
P.23DevSecOps is distinct from DevOps and from security engineering. What the role covers, what to screen for, and why supply chain security is now the core.
P.24SRE is a discipline, not DevOps with a pager. How to define the role, screen for reliability math, and avoid hiring an ops generalist by accident.
P.25Both tools keep your dependencies current automatically. Here is how they actually differ, where each one breaks down, and which to choose based on your team's setup.
P.26The DevOps engineer title now covers three jobs: platform engineer, SRE, and CI/CD specialist. What each does, what to screen for, and what the market pays.
P.27Setting up metrics with Prometheus and dashboards with Grafana: what to instrument, what to skip, and what a dashboard should show during an incident.
P.28Dev Containers define your entire dev environment in a devcontainer.json file, so new teammates are productive in minutes. Here's how to set them up.
P.29Vulnerability scanning catches known CVEs in your base images before they reach production. Here's how to set up Trivy and Snyk, read their output, and act on findings.
P.30Multi-stage Docker builds cut image size by 80-90%, speeding up pulls, cold starts, and CI, while shrinking your attack surface and registry bill.
P.31Every cloud decision locks you in somewhere; the real question is which lock-in costs less. A practical framework for when to abstract and when to accept it.
P.32Fly.io and Railway sit between Vercel's simplicity and AWS's complexity, making them the most practical hosts for backend-heavy full-stack apps in 2026.
P.33Git worktrees give you multiple branches checked out in separate directories at once. No stashing, no context switching, no losing your place.
P.34Blue-green and canary deployments limit the blast radius of a bad release. Here's how each works, with real Kubernetes and Argo Rollouts configs.
P.35Structured commit messages unlock automatic changelogs, version bumps, and release notes. The full setup, from commitlint hooks to shipping in CI.
P.36eBPF attaches programs to any Linux kernel hook, network packets, syscalls, function calls, without patching the kernel. Here's what developers need to know.
P.37Tailscale is a mesh VPN giving distributed teams private networking between laptops, servers, and office machines in about 30 seconds, no VPN hardware needed.
P.38Multi-cloud usually costs more in engineering time than the lock-in risk it prevents; most teams do better on one cloud with deliberate exceptions.
P.39OpenTelemetry is the observability standard now, but most tutorials skip the hard part: which signals help you debug, and which just add noise and cost.
P.40HPA scales on CPU and memory. But most production workloads don't scale well on those signals. KEDA, VPA, and Goldilocks fill the gaps that HPA leaves open.
P.41k6 is a load testing tool with JavaScript scripting and CI integration. Writing meaningful tests, reading the results, and catching regressions early.
P.42CodeRabbit and GitHub Copilot code review changed the first pass. Here's what these tools actually catch, where they fail, and a workflow that combines both effectively.
P.43From .env files to Vault to AWS Secrets Manager: a practical guide to storing credentials, API keys, and certificates without waking up to a breach notification.
P.44A practical incident response process for small teams: severity tiers, on-call rotations, better alerting, and blameless postmortems, no SRE org required.
P.45Leaked credentials are the most preventable breach category. When you need a real secrets manager, which one to pick, and what to do if you're still on .env.
P.46Most teams adopt a service mesh before they actually need one. Here's the decision framework, real cost tradeoffs, and when Istio, Linkerd, or Cilium earns its keep.
P.47A few hours of optimization can cut CI time 40-60% and your GitHub Actions bill by a similar margin. Here's exactly how, with the configs that do it.
P.48HashiCorp's 2023 BSL relicensing split Terraform into OpenTofu, while Pulumi took a code-first approach. Here's how to choose between them in 2026.
P.49Backstage is open source and highly customizable but needs a team to run it. Port and Cortex are SaaS portals that start faster. How to choose and measure one.
P.50EditorPickEveryone said Wasm would kill Docker. Two years later they coexist, and teams running both ship faster: a reality check on Wasm, containers, and the containerd shim.
P.51Trunk-based, Git Flow, GitHub Flow: here is the simple Git workflow that works for teams under 10, why Git Flow struggles at that size, and the mistakes to avoid.
P.52GitOps adoption hit 64% in 2025, but costs rose with it. Real-time cost visibility in every infrastructure PR is how serious teams are fixing that in 2026.
P.53Monorepos are mainstream, but choosing between Turborepo, Nx, and pnpm workspaces is confusing. Here's a practical guide to picking the right tool for your team.
P.54Most agencies vanish after launch. Here's our exact 90-day post-deployment process, from day-one monitoring to the month-three client handoff meeting.