<?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>Flask on The IT Hollow</title>
    <link>https://theithollow.com/tags/flask/</link>
    <description>Recent content in Flask on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 26 May 2020 15:05:00 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/flask/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes Validating Admission Controllers</title>
      <link>https://theithollow.com/2020/05/26/kubernetes-validating-admission-controllers/</link>
      <pubDate>Tue, 26 May 2020 15:05:00 +0000</pubDate>
      <guid>https://theithollow.com/2020/05/26/kubernetes-validating-admission-controllers/</guid>
      <description>&lt;p&gt;Hey! Who deployed this container in our shared Kubernetes cluster without putting resource limits on it? Why don&amp;rsquo;t we have any labels on these containers so we can report for charge back purposes? Who allowed this image to be used in our production cluster?&lt;/p&gt;
&lt;p&gt;If any of the questions above sound familiar, its probably time to learn about Validating Admission Controllers.&lt;/p&gt;
&lt;h2 id=&#34;validating-admission-controllers---the-theory&#34;&gt;Validating Admission Controllers - The Theory&lt;/h2&gt;
&lt;p&gt;Admission Controllers are used as a roadblocks before objects are deployed to a Kubernetes cluster. The examples from the section above are common rules that companies might want to enforce before objects get pushed into a production Kubernetes cluster. These admission controllers can be from custom code that you&amp;rsquo;ve written yourself, or a third party admission controller. A common open-source project that manages admission control rules is &lt;a href=&#34;https://www.openpolicyagent.org/&#34;&gt;Open Policy Agent (OPA)&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
