Across Kubernetes Namespace Boundaries: Your Volumes Can Be Shared Now!

Provisioning PVCs from Cross-Namespace Data Sources in Kubernetes

• CSI provisional behavior is divided into five steps
• The feature became Alpha in Kubernetes 1.26
• The scope is only provision of PVC from close namespace data source
• Currently supported data source is volume snapshot and persistent Emporium
• In this feature, we plan to support any volume data source

In our demo, we deployed WordPress input with empty plugins, took a snapshot, and deployed another WordPress in table World Dev from the snapshot

Are you currently storing data to PVCs? Have you found difficulty in sharing the data across Kubernetes namespace? If yes, this is the talk for you. Kubernetes supports provisioning volumes from a variety of data sources, like PVCs, VolumeSnapshots, and CRDs (beta in Kubernetes 1.24). However, data sources are restricted to exist in the same namespace. Due to this restriction, sharing data between namespaces has been difficult. As a result, use cases like copying volumes from a production namespace to a development namespace for testing and copying golden images in one namespace to other consuming namespaces can't be achieved without administrators' help. To solve this issue, provision of volumes from cross-namespace data sources (KEP-3294) is planned to be supported as alpha feature in Kubernetes 1.26. This talk will explain how users can use this feature and how it works with demos.