Why Kubernetes Ingress Controller Sticky Sessions Break Under Rolling Updates
from DevOps Daily with Fexingo: CI/CD, Kubernetes, and Modern Software Operations Hosted by Fexingo
In this episode of DevOps Daily, Lucas and Luna investigate a deceptively common Kubernetes failure: when ingress controller session affinity (sticky sessions) silently breaks during rolling updates. They walk through a real incident at a mid-size e-commerce platform where users were suddenly logged out mid-session after a routine deployment. Lucas explains the mechanics — how NGINX ingress controller uses Pod IP hashing by default, and how a new replica set flips the hash mapping, redirecting users to pods that have never seen their session data. Luna pushes on whether the fix is a readiness probe tweak, an external session store, or a different ingress controller. They also discuss when to use sticky sessions at all, and why session affinity is often a workaround for a deeper architectural issue. Concrete, specific, and immediately applicable for anyone running Kubernetes in production. #Kubernetes #IngressController #StickySessions #SessionAffinity #RollingUpdate #NGINXIngress #DevOps #SiteReliabilityEngineering #PodLifecycle #SessionManagement #K8sNetworking #ProductionIncident #ECommerce #LoadBalancing #ReadinessProbe #Technology #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo
Embed this episode
No transcript yet.