<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Matt Silverlock</title>
    <description/>
    <link>https://speakerdeck.com/elithrar</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/elithrar.rss"/>
    <lastBuildDate>2019-11-28 05:11:04 -0500</lastBuildDate>
    <item>
      <title>The Myth of the Monocluster (KubeCon NA, 2019)</title>
      <description>Building out a single monolithic Kubernetes cluster and trying to migrate all the things rarely, if ever, works out, and Kubernetes doesn't change that. It becomes harder to gather non-conflicting requirements, or avoid scope creep as new teams have what seem like reasonable asks (to them). Not to mention the technical challenges &amp; increased blast radius of a big cluster.

How can we start with smaller teams, help them migrate and operationalize their clusters, learn from the inevitable mistakes, document the shortcuts, and use that as the framework for future teams?

Presented at KubeCon North America, 2019: https://kccncna19.sched.com/event/Uady/the-myth-of-the-monocluster-matt-silverlock-google</description>
      <media:content url="https://files.speakerdeck.com/presentations/a5440260f4ff40b4a47d742937931969/preview_slide_0.jpg?14312573" type="image/jpeg" medium="image"/>
      <content:encoded>Building out a single monolithic Kubernetes cluster and trying to migrate all the things rarely, if ever, works out, and Kubernetes doesn't change that. It becomes harder to gather non-conflicting requirements, or avoid scope creep as new teams have what seem like reasonable asks (to them). Not to mention the technical challenges &amp; increased blast radius of a big cluster.

How can we start with smaller teams, help them migrate and operationalize their clusters, learn from the inevitable mistakes, document the shortcuts, and use that as the framework for future teams?

Presented at KubeCon North America, 2019: https://kccncna19.sched.com/event/Uady/the-myth-of-the-monocluster-matt-silverlock-google</content:encoded>
      <pubDate>Wed, 20 Nov 2019 00:00:00 -0500</pubDate>
      <link>https://speakerdeck.com/elithrar/the-myth-of-the-monocluster-kubecon-na-2019</link>
      <guid>https://speakerdeck.com/elithrar/the-myth-of-the-monocluster-kubecon-na-2019</guid>
    </item>
  </channel>
</rss>
