<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>helm on ropnop blog</title>
    <link>https://blog.ropnop.com/tags/helm/</link>
    <description>Recent content in helm on ropnop blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <managingEditor>rflathers@gmail.com (ropnop)</managingEditor>
    <webMaster>rflathers@gmail.com (ropnop)</webMaster>
    <lastBuildDate>Mon, 28 Jan 2019 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://blog.ropnop.com/tags/helm/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Attacking Default Installs of Helm on Kubernetes</title>
      <link>https://blog.ropnop.com/attacking-default-installs-of-helm-on-kubernetes/</link>
      <pubDate>Mon, 28 Jan 2019 00:00:00 +0000</pubDate>
      <author>rflathers@gmail.com (ropnop)</author>
      <guid>https://blog.ropnop.com/attacking-default-installs-of-helm-on-kubernetes/</guid>
      <description>Default installations of Helm on Kubernetes can make it trivial for attackers to escalate to cluster admin. In this post I&amp;rsquo;ll demonstrate how.</description>
    </item>
    
  </channel>
</rss>