Kubernetes
posts (32)
- Deployment Strategies: Why They Exist5/6
Feature Flags: Deploy Is Not Release
A feature flag lets you deploy code without enabling behavior. It shortens feature rollback, but creates debt if flags are not removed.
- Deployment Strategies: Why They Exist4/6
Targeted Rollout: A/B Tests, Rings, and Segments
Canary splits traffic by percentage. Targeted rollout chooses specific users, rings, or segments, so it answers a different question.
- Deployment Strategies: Why They Exist3/6
Canary Deployment: The New Version Gets Part of the Traffic
Canary limits blast radius by using a small percentage of real traffic. Without metrics, it is only a slower rollout.
- Deployment Strategies: Why They Exist2/6
Blue-Green Deployment: Two Versions, One Traffic Path
Blue-green separates deploying from switching traffic. Rollback can be fast, but data does not move back with routing.
- Deployment Strategies: Why They Exist1/6
Rolling Update: Replacing Pieces Gradually
Rolling update removes downtime during version replacement, but it only works safely when old and new versions can live together for a while.
- series · 6 parts
Deployment Strategies: Why They Exist
Deployment strategies did not appear to make pipelines look serious. They appeared because replacing a version became a moment of risk.
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 Magic2/4
Gateway Does Not Always Mean the Same Thing
The word gateway mixes a product, a network role, and a Kubernetes API. Without that split, it is easy to compare things from different layers.