We actually went ahead and implemented CreateVolume RPC of the controller service form the CSI plugin. As described in the CSI specification, CreateVolume method/RPC from controller service gets called as soon as a volume is requested from Container Orchestrator, in our case Kubernetes.
We also looked, in detail, into how the input object to create volume request looks like. For example AccessMode, AccessType etc.
CSI Specification:
github.com/container-storage-...
DO CSI Plugin:
github.com/digitalocean/csi-d...
bsos GitHub repo:
github.com/viveksinghggits/bsos
Web:
viveksingh.dev/
00:00 Introduction
00:22 Agenda
01:34 CreateVolume RPC
02:30 Verify that CreateVolume or Controller Svc is being called (Creating SC)
07:00 Creating PVC resource and testing the plugin
11:34 Implement Create Volume method
11:51 Looking Input request struct of csi.CreateVolumeRequest
12:00 Name
12:50 CapacityRange
14:31 VolumeCapabilities (accessMode and accessType)
16:24 VolumeContentSource
17:47 Accessibility Requirements
19:55 Implement CreateVolume
31:17 Forming the request to call DO create volume API
37:05 Add/Init storage client as field in Driver struct
41:04 Call DO API to create the volume
43:56 Pass DO token from controller plugin manifest
48:20 Re-Build and deploy to test creation of PVC
50:56 Update SA permissions to patch and create Events
51:34 Re-Build and deploy to test create of PVC
51:57 Create Volume request failed
53:18 Debugging/Fixing the problem
54:47 Re-Build and deploy again to test things
56:42 Volume was provisioned successfully
56:56 Size conversion issue
58:05 Deploy a pod to mount the volume to test the things
01:01:59 Describe the pod to look at the events
01:02:55 Describe the pod again to show event that attachment failed
01:03:42 Like, Share and Subscribe
28 июн 2024
