October 6, 2019

219 words 2 mins read

VMware SIG: Cloud Provider Moving Out of Tree+CSI - What it Means to Users

VMware SIG: Cloud Provider Moving Out of Tree+CSI - What it Means to Users

Kubernetes cloud providers and volume plugins used to be "in-tree" meaning that their source code is included in the main Kubernetes repo. They were compiled in, and shipped only in a Kubernetes relea …

Talk Title VMware SIG: Cloud Provider Moving Out of Tree+CSI - What it Means to Users
Speakers Fabio Rapposelli (Staff Engineer 2, VMware), Steven Wong (Open Source Software Engineer, VMware)
Conference KubeCon + CloudNativeCon
Conf Tag
Location Shanghai, China
Date Jun 23-26, 2019
URL Talk Page
Slides Talk Slides
Video

Kubernetes cloud providers and volume plugins used to be “in-tree” meaning that their source code is included in the main Kubernetes repo. They were compiled in, and shipped only in a Kubernetes release. The drawbacks of this monolithic approach were that Kubernetes was larger than needed, and feature + patch activity was locked to Kubernetes release schedules. Going forward, new features are exclusive to the new replacements: an out-of-tree vSphere cloud provider + a CSI storage plugin. Legacy implementations remain for the short term but destined are for deprecation. Agenda: - Deep Dive : Install and configure of out-of-tree cloud provider + CSI storage - Migration options for current users This session will be useful to: - Users running Kubernetes on VMware infrastructure - Authors of installers and Kubernetes distributions which target the vSphere platform

comments powered by Disqus