<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>kubernetes on Equativ's Tech Blog</title><link>http://tech.equativ.com/tags/kubernetes/</link><description>Recent content in kubernetes on Equativ's Tech Blog</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Thu, 29 Oct 2026 10:00:00 +0100</lastBuildDate><atom:link href="http://tech.equativ.com/tags/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>Saving network bandwidth by keeping Kubernetes traffic on the node</title><link>http://tech.equativ.com/articles/node-local-routing/</link><pubDate>Thu, 29 Oct 2026 10:00:00 +0100</pubDate><guid>http://tech.equativ.com/articles/node-local-routing/</guid><description>On our bare-metal Kubernetes clusters, a third of each node&amp;rsquo;s inbound traffic was a hop that never needed to leave the node. Here is how we made the ingress prefer a pod on its own node, without giving up load balancing.</description></item></channel></rss>