<?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>Toleration on The IT Hollow</title>
    <link>https://theithollow.com/tags/toleration/</link>
    <description>Recent content in Toleration on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 29 Jul 2019 14:15:22 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/toleration/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes - Taints and Tolerations</title>
      <link>https://theithollow.com/2019/07/29/kubernetes-taints-and-tolerations/</link>
      <pubDate>Mon, 29 Jul 2019 14:15:22 +0000</pubDate>
      <guid>https://theithollow.com/2019/07/29/kubernetes-taints-and-tolerations/</guid>
      <description>&lt;p&gt;One of the best things about Kubernetes, is that I don&amp;rsquo;t have to think about which piece of hardware my container will run on when I deploy it. The Kubernetes scheduler can make that decision for me. This is great until I actually DO care about what node my container runs on. This post will examine one solution to pod placement, through taints and tolerations.&lt;/p&gt;
&lt;h2 id=&#34;taints---the-theory&#34;&gt;Taints - The Theory&lt;/h2&gt;
&lt;p&gt;Suppose we had a Kubernetes cluster where we didn&amp;rsquo;t want any pods to run on a specific node. You might need to do this for a variety of reasons, such as:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
