<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rancher on Danilo Falcão da Silva</title><link>https://falcao.org/tags/rancher/</link><description>Recent content in Rancher on Danilo Falcão da Silva</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 20 May 2026 21:15:00 -0300</lastBuildDate><atom:link href="https://falcao.org/tags/rancher/index.xml" rel="self" type="application/rss+xml"/><item><title>Rancher vs Lens: A Platform and a Dashboard, Not the Same Thing</title><link>https://falcao.org/posts/rancher-platform-vs-lens/</link><pubDate>Wed, 20 May 2026 21:15:00 -0300</pubDate><guid>https://falcao.org/posts/rancher-platform-vs-lens/</guid><description>&lt;p>You&amp;rsquo;ll see this comparison on r/kubernetes every couple of months,
phrased as if it&amp;rsquo;s a real choice: &lt;strong>Rancher or Lens?&lt;/strong> The framing is
wrong. They occupy different layers of the stack. Asking which one
&amp;ldquo;wins&amp;rdquo; is like asking whether VS Code beats Kubernetes.&lt;/p>
&lt;p>But the question keeps coming up — usually from someone who has Lens
installed, has heard about Rancher, and is trying to figure out
whether they should swap. So let me lay out what each one actually
is, where they overlap, where they don&amp;rsquo;t, and which one earns a place
in a serious on-prem setup.&lt;/p></description></item><item><title>GitOps with Argo CD: The Reconciliation Loop That Survives 3 a.m.</title><link>https://falcao.org/posts/gitops-argocd/</link><pubDate>Tue, 19 May 2026 13:30:00 -0300</pubDate><guid>https://falcao.org/posts/gitops-argocd/</guid><description>&lt;p>Here&amp;rsquo;s the test I use for any deployment tooling:&lt;/p>
&lt;p>&lt;strong>It is 3 a.m. on a Sunday. PagerDuty just woke you up. A production
service is degraded. You roll out of bed, open your laptop, and have
to figure out what the cluster &lt;em>thinks&lt;/em> is true, what&amp;rsquo;s &lt;em>actually&lt;/em>
true, and what changed in the last twelve hours. The faster you can
answer those three questions, the better the tooling.&lt;/strong>&lt;/p>
&lt;p>The right GitOps stack collapses all three questions into one
dashboard. The wrong one has you SSH-hopping between five servers
running &lt;code>kubectl rollout history&lt;/code> against unlabeled deployments. I&amp;rsquo;ve
done both. I&amp;rsquo;m writing this post about the former.&lt;/p></description></item><item><title>RKE2 Deserves Some Love: Why It's My On-Prem Kubernetes Pick</title><link>https://falcao.org/posts/rke2-on-prem-kubernetes/</link><pubDate>Tue, 19 May 2026 12:30:00 -0300</pubDate><guid>https://falcao.org/posts/rke2-on-prem-kubernetes/</guid><description>&lt;p>Most of the Kubernetes conversation in 2026 happens around managed
services — &lt;strong>EKS&lt;/strong>, &lt;strong>GKE&lt;/strong>, &lt;strong>AKS&lt;/strong> — and most of the rest happens
around &lt;strong>K3s&lt;/strong> for edge and homelab. Somewhere in the middle, on the
hardware that lives in a rack in a datacenter you can drive to,
there&amp;rsquo;s a Kubernetes story that nobody talks about loudly enough.&lt;/p>
&lt;p>That story is &lt;strong>RKE2&lt;/strong> — the Rancher Kubernetes Engine 2, SUSE&amp;rsquo;s
hardened, security-focused, single-binary distribution designed for
on-premises production. I&amp;rsquo;ve been running it for two years across
two different employers and one home lab, and it&amp;rsquo;s the rare piece of
infrastructure that gets more impressive the longer you live with it.&lt;/p></description></item></channel></rss>