<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Eks on Danilo Falcão da Silva</title><link>https://falcao.org/tags/eks/</link><description>Recent content in Eks on Danilo Falcão da Silva</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 27 May 2026 23:20:00 -0300</lastBuildDate><atom:link href="https://falcao.org/tags/eks/index.xml" rel="self" type="application/rss+xml"/><item><title>EKS Hybrid Nodes Gateway Is the Hybrid Kubernetes Reality Check We Needed</title><link>https://falcao.org/posts/eks-hybrid-nodes-gateway/</link><pubDate>Wed, 27 May 2026 23:20:00 -0300</pubDate><guid>https://falcao.org/posts/eks-hybrid-nodes-gateway/</guid><description>&lt;p>I have been waiting years to write this sentence without rolling my eyes: hybrid Kubernetes on a major managed platform finally looks practical.&lt;/p>
&lt;p>Not perfect. Not magical. Practical.&lt;/p>
&lt;p>The new EKS Hybrid Nodes Gateway is the first AWS move in this space that feels like an operations feature, not a slide-deck feature. It directly targets one of the worst recurring pain points in hybrid Kubernetes: getting reliable traffic flow between cloud-side components and on-prem or edge pods without building a pile of bespoke routing logic that only two people on the team understand.&lt;/p></description></item></channel></rss>