FlexVolume
Glossary Page
FlexVolume was an interface for creating external volume plugins in Kubernetes. However, it has been deprecated and replaced by the Container Storage Interface (CSI), which addresses several issues with FlexVolume. FlexVolumes required root access to install driver binaries and dependencies on host machines, and it was challenging to maintain them. In contrast, CSI drivers provide a standardized API, are more flexible, and more manageable. Therefore, the Kubernetes Storage Special Interest Group (SIG) suggests implementing CSI drivers instead of FlexVolumes. More information about FlexVolume can be found in the Kubernetes documentation, and the Volume Plugin FAQ for Storage Vendors provides additional details.
https://kubernetes.io/docs/reference/glossary/?all=true
Latest Webinars
Latest Articles
Bundesliga fans on the move: What Motion Data reveals about football culture
The article explores how T‑Systems’ Motion Data leverages anonymized mobile network information to reveal real‑world fan behavior in the 2024/25 Bundesliga season. It highlights how supporters travel to home and away matches, the demographic composition of stadium audiences, and which clubs attract the largest crowds—including surprising cross‑border dynamics. By transforming assumptions into measurable insights, Motion Data enables clubs, cities, and event organizers to improve mobility planning, enhance stadium operations, and design more targeted fan engagement strategies.
Read more
Tino Bliesener
Jan 28, 2026
Flex: Electronic Control Unit (ECU)
Flex partnered with T-Systems to migrate ECU data exchange to Catena-X, enabling secure, multiregional, real-time validation across global production sites. Using T-Systems’ Connect & Integrate solution, Flex achieved end-to-end integration, API and Cofinity-X interface testing, and a fully validated production setup. This scalable dataspace foundation now supports future use cases including Product Carbon Footprint, Certificate Management, Battery Pass, and global traceability, while maintaining full data sovereignty.
Read more
Andrea Garcia
Jan 16, 2026
Sovereign connectivity: Automating access in dataspaces
Sovereign connectivity in dataspaces requires automating network access to ensure security, compliance, and operational scale. In the Data Intelligence Hub, we replace manual firewall updates with a declarative, Kubernetes-native model using Custom Resource Definitions (CRDs). Customers define their allowed IP ranges through a self-service portal, which generates an IpAccessPolicy object representing the desired state. A controller then reconciles this state with the underlying infrastructure, automatically updating Kubernetes Ingress configurations and preventing drift. This architecture ensures auditability, validates inputs before enforcement, and keeps network access aligned with the principles of data sovereignty across multi-tenant environments.
Read more
Mohamed Radwan
Jan 15, 2026