This section of documentation covers the use of the managed Kubernetes Azure service AKS. For information on the installation of StorageOS with vanilla Kubernetes in Azure VMs, please refer to the Kubernetes standard installation procedure.
AKS and StorageOS
AKS deployment of Kubernetes uses Ubuntu by default with an optimized kernel.
All versions of Ubuntu with a kernel version later than
meets the StorageOS prerequisites.
Visit the best practices section to install StorageOS for production clusters.
Kubernetes with StorageOS
Kubernetes and StorageOS communicate with each other to perform actions such as creation, deletion or mounting volumes. The standard communication procedure uses REST API calls. However, StorageOS also implements communication using CSI. By using CSI, Kubernetes and StorageOS communicate over a Unix domain socket. That socket is handled by the Kubelet in the Host.
CSI (Container Storage Interface) Note
CSI is the future standard that enables storage drivers to release on their own schedule. This allows storage vendors to upgrade, update, and enhance their drivers without the need to update Kubernetes source code, or follow Kubernetes release cycles.
StorageOS current installation procedure communicates with AKS Kubernetes Master nodes using CSI. A native storage driver installation procedure will be released shortly.
Check out the status of the CSI release cycle in relation with Kubernetes on the CSI project page.
StorageOS leverages labels on PVCs to apply features to StorageOS volumes. However, StorageOS doesn’t
have these labels set when using CSI. Therefore, default feature labels
storageos.com/*) must be defined on the Kubernetes StorageClass parameters.
Multiple StorageClasses can be defined with different parameters. The
StorageOS CLI can also manipulate
volume labels or create rules to
add/delete labels on StorageOS volumes.