Cloud Native Short Take - Kubernetes Block Storage

hello everyone welcome to the latest rxm cloud native short take my name is christian luxena and today we'll take short take the rxm kubernetes block storage module in this module we introduce the container storage initiative we'll then talk about the evolution of dynamic storage provisioning for kubernetes we'll present examples and use cases of csi plugins and will demonstrate the use of csi plugins in kubernetes for this short takes demo i'm going to demonstrate the steps required to enable dynamic block storage provisioning for my cluster using aws ebs my cluster consists of a single node kubernetes cluster and in order to set up dynamic provisioning i first need to set up my csi plugin a csi plugin on kubernetes provides a provisioner which runs on the cluster it's the provisioner's job to realize my requests for storage using the chosen backend for my storage in this case aws ebs to do this the provisioner must have credentials which are ideally provided by a kubernetes secret for aws cbs i needed to provide a valid api identity and access key which i've already loaded onto my cluster next i need to deploy the provisioner itself and its supporting components the provisioner itself runs as pods on the cluster with a managing controller running as a deployment and a daemon set running a pod on every node in the cluster that ensures the created volumes are properly attached to each node our back elements are also included to ensure the provisioner can communicate with the api server finally a csi driver resource enables the kubernetes persistent volume subsystem to identify the driver with the provisioner deployed i need to create a storage class resource that enables my persistent volume claims to use the provisioner this storage class identifies the provisioner using the name established by the csi driver resource created earlier i'll go ahead and apply it to my cluster now now that i have my storage class in place i can create a pvc that uses the ebs csi driver the key line in this pvc is the storage class name the storage class name refers to my ebs sc storage class which uses the aws ebs csi driver once i apply this pvc to the cluster it will soon bind to a brand new pv automatically go ahead and establish a watch for persistent volumes and persistent volume claims and i will then apply my pvc we can see the pvc is created it's in a pending state and shortly after a persistent volume is created during this process the provisioner reaches out to the ebs subsystem on aws itself tells it to create a pv or rather tells it to create a block storage device on ebs which best fulfills my request for storage depending on the storage back end you might see slight differences between your request and the provisioned pv aws ebs has a minimum volume size of one gigabyte so my initial request for 512 megabytes was fulfilled with a one gigabyte volume and that's it any pvc applied to the cluster using the storage class will automatically provision an ebs block storage device for itself the use of block storage devices on kubernetes is just one of the things you'll learn in the kubernetes block storage module from rxm you can create your own customized kubernetes courses with this and many other modules using the courseware builder on the rxm website rxm.com once you get to the website go under courses and you can find the custom courseware builder in the custom course builder you can scroll down and find the block storage module under kubernetes drag it over to your custom course and along with other modules in the rxm catalog you can create a customized kubernetes course that fits your needs that's our cloud native short take on the kubernetes block storage module thank you for watching [Music]