<?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>Harbor on The IT Hollow</title>
    <link>https://theithollow.com/tags/harbor/</link>
    <description>Recent content in Harbor on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 04 Jan 2021 21:50:57 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/harbor/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Enable the Harbor Registry on vSphere 7 with Tanzu</title>
      <link>https://theithollow.com/2021/01/04/enable-the-harbor-registry-on-vsphere-7-with-tanzu/</link>
      <pubDate>Mon, 04 Jan 2021 21:50:57 +0000</pubDate>
      <guid>https://theithollow.com/2021/01/04/enable-the-harbor-registry-on-vsphere-7-with-tanzu/</guid>
      <description>&lt;p&gt;Your Kubernetes clusters are up and running on vSphere 7 with Tanzu and you can&amp;rsquo;t wait to get started on your first project. But before you get to that, you might want to enable the Harbor registry so that you can privately store your own container images and use them with your clusters. Luckily, in vSphere 7 with Tanzu, the Harbor project has been integrated into the solution. You just have to turn it on and set it up.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Use a Private Registry with Kubernetes</title>
      <link>https://theithollow.com/2020/03/03/use-a-private-registry-with-kubernetes/</link>
      <pubDate>Tue, 03 Mar 2020 21:09:07 +0000</pubDate>
      <guid>https://theithollow.com/2020/03/03/use-a-private-registry-with-kubernetes/</guid>
      <description>&lt;p&gt;Most of the blog posts I write about Kubernetes have examples using publicly available images from public image registries like DockerHub or Google Container Registry. But in the real world, companies use private registries for storing their container images. There are a list of reasons why you might want to do this including:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Custom code is inside the container such as business logic or other intellectual property.&lt;/li&gt;
&lt;li&gt;On-premises private repos provide solutions to bandwidth or firewall restrictions.&lt;/li&gt;
&lt;li&gt;Custom scanning software is being integrated for vulnerability management.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In this post, we&amp;rsquo;ll setup our Kubernetes cluster to be able to use a private container registry.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
