1

00:00:00,210 --> 00:00:03,390

In this lecture, we will look at storage classes.



2

00:00:04,510 --> 00:00:11,920

In the previous lectures we discussed about how to create PVS and then create PVCs to claim that storage



3

00:00:11,920 --> 00:00:16,510

and then use the PVCs in the definition files as volumes.



4

00:00:17,470 --> 00:00:22,360

In this case, we create a proxy from a Google cloud persistent desk.



5

00:00:23,240 --> 00:00:30,260

The problem here is that before this PVG is created, you must have created the desk on Google Cloud.



6

00:00:31,100 --> 00:00:37,430

Every time an application requires storage, you have to first manually provisioned the desk on Google



7

00:00:37,430 --> 00:00:43,820

Cloud and then manually create a persistent volume definition file using the same name as that of the



8

00:00:43,820 --> 00:00:45,020

disk that you created.



9

00:00:46,200 --> 00:00:48,900

That's called static provisioning volumes.



10

00:00:49,110 --> 00:00:54,980

It would have been nice if the volume gets provisioned automatically when the application requires it,



11

00:00:55,770 --> 00:00:58,070

and that's where storage clauses come in.



12

00:00:59,080 --> 00:01:06,670

With storage classes, you can define a provisional such as Google storage that can automatically provision



13

00:01:06,670 --> 00:01:11,940

storage on Google Cloud and attach that to parts when a claim is made.



14

00:01:12,760 --> 00:01:15,950

That's called dynamic provisioning of volumes.



15

00:01:16,810 --> 00:01:23,320

You do that by creating a storage class object with the API version set to storage dorkiest, or if



16

00:01:23,860 --> 00:01:28,210

we want one, specify a name and use provisional as cabinet.



17

00:01:28,210 --> 00:01:31,750

Izidor Io slash GCE Despard.



18

00:01:34,220 --> 00:01:41,030

So going back to our original state where we have a pod using a proxy for its storage and the privacy



19

00:01:41,030 --> 00:01:45,260

is bound to APV, we now have a storage class.



20

00:01:46,040 --> 00:01:53,960

So we no longer need the PV definition because the PV and any associated storage is going to be created



21

00:01:53,960 --> 00:01:56,870

automatically when the storage class is created.



22

00:01:58,180 --> 00:02:05,140

For the privacy to use the storage class we defined, we specify the storage class name in the privacy



23

00:02:05,140 --> 00:02:05,770

definition.



24

00:02:08,000 --> 00:02:16,250

That's how the pixie knows which stories class to use next time a PVCs created the storage class associated



25

00:02:16,250 --> 00:02:23,990

with it, uses the defined probationer to provision a new desk with the required size on GCP and then



26

00:02:23,990 --> 00:02:28,730

creates a persistent volume and then binds the PVC to that volume.



27

00:02:29,450 --> 00:02:32,710

So remember that it still creates a Peevey.



28

00:02:32,750 --> 00:02:36,050

It's just that you don't have to manually create PVC anymore.



29

00:02:36,260 --> 00:02:39,320

It's created automatically by the storage class.



30

00:02:40,960 --> 00:02:48,400

We used the GCE provision are to create a volume on Giuseppi, there are many other provisions as well,



31

00:02:48,400 --> 00:02:57,100

such as for Acebes as your file at your desk as pot works scaleable and so on.



32

00:02:58,390 --> 00:03:04,730

With each of these provisions, you can pass in additional parameters, such as the type of desk to



33

00:03:04,810 --> 00:03:12,040

provision, the replication type, etc., these parameters are very specific to the provision that you



34

00:03:12,040 --> 00:03:13,600

are using for Google.



35

00:03:13,600 --> 00:03:14,560

Persist in this.



36

00:03:14,680 --> 00:03:18,540

You can specify the type which could be standard or SSD.



37

00:03:18,970 --> 00:03:24,790

You can specify the replication mode which could be done or regional pre.



38

00:03:26,120 --> 00:03:33,020

So you see, you can create different storage classes, each using different types of desks, for example,



39

00:03:33,020 --> 00:03:39,590

a silver storage class with the standard desks, a gold class with SSD drives, and a platinum class



40

00:03:39,590 --> 00:03:41,900

with SSD drives and replication.



41

00:03:42,590 --> 00:03:45,430

And that's why it's called storage class.



42

00:03:46,040 --> 00:03:54,770

You can create different classes of service next time you create a PC, you can simply specify the class



43

00:03:54,770 --> 00:03:57,560

of storage you need for your volumes.