<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubernetes on cloudmato.com</title><link>https://cloudmato.com/tags/kubernetes/</link><description>Recent content in Kubernetes on cloudmato.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>cloudmato.com</managingEditor><webMaster>cloudmato.com</webMaster><lastBuildDate>Sun, 14 Jun 2026 21:29:11 +0530</lastBuildDate><atom:link href="https://cloudmato.com/tags/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>What Is Hadoop, and Why It Isn't 10 Microservices on K8s</title><link>https://cloudmato.com/posts/what-is-hadoop-vs-microservices-kubernetes/</link><pubDate>Sun, 14 Jun 2026 21:29:11 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/what-is-hadoop-vs-microservices-kubernetes/</guid><description>&lt;p&gt;Someone asked me this exact question last week, and it&amp;rsquo;s a good one because both setups &lt;em&gt;look&lt;/em&gt; the same if you squint. A bunch of machines, some shared storage in the middle, work spread across nodes. So why does one get called &amp;ldquo;big data&amp;rdquo; and the other &amp;ldquo;microservices&amp;rdquo;? Are they just two words for the same cluster? Honestly, no. They&amp;rsquo;re built on opposite assumptions about one thing: &lt;strong&gt;where the data lives and who moves to whom.&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Kubernetes Load Balancers: Inside, Outside, or Both?</title><link>https://cloudmato.com/posts/kubernetes-load-balancer-options/</link><pubDate>Thu, 04 Jun 2026 15:30:08 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/kubernetes-load-balancer-options/</guid><description>&lt;p&gt;Everyone setting up a Kubernetes cluster eventually hits the same wall: how do I actually get traffic into this thing? Then the docs mention ClusterIP, NodePort, LoadBalancer, Ingress, Gateway API, MetalLB — and it spirals. Worse, there&amp;rsquo;s a Service &lt;em&gt;type&lt;/em&gt; called &amp;ldquo;LoadBalancer&amp;rdquo; and there are actual load balancers, and they are not the same thing. Let me go through the real options, where each one sits in the stack, and what genuinely makes sense to reach for.&lt;/p&gt;</description></item></channel></rss>