<?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>Attach on The IT Hollow</title>
    <link>https://theithollow.com/tags/attach/</link>
    <description>Recent content in Attach on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 10 Mar 2020 18:00:00 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/attach/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tanzu Mission Control - Attach Clusters</title>
      <link>https://theithollow.com/2020/03/10/tanzu-mission-control-attach-clusters/</link>
      <pubDate>Tue, 10 Mar 2020 18:00:00 +0000</pubDate>
      <guid>https://theithollow.com/2020/03/10/tanzu-mission-control-attach-clusters/</guid>
      <description>&lt;p&gt;What do you do if you&amp;rsquo;ve already provisioned some Kubernetes clusters before you got Tanzu Mission Control? Or maybe you&amp;rsquo;re inheriting some new clusters through an acquisition? Or a new team came on board and were using their own installation? Whatever the case, Tanzu Mission Control will let you manage a conformant Kubernetes cluster but you must first attach it.&lt;/p&gt;
&lt;h2 id=&#34;attach-an-existing-cluster&#34;&gt;Attach An Existing Cluster&lt;/h2&gt;
&lt;p&gt;For this example, I&amp;rsquo;ll be attaching a pre-existing Kubernetes cluster on vSphere infrastructure. This cluster was deployed via kubeadm as documented in this previous article about deploying &lt;a href=&#34;https://theithollow.com/2020/01/08/deploy-kubernetes-on-vsphere/&#34;&gt;Kubernetes on vSphere&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
