We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

What’s next after CSI? An introduction to Object Storage for Kubernetes

Formal Metadata

Title
What’s next after CSI? An introduction to Object Storage for Kubernetes
Subtitle
Moving beyond file and block storage in Kubernetes
Title of Series
Number of Parts
637
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Kubernetes graduated Container Storage Interface (CSI) to GA status in v1.13. Since CSI’s origin, it has evolved to support a large number of vendors and storage formats. It has brought the industry together in consensus about the best practices in storage. However, CSI’s major limitation is that it only supports Block and File storage. The rapid growth of Object storage means that a growing share of the ecosystem is currently using ad-hoc solutions to leverage this new technology. Object storage is a fundamentally different paradigm where data is accessed over the network rather than locally. It allows applications to remain stateless while offloading state into a black box over the network. Object storage is the key enabler for cloud migration. This paradigm, however, does not have a standard mechanism for consumption in Kubernetes. COSI fundamentally exists to enable the natural consumption of object storage with Kubernetes. In this talk, we discuss our efforts in bringing object storage into the forefront of Kubernetes and introduce the Container Object Storage Interface (COSI) and cover: - Why COSI is needed for Kubernetes - Best practices for using COSI - Designing apps to leverage COSI - The COSI architecture, and how to contribute to the project.