<?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>Fluentd on The IT Hollow</title>
    <link>https://theithollow.com/tags/fluentd/</link>
    <description>Recent content in Fluentd on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 13 Aug 2019 14:10:04 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/fluentd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes - DaemonSets</title>
      <link>https://theithollow.com/2019/08/13/kubernetes-daemonsets/</link>
      <pubDate>Tue, 13 Aug 2019 14:10:04 +0000</pubDate>
      <guid>https://theithollow.com/2019/08/13/kubernetes-daemonsets/</guid>
      <description>&lt;p&gt;DaemonSets can be a really useful tool for managing the health and operation of the pods within a Kubernetes cluster. In this post we&amp;rsquo;ll explore a use case for a DaemonSet, why we need them, and an example in the lab.&lt;/p&gt;
&lt;h2 id=&#34;daemonsets---the-theory&#34;&gt;DaemonSets - The Theory&lt;/h2&gt;
&lt;p&gt;DaemonSets are actually pretty easy to explain. A DaemonSet is a Kubernetes construct that ensures a pod is running on every node (where eligible) in a cluster. This means that if we were to create a DaemonSet on our six node cluster (3 master, 3 workers), the DaemonSet would schedule the defined pods on each of the nodes for a total of six pods. Now, this assumes there are either no &lt;a href=&#34;https://theithollow.com/?p=9736&#34;&gt;taints on the nodes, or there are tolerations&lt;/a&gt; on the DaemonSets.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
