<?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>Vsphere7 on The IT Hollow</title>
    <link>https://theithollow.com/tags/vsphere7/</link>
    <description>Recent content in Vsphere7 on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 13 May 2021 14:45:54 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/vsphere7/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>vSphere 7 with Tanzu Updates</title>
      <link>https://theithollow.com/2021/05/13/vsphere-7-with-tanzu-updates/</link>
      <pubDate>Thu, 13 May 2021 14:45:54 +0000</pubDate>
      <guid>https://theithollow.com/2021/05/13/vsphere-7-with-tanzu-updates/</guid>
      <description>&lt;p&gt;At some point, you&amp;rsquo;ll be faced with an upgrade request. New Kubernetes features, new security patches, or just to maintain your support. A vSphere 7 with Tanzu deployment has several components that may need to be updated and most of which can be updated independently of one another. In this post we&amp;rsquo;ll walk through an update to vSphere, then update the Supervisor namespace, and then finally the Tanzu Kubernetes cluster.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Deploying Tanzu Kubernetes Clusters on vSphere 7</title>
      <link>https://theithollow.com/2020/09/09/deploying-tanzu-kubernetes-clusters-on-vsphere-7/</link>
      <pubDate>Wed, 09 Sep 2020 14:15:00 +0000</pubDate>
      <guid>https://theithollow.com/2020/09/09/deploying-tanzu-kubernetes-clusters-on-vsphere-7/</guid>
      <description>&lt;p&gt;This post will focus on deploying Tanzu Kubernetes Grid (TKG) clusters in your vSphere 7 with Tanzu environment. These TKG clusters are the individual Kubernetes clusters that can be shared with teams for their development purposes.&lt;/p&gt;
&lt;p&gt;I know what you&amp;rsquo;re thinking. Didn&amp;rsquo;t we already create a Kubernetes cluster when we setup our Supervisor cluster? The short answer is yes. However the Supervisor cluster is a unique Kubernetes cluster that probably shouldn&amp;rsquo;t be used for normal workloads. We&amp;rsquo;ll discuss this in more detail in a follow-up post. For now, let&amp;rsquo;s focus on how to create them, and later we&amp;rsquo;ll discuss when to use them vs the Supervisor cluster.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
