TLS
posts (7)
- The Layers of HTTP in the Browser: From fetch() to QUIC8/9
HTTP/3 and QUIC: Same HTTP, Different Transport
QUIC removes transport-level head-of-line blocking and sets up a session more cheaply, but it does not fix the dependencies the frontend creates in its own…
- The Layers of HTTP in the Browser: From fetch() to QUIC5/9
Connections: Why One fetch() Does Not Mean One Connection
A request and a connection have different lifecycles. The connection pool belongs to the browser, and the frontend influences it only through the architecture…
Introduction to Service Mesh: Why Istio and Linkerd Exist
Service mesh appeared because, in a microservice system, traffic, identity, and observability problems started repeating in every service.
- Gateway API Without the Magic4/4
Migrating from ingress-nginx to Gateway API
Migrating from ingress-nginx is not mechanical YAML translation. First, separate the application contract from controller-specific behavior.
- Gateway API Without the Magic3/4
GatewayClass: A Contract With the Implementation
GatewayClass is not an environment label. It is where Kubernetes Gateway API meets a specific controller.
- Gateway API Without the Magic1/4
From Service to Gateway API: Where the Problem Came From
Ingress did not fail because it was bad. It failed because its small specification had no language for production HTTP behavior.
- series · 4 parts
Gateway API Without the Magic
A short entry point to a series about where Gateway API came from, how it differs from Ingress, and how to approach an ingress-nginx migration.