<?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>Tls on The IT Hollow</title>
    <link>https://theithollow.com/tags/tls/</link>
    <description>Recent content in Tls on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 22 Sep 2021 13:31:53 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/tls/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Configure a Private Registry for Tanzu Kubernetes Clusters</title>
      <link>https://theithollow.com/2021/09/22/configure-a-private-registry-for-tanzu-kubernetes-clusters/</link>
      <pubDate>Wed, 22 Sep 2021 13:31:53 +0000</pubDate>
      <guid>https://theithollow.com/2021/09/22/configure-a-private-registry-for-tanzu-kubernetes-clusters/</guid>
      <description>&lt;p&gt;A really common task after deploying a Kubernetes cluster is to configure it to use a container registry where the container images are stored. A Tanzu Kubernetes Cluster (TKC) is no exception to this rule. vSphere 7 with Tanzu comes with an embedded harbor registry that can be used, but in many cases you all ready have your own container registry and so you&amp;rsquo;d like to continue using that instead.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
