![]() ![]() Using the Container Storage Interface in Kubernetes resolves these major issues.Īs more CSI Drivers were created and became production ready, we wanted all Kubernetes users to reap the benefits of the CSI model. ![]() In addition, third-party storage code caused reliability and security issues in core Kubernetes binaries and the code was often difficult (and in some cases impossible) for Kubernetes maintainers to test and maintain. Vendors that wanted to add support for their storage system to Kubernetes (or even fix a bug in an existing volume plugin) were forced to align with the Kubernetes release process. However, adding support for new volume plugins to Kubernetes was challenging. These volume plugins were “in-tree” meaning their code was part of the core Kubernetes code and shipped with the core Kubernetes binaries. Prior to CSI, Kubernetes provided a powerful volume plugin system. Why are we migrating in-tree plugins to CSI? This process allows Kubernetes developers to get feedback, discover and fix issues, iterate on the designs, and deliver high quality, production grade features. Kubernetes features are generally introduced as alpha and moved to beta (and eventually to stable/GA) over subsequent Kubernetes releases. CSI migration was introduced as alpha in Kubernetes v1.14. The Kubernetes in-tree storage plugin to Container Storage Interface (CSI) migration infrastructure is now beta in Kubernetes v1.17. Authors: David Zhu, Software Engineer, Google ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |