<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubectx on Danilo Falcão da Silva</title><link>https://falcao.org/tags/kubectx/</link><description>Recent content in Kubectx on Danilo Falcão da Silva</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 25 May 2026 14:35:00 -0300</lastBuildDate><atom:link href="https://falcao.org/tags/kubectx/index.xml" rel="self" type="application/rss+xml"/><item><title>The Kubernetes Operator's Batman Utility Belt: Day-2 Tools That Actually Earn Their Keep</title><link>https://falcao.org/posts/batman-belt-kubernetes-tools/</link><pubDate>Mon, 25 May 2026 14:35:00 -0300</pubDate><guid>https://falcao.org/posts/batman-belt-kubernetes-tools/</guid><description>&lt;p>&lt;code>kubectl&lt;/code> is the Swiss Army knife. Nobody disputes this. But Swiss
Army knives are terrible at most of the individual jobs they claim to
do, and &lt;code>kubectl&lt;/code> is no different: it can tail logs, but only one pod
at a time. It can switch contexts, but with zero guardrails. It can
describe resources, but in a wall of YAML that buries the thing you
actually care about.&lt;/p>
&lt;p>Day-2 operations — the part where the cluster is live, traffic is
flowing, and someone pages you at 2 a.m. — need sharper instruments.
What follows is the utility belt I&amp;rsquo;d recommend to any Kubernetes
operator building their toolkit in 2026. Not everything here is new.
Some of these tools have been around since 2018. The point is that
they&amp;rsquo;re still maintained, still solve real problems, and still faster
than the &lt;code>kubectl&lt;/code> incantation you&amp;rsquo;d otherwise be typing.&lt;/p></description></item></channel></rss>