<?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>Flannel on The IT Hollow</title>
    <link>https://theithollow.com/tags/flannel/</link>
    <description>Recent content in Flannel on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 14 Jan 2019 15:35:36 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/flannel/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Deploy Kubernetes Using Kubeadm - CentOS7</title>
      <link>https://theithollow.com/2019/01/14/deploy-kubernetes-using-kubeadm-centos7/</link>
      <pubDate>Mon, 14 Jan 2019 15:35:36 +0000</pubDate>
      <guid>https://theithollow.com/2019/01/14/deploy-kubernetes-using-kubeadm-centos7/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve been wanting to have a playground to mess around with Kubernetes (k8s) deployments for a while and didn&amp;rsquo;t want to spend the money on a cloud solution like &lt;a href=&#34;https://aws.amazon.com/eks/?nc2=h_m1&#34;&gt;AWS Elastic Container Service for Kubernetes&lt;/a&gt; or &lt;a href=&#34;https://cloud.google.com/kubernetes-engine/&#34;&gt;Google Kubernetes Engine&lt;/a&gt; . While these hosted solutions provide additional features such as the ability to spin up a load balancer, they also cost money every hour they&amp;rsquo;re available and I&amp;rsquo;m planning on leaving my cluster running. Also, from a learning perspective, there is no greater way to learn the underpinnings of a solution than having to deploy and manage it on your own. Therefore, I set out to deploy k8s in my vSphere home lab on some CentOS 7 virtual machines using Kubeadm. I found several articles on how to do this but somehow I got off track a few times and thought another blog post with step by step instructions and screenshots would help others. Hopefully it helps you. Let&amp;rsquo;s begin.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
