<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Go on Alexandre Mulatinho Blog</title>
		<link>https://mulatinho.net/tags/go/</link>
		<description>Recent content in Go on Alexandre Mulatinho Blog</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Thu, 29 Oct 2026 19:16:00 -0300</lastBuildDate>
		
			<atom:link href="https://mulatinho.net/tags/go/posts/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Your Kubernetes CronJobs Web UI</title>
				<link>https://mulatinho.net/posts/jobs-dashboard/</link>
				<pubDate>Thu, 29 Oct 2026 19:16:00 -0300</pubDate>
				<guid>https://mulatinho.net/posts/jobs-dashboard/</guid>
				<description>&lt;p&gt;CronJobs are great right up until you need to answer a very ordinary question: &lt;em&gt;Did that thing run, and what happened?&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;The answer is usually somewhere between a terminal, a namespace, a handful of &lt;code&gt;kubectl&lt;/code&gt; commands, and one more YAML file than you wanted to read today.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;jobs-dashboard&lt;/strong&gt; brings the essentials into one small, self-hosted web app: schedules, recent runs, quick controls, and a direct look at what each Job actually did.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
