<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Workloads on Nerdsid.com</title><link>https://nerdsid.com/tags/workloads/</link><description>Recent content in Workloads on Nerdsid.com</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 17 Aug 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://nerdsid.com/tags/workloads/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes DaemonSets</title><link>https://nerdsid.com/posts/kubernetes-daemonsets/</link><pubDate>Mon, 17 Aug 2026 10:00:00 +0000</pubDate><guid>https://nerdsid.com/posts/kubernetes-daemonsets/</guid><description>&lt;p>DaemonSet runs exactly one Pod per matching node, and it schedules onto new nodes automatically as they join the cluster. That&amp;rsquo;s why CNI plugins, log shippers and node exporters are almost always DaemonSets rather than Deployments.&lt;/p>
&lt;p>Five short tasks below: three about reading an existing cluster, two about building a DaemonSet from scratch. Everything assumes the usual alias:&lt;/p>
&lt;figure class="codeblock">
 &lt;figcaption class="codeblock__header">&lt;span class="codeblock__filename codeblock__filename--lang">Bash&lt;/span>

 &lt;span class="codeblock__actions">&lt;/span>
&lt;/figcaption>

 &lt;div class="codeblock__body">
 &lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-bash" data-lang="bash">&lt;span class="line">&lt;span class="cl">&lt;span class="nb">alias&lt;/span> &lt;span class="nv">k&lt;/span>&lt;span class="o">=&lt;/span>kubectl&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>
 &lt;/div>
&lt;/figure>
&lt;h2 id="task-1-how-many-daemonsets-exist-cluster-wide">Task 1: How many DaemonSets exist cluster-wide?&lt;/h2>
&lt;p>The trap is the default namespace scoping — you have to ask for all namespaces explicitly:&lt;/p></description></item></channel></rss>