<?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>Rbac on Mohanad Abu-Nayla</title><link>https://hannody.github.io/tags/rbac/</link><description>Recent content in Rbac on Mohanad Abu-Nayla</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 23 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://hannody.github.io/tags/rbac/index.xml" rel="self" type="application/rss+xml"/><item><title>On-Demand Namespace Error Log Watcher in a Locked-Down Kubernetes Environment</title><link>https://hannody.github.io/posts/k8s/kubernetes-stern-error-watcher/</link><pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate><guid>https://hannody.github.io/posts/k8s/kubernetes-stern-error-watcher/</guid><description>&lt;p&gt;During a large-scale stress test, the last thing you want is to be hunting errors across 150 pods manually.&lt;/p&gt;
&lt;p&gt;So I built an on-demand error log watcher for a complex Kubernetes namespace under real-world constraints, without touching anything outside the namespace, and without installing a single binary on the server.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What we are building:&lt;/strong&gt; a Kubernetes Deployment, scaled to zero by default, that runs &lt;a href="https://github.com/stern/stern"&gt;Stern&lt;/a&gt; as a container inside the cluster. It watches all pods in a target namespace, filters output to errors only, and can be started or stopped with a single &lt;code&gt;kubectl scale&lt;/code&gt; command. The entire setup RBAC, ServiceAccount, and Deployment lives within the targeted namespace it monitors and leaves no trace when removed.&lt;/p&gt;</description></item></channel></rss>