← ALL SERIES
COMPLETE MODERN INFRASTRUCTURE & IAC

Kubernetes Ingress Architecture Series

The Ingress-NGINX deprecation turns a controller choice into a migration and operations problem: pick the path, move to Gateway API without breaking production, then operate it.

Kubernetes Ingress Architecture Series - ingress-nginx deprecation

4 PARTS · READING ORDER

  1. CLOUD STRATEGY

    Ingress-NGINX Deprecation: What to Do Next (Four Paths, Four Failure Modes)

    04/04/2026

    The ingress-nginx deprecation changes the default ingress architecture for Kubernetes clusters. Here's the migration path, the alternatives, and the architectural tradeoff each one introduces.

  2. CLOUD STRATEGY

    Gateway API Is the Direction. Your Controller Choice Is the Risk.

    04/07/2026

    Gateway API Kubernetes controller selection is where the architectural risk lives — failure modes, Day-2 behavior, and operational tradeoffs for production clusters

  3. MODERN INFRASTRUCTURE & IAC

    Kubernetes Ingress to Gateway API Migration: How to Move Without Breaking Production

    04/15/2026

    Migrate ingress to Gateway API without breaking production. The annotation audit, ingress2gateway 1.0 reality check, side-by-side deployment pattern, and failure modes that only surface under real load.

  4. MODERN INFRASTRUCTURE & IAC

    Operating Gateway API in Production: What the Migration Guides Don’t Cover

    04/23/2026

    Gateway API production failures don't look like failures. Here's the observability model, policy boundaries, and Day-2 failure patterns teams hit in the first 60 days.