In this lecture, we will look at storage classes.
In the previous lectures we discussed about how to create PVS and then create PVCs to claim that storage
and then use the PVCs in the definition files as volumes.
In this case, we create a proxy from a Google cloud persistent desk.
The problem here is that before this PVG is created, you must have created the desk on Google Cloud.
Every time an application requires storage, you have to first manually provisioned the desk on Google
Cloud and then manually create a persistent volume definition file using the same name as that of the
disk that you created.
That's called static provisioning volumes.
It would have been nice if the volume gets provisioned automatically when the application requires it,
and that's where storage clauses come in.
With storage classes, you can define a provisional such as Google storage that can automatically provision
storage on Google Cloud and attach that to parts when a claim is made.
That's called dynamic provisioning of volumes.
You do that by creating a storage class object with the API version set to storage dorkiest, or if
we want one, specify a name and use provisional as cabinet.
Izidor Io slash GCE Despard.
So going back to our original state where we have a pod using a proxy for its storage and the privacy
is bound to APV, we now have a storage class.
So we no longer need the PV definition because the PV and any associated storage is going to be created
automatically when the storage class is created.
For the privacy to use the storage class we defined, we specify the storage class name in the privacy
definition.
That's how the pixie knows which stories class to use next time a PVCs created the storage class associated
with it, uses the defined probationer to provision a new desk with the required size on GCP and then
creates a persistent volume and then binds the PVC to that volume.
So remember that it still creates a Peevey.
It's just that you don't have to manually create PVC anymore.
It's created automatically by the storage class.
We used the GCE provision are to create a volume on Giuseppi, there are many other provisions as well,
such as for Acebes as your file at your desk as pot works scaleable and so on.
With each of these provisions, you can pass in additional parameters, such as the type of desk to
provision, the replication type, etc., these parameters are very specific to the provision that you
are using for Google.
Persist in this.
You can specify the type which could be standard or SSD.
You can specify the replication mode which could be done or regional pre.
So you see, you can create different storage classes, each using different types of desks, for example,
a silver storage class with the standard desks, a gold class with SSD drives, and a platinum class
with SSD drives and replication.
And that's why it's called storage class.
You can create different classes of service next time you create a PC, you can simply specify the class
of storage you need for your volumes.