<?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>Rbac on The IT Hollow</title>
    <link>https://theithollow.com/tags/rbac/</link>
    <description>Recent content in Rbac on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 20 May 2019 14:10:48 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/rbac/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes - Role Based Access</title>
      <link>https://theithollow.com/2019/05/20/kubernetes-role-based-access/</link>
      <pubDate>Mon, 20 May 2019 14:10:48 +0000</pubDate>
      <guid>https://theithollow.com/2019/05/20/kubernetes-role-based-access/</guid>
      <description>&lt;p&gt;As with all systems, we need to be able to secure a Kubernetes cluster so that everyone doesn&amp;rsquo;t have administrator privileges on it. I know this is a serious drag because no one wants to deal with a permission denied error when we try to get some work done, but permissions are important to ensure the safety of the system. Especially when you have multiple groups accessing the same resources. We might need a way to keep those groups from stepping on each other&amp;rsquo;s work, and we can do that through role based access controls.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
