<?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>Control-Loop on The IT Hollow</title>
    <link>https://theithollow.com/tags/control-loop/</link>
    <description>Recent content in Control-Loop on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 16 Sep 2019 14:05:30 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/control-loop/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes - Desired State and Control Loops</title>
      <link>https://theithollow.com/2019/09/16/kubernetes-desired-state-and-control-loops/</link>
      <pubDate>Mon, 16 Sep 2019 14:05:30 +0000</pubDate>
      <guid>https://theithollow.com/2019/09/16/kubernetes-desired-state-and-control-loops/</guid>
      <description>&lt;p&gt;If you&amp;rsquo;ve just gotten started with Kubernetes, you might be curious to know how the desired state is achieved? Think about it, you pass a YAML file to the API server and magically stuff happens. Not only that, but when disaster strikes (e.g. pod crashes) Kubernetes also makes it right again so that it matches the desired state.&lt;/p&gt;
&lt;p&gt;The mechanism that allows for Kubernetes to enforce this desired state is the control loop. The basics of this are pretty simple. A control loop can be though of in three stages.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
