<?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>Vcp on The IT Hollow</title>
    <link>https://theithollow.com/tags/vcp/</link>
    <description>Recent content in Vcp on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 14 Apr 2020 14:05:00 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/vcp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>In-tree vs Out-of-tree Kubernetes Cloud Providers</title>
      <link>https://theithollow.com/2020/04/14/in-tree-vs-out-of-tree-kubernetes-cloud-providers/</link>
      <pubDate>Tue, 14 Apr 2020 14:05:00 +0000</pubDate>
      <guid>https://theithollow.com/2020/04/14/in-tree-vs-out-of-tree-kubernetes-cloud-providers/</guid>
      <description>&lt;p&gt;VMware offers a Kubernetes Cloud Provider that allows Kubernetes (k8s) administrators to manage parts of the vSphere infrastructure by interacting with the Kubernetes Control Plane. Why is this needed? Well, being able to spin up some new virtual disks and attaching them to your k8s cluster is especially useful when your pods need access to persistent storage for example.&lt;/p&gt;
&lt;p&gt;The Cloud providers (AWS, vSphere, Azure, GCE) obviously differ between vendors. Each cloud provider has different functionality that might be exposed in some way to the Kubernetes control plane. For example, Amazon Web Services provides a load balancer that can be configured with k8s on demand if you are using the AWS provider, but vSphere does not (unless you&amp;rsquo;re using NSX).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
