<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking on Szymon Kocur</title><link>https://szymonkocur.com/tags/networking/</link><description>Recent content in Networking on Szymon Kocur</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 02 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://szymonkocur.com/tags/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Your Kubernetes Pods Get 502s During Deployments (and How preStop Hooks Fix It)</title><link>https://szymonkocur.com/posts/kubernetes-prestop-hooks-zero-downtime/</link><pubDate>Thu, 02 Apr 2026 00:00:00 +0000</pubDate><guid>https://szymonkocur.com/posts/kubernetes-prestop-hooks-zero-downtime/</guid><description>&lt;p&gt;If you&amp;rsquo;ve ever deployed to Kubernetes and seen users briefly hit a blank page or a &lt;code&gt;502 Bad Gateway&lt;/code&gt; error, you&amp;rsquo;re not alone. I ran into this exact issue on a production GKE cluster running a web frontend with multiple replicas behind a Google Cloud Load Balancer.&lt;/p&gt;
&lt;p&gt;The symptom: during a rolling update, for a few seconds, some users would see a black screen with a &amp;ldquo;failed upstream&amp;rdquo; message. Then it would resolve on its own. Annoying, intermittent, and hard to reproduce locally.&lt;/p&gt;</description></item></channel></rss>