Youtube daily report Sep 25 2018

♪ OPENING MUSIC ♪

* RIFLE FIRING *

WELCOME BACK TO

THIS IS RIFLE COUNTRY

AND I'M EXCITED TO

TALK ABOUT THIS RIFLE RIGHT HERE

AND THE REASON IS

IS BECAUSE I REALLY LIKE IT

I'VE HAD THIS GUN

FOR AWHILE NOW

THIS IS THE WEATHERBY

MODEL SUB MOA

AND YOU SAID, HANG ON A SECOND PAUL

I JUST WENT TO THEIR WEBSITE

AND THEY DON'T HAVE A SUB MOA RIFLE LISTED

NO, THEY CHANGED THE NAME OF IT

BUT THE RIFLE IS STILL THE RIFLE

THIS IS A .308 BOLT ACTION RIFLE

AND

THIS IS ONE OF WEATHERBY'S

LESS EXPENSIVE MODELS

SHALL WE SAY

IF YOU'VE EVER PRICED A WEATHERBY RIFLE

THEY'RE NOT CHEAP

THEY'RE NOT REALLY ENTRY-LEVEL GUNS

BUT THIS GUN WAS ACTUALLY

DESIGNED TO BE A LOWER PRICE POINT

FOR THE WEATHERBY FAN

I'M ALSO EXCITED

TO TALK ABOUT THIS WEATHERBY RIFLE

BECAUSE, WHY

WELL

IF YOU ARE IN THE GUN CULTURE

AND YOU'RE IN-THE-KNOW

YOU SHOULD KNOW THAT WEATHERBY

HAS MOVED THEIR OPERATIONS

THEIR CORPORATE HEADQUARTERS

AND THEIR MANUFACTURING

RIGHT HERE TO WYOMING

THAT'S RIGHT

AND WE'RE LOOKING FORWARD

TO THEIR GRAND OPENING VERY SOON

SO THAT IS A VERY COOL THING

ALRIGHT, WHAT DO WE HAVE

ON THIS BOLT ACTION RIFLE

WE HAVE A HEAVY MATCH BARREL

OKAY

NOT TOO HEAVY

BUT HEAVIER THAN THE STANDARD

WE HAVE A

FIBERGLASS STOCK

AND IF YOU LOOK AT THE STOCK

YES, I DID DURACOAT THE STOCK

I PUT THE CAMOUFLAGE

YOU KNOW, THE VARIOUS GREEN

CAMOUFLAGE ON THERE

WE'VE GOT A HARRIS BIPOD

WE'VE GOT A NYLON SLING

AND THEN WE HAVE A

A PAD/BUTT POUCH ON THE REAR

NOW ALL OF THESE ACCESSORIES

ARE SUPER EASY TO FIND

JUST GO TO BROWNELLS

AND YOU CAN FIND STUFF LIKE THAT

ON TOP, I HAVE A LEUPOLD SCOPE

BUT THIS IS A LITTLE DIFFERENT

THAN THE NORM

THIS ACTUALLY IS A

VARIABLE POWER

IT'S A 1.5 TO 5 POWER RIFLE SCOPE

AND

A LOT OF FOLKS SAY, WELL

PAUL, THAT'S A .308 RIFLE

THAT'S A LONG-RANG RIFLE

IT'S A PRECISION GUN

WHY WOULD YOU ONLY PUT

A 5 POWER SCOPE ON IT

WELL, DEPENDING ON WHERE YOU LIVE

YOU MAY NOT BE ABLE TO SHOOT

OR HAVE AN OPPORTUNITY

TO SHOOT YOUR RIFLE

BEYOND 200 YARDS

BEYOND 3 MAYBE EVEN 400 YARDS

IF YOU LIVE EAST OF THE MISSISSIPPI

A SHOT BEYOND 300 YARDS

IS PRETTY RARE

SO IF I'M GOING TO BE SHOOTING

A RIFLE LIKE THIS

IN THE 1 TO 2 TO 300 YARD RANGE

DO I NEED A 12 OR 15 POWER SCOPE

NO, I REALLY DON'T

SO, WHAT I DID

JUST TO PROVE A POINT

I ACTUALLY PUT THIS

LOWER POWER SCOPE ON HERE

AND YES, BECAUSE I KNOW THE DOPE

AND I KNOW THE ADJUSTMENTS

I CAN HIT TARGETS OUT TO 500 YARDS

WITH THIS SCOPE

AND I HAVE QUITE OFTEN

NOW WHAT AM I GOING TO

FEED THIS RIFLE TODAY

I'M GOING TO FEED IT

THE NOSLER SSA

THIS IS A 168 GRAIN

BOAT TAILED HOLLOW POINT

THIS GUN RIGHT HERE

REALLY SEEMS TO LIKE THIS AMMUNITION

I CAN SHOOT SUB MOA OR

SUB INCH GROUPS

AT 100 YARDS WITH THIS GUN, EVEN

THOUGH IT ONLY HAS A 5 POWER SCOPE

ALL DAY LONG, EVERY DAY

I WANTED TO TAKE A SECOND

AND MENTION SOMETHING

THAT A LOT OF PEOPLE

DON'T THINK ABOUT WHEN

THEY GO TO THE RANGE

YOU GO TO THE RANGE

AND WHAT DO YOU HAVE

YOU'VE GOT, WELL, YOUR GUN

YOUR RIFLE, YOUR PISTOL

YOUR SHOTGUN, WHATEVER

YOU'VE GOT YOUR RANGE BAG

AND IT'S FULL OF AMMO

YOU MIGHT HAVE YOUR EAR PROTECTION

EYE PROTECTION, ALL THAT

AND YOU'RE LIKE, I'M GOOD TO GO

DO YOU HAVE A TRAUMATIC MEDICAL KIT

THIS KIT RIGHT HERE

I PULLED IT OUT OF THE RANGE BAG

IT SITS IN THE SIDE POCKET

OR ACTUALLY THE END POCKET

OF MY RANGE BAG

AND IT'S ALWAYS THERE

EVERY TIME I GO TO THE RANGE

IT'S THERE

IT HAS A TOURNIQUET

IT HAS A PRESSURE DRESSING

IT HAS GAUZE

IT HAS LOTS OF OTHER THINGS

TO DEAL WITH

EMERGENCY BLEEDING SITUATIONS

I'M NOT JUST TALKING ABOUT

BANDAIDS, I'M NOT TALKING ABOUT

THAT LITTLE

SQUARE PLASTIC BOX

THAT HAS A COUPLE OF BANDAIDS

AND A LITTLE ALCOHOL WIPE

AND SOMETHING

I'M TALKING

WHAT DO YOU DO

WHEN SOMEONE IS

BLEEDING HEAVILY ON THE RANGE

YOU'RE LIKE UN-UH

WE'RE ALL SAFE PAUL

WE'RE ALL SAFE SHOOTERS

WE KNOW THE RULES

THAT WILL NEVER HAPPEN

YES IT WILL

I'VE BEEN ON THE RANGE TWICE

TWO DIFFERENT OCCASIONS

WHEN PEOPLE WERE ON THE RANGE

WITH ME

AND THEY SUSTAINED

TRAUMATIC BLEEDING INJURIES

AND I HAD TO HELP THEM

AND ASSIST THEM

I NEVER EVER GO TO THE RANGE

WITHOUT A KIT

WE SELL THE

POCKET LIFE SAVER KITS

THIS IS A STUDENT KIT

IT'S A SMALL ONE

WE HAVE THE LARGER KITS

YOU CAN PUT IN A CARGO POCKET

CARRY IT WITH YOU

YOU SHOULD ALWAYS HAVE

TRAUMATIC MEDICAL GEAR

WITH YOU

WHEN YOU GO TO THE RANGE, AND

WHEN YOU GO TO THE RANGE

MAKE SURE THAT THE OTHER PEOPLE

WHO ARE WITH YOU

KNOW WHERE THE MEDICAL GEAR IS

AND HOW TO USE IT

BECAUSE IT MIGHT BE YOU THAT'S BLEEDING

For more infomation >> Weatherby Sub MOA .308 Bolt Action - This is Rifle Country S1 Ep4 - Duration: 5:34.

-------------------------------------------

Kia cee'd 1.0 T-GDI *Budget Topper! Rijklaar GT-Plusline Zie mededelingen - Duration: 1:10.

For more infomation >> Kia cee'd 1.0 T-GDI *Budget Topper! Rijklaar GT-Plusline Zie mededelingen - Duration: 1:10.

-------------------------------------------

Peugeot 208 1.2 VTi Urban Soul | Airco | LM velgen | Bluetooth | Trekhaak | PDC | Cruise | - Duration: 1:06.

For more infomation >> Peugeot 208 1.2 VTi Urban Soul | Airco | LM velgen | Bluetooth | Trekhaak | PDC | Cruise | - Duration: 1:06.

-------------------------------------------

Weatherby Sub MOA .308 Bolt Action - This is Rifle Country S1 Ep4 - Duration: 5:34.

♪ OPENING MUSIC ♪

* RIFLE FIRING *

WELCOME BACK TO

THIS IS RIFLE COUNTRY

AND I'M EXCITED TO

TALK ABOUT THIS RIFLE RIGHT HERE

AND THE REASON IS

IS BECAUSE I REALLY LIKE IT

I'VE HAD THIS GUN

FOR AWHILE NOW

THIS IS THE WEATHERBY

MODEL SUB MOA

AND YOU SAID, HANG ON A SECOND PAUL

I JUST WENT TO THEIR WEBSITE

AND THEY DON'T HAVE A SUB MOA RIFLE LISTED

NO, THEY CHANGED THE NAME OF IT

BUT THE RIFLE IS STILL THE RIFLE

THIS IS A .308 BOLT ACTION RIFLE

AND

THIS IS ONE OF WEATHERBY'S

LESS EXPENSIVE MODELS

SHALL WE SAY

IF YOU'VE EVER PRICED A WEATHERBY RIFLE

THEY'RE NOT CHEAP

THEY'RE NOT REALLY ENTRY-LEVEL GUNS

BUT THIS GUN WAS ACTUALLY

DESIGNED TO BE A LOWER PRICE POINT

FOR THE WEATHERBY FAN

I'M ALSO EXCITED

TO TALK ABOUT THIS WEATHERBY RIFLE

BECAUSE, WHY

WELL

IF YOU ARE IN THE GUN CULTURE

AND YOU'RE IN-THE-KNOW

YOU SHOULD KNOW THAT WEATHERBY

HAS MOVED THEIR OPERATIONS

THEIR CORPORATE HEADQUARTERS

AND THEIR MANUFACTURING

RIGHT HERE TO WYOMING

THAT'S RIGHT

AND WE'RE LOOKING FORWARD

TO THEIR GRAND OPENING VERY SOON

SO THAT IS A VERY COOL THING

ALRIGHT, WHAT DO WE HAVE

ON THIS BOLT ACTION RIFLE

WE HAVE A HEAVY MATCH BARREL

OKAY

NOT TOO HEAVY

BUT HEAVIER THAN THE STANDARD

WE HAVE A

FIBERGLASS STOCK

AND IF YOU LOOK AT THE STOCK

YES, I DID DURACOAT THE STOCK

I PUT THE CAMOUFLAGE

YOU KNOW, THE VARIOUS GREEN

CAMOUFLAGE ON THERE

WE'VE GOT A HARRIS BIPOD

WE'VE GOT A NYLON SLING

AND THEN WE HAVE A

A PAD/BUTT POUCH ON THE REAR

NOW ALL OF THESE ACCESSORIES

ARE SUPER EASY TO FIND

JUST GO TO BROWNELLS

AND YOU CAN FIND STUFF LIKE THAT

ON TOP, I HAVE A LEUPOLD SCOPE

BUT THIS IS A LITTLE DIFFERENT

THAN THE NORM

THIS ACTUALLY IS A

VARIABLE POWER

IT'S A 1.5 TO 5 POWER RIFLE SCOPE

AND

A LOT OF FOLKS SAY, WELL

PAUL, THAT'S A .308 RIFLE

THAT'S A LONG-RANG RIFLE

IT'S A PRECISION GUN

WHY WOULD YOU ONLY PUT

A 5 POWER SCOPE ON IT

WELL, DEPENDING ON WHERE YOU LIVE

YOU MAY NOT BE ABLE TO SHOOT

OR HAVE AN OPPORTUNITY

TO SHOOT YOUR RIFLE

BEYOND 200 YARDS

BEYOND 3 MAYBE EVEN 400 YARDS

IF YOU LIVE EAST OF THE MISSISSIPPI

A SHOT BEYOND 300 YARDS

IS PRETTY RARE

SO IF I'M GOING TO BE SHOOTING

A RIFLE LIKE THIS

IN THE 1 TO 2 TO 300 YARD RANGE

DO I NEED A 12 OR 15 POWER SCOPE

NO, I REALLY DON'T

SO, WHAT I DID

JUST TO PROVE A POINT

I ACTUALLY PUT THIS

LOWER POWER SCOPE ON HERE

AND YES, BECAUSE I KNOW THE DOPE

AND I KNOW THE ADJUSTMENTS

I CAN HIT TARGETS OUT TO 500 YARDS

WITH THIS SCOPE

AND I HAVE QUITE OFTEN

NOW WHAT AM I GOING TO

FEED THIS RIFLE TODAY

I'M GOING TO FEED IT

THE NOSLER SSA

THIS IS A 168 GRAIN

BOAT TAILED HOLLOW POINT

THIS GUN RIGHT HERE

REALLY SEEMS TO LIKE THIS AMMUNITION

I CAN SHOOT SUB MOA OR

SUB INCH GROUPS

AT 100 YARDS WITH THIS GUN, EVEN

THOUGH IT ONLY HAS A 5 POWER SCOPE

ALL DAY LONG, EVERY DAY

I WANTED TO TAKE A SECOND

AND MENTION SOMETHING

THAT A LOT OF PEOPLE

DON'T THINK ABOUT WHEN

THEY GO TO THE RANGE

YOU GO TO THE RANGE

AND WHAT DO YOU HAVE

YOU'VE GOT, WELL, YOUR GUN

YOUR RIFLE, YOUR PISTOL

YOUR SHOTGUN, WHATEVER

YOU'VE GOT YOUR RANGE BAG

AND IT'S FULL OF AMMO

YOU MIGHT HAVE YOUR EAR PROTECTION

EYE PROTECTION, ALL THAT

AND YOU'RE LIKE, I'M GOOD TO GO

DO YOU HAVE A TRAUMATIC MEDICAL KIT

THIS KIT RIGHT HERE

I PULLED IT OUT OF THE RANGE BAG

IT SITS IN THE SIDE POCKET

OR ACTUALLY THE END POCKET

OF MY RANGE BAG

AND IT'S ALWAYS THERE

EVERY TIME I GO TO THE RANGE

IT'S THERE

IT HAS A TOURNIQUET

IT HAS A PRESSURE DRESSING

IT HAS GAUZE

IT HAS LOTS OF OTHER THINGS

TO DEAL WITH

EMERGENCY BLEEDING SITUATIONS

I'M NOT JUST TALKING ABOUT

BANDAIDS, I'M NOT TALKING ABOUT

THAT LITTLE

SQUARE PLASTIC BOX

THAT HAS A COUPLE OF BANDAIDS

AND A LITTLE ALCOHOL WIPE

AND SOMETHING

I'M TALKING

WHAT DO YOU DO

WHEN SOMEONE IS

BLEEDING HEAVILY ON THE RANGE

YOU'RE LIKE UN-UH

WE'RE ALL SAFE PAUL

WE'RE ALL SAFE SHOOTERS

WE KNOW THE RULES

THAT WILL NEVER HAPPEN

YES IT WILL

I'VE BEEN ON THE RANGE TWICE

TWO DIFFERENT OCCASIONS

WHEN PEOPLE WERE ON THE RANGE

WITH ME

AND THEY SUSTAINED

TRAUMATIC BLEEDING INJURIES

AND I HAD TO HELP THEM

AND ASSIST THEM

I NEVER EVER GO TO THE RANGE

WITHOUT A KIT

WE SELL THE

POCKET LIFE SAVER KITS

THIS IS A STUDENT KIT

IT'S A SMALL ONE

WE HAVE THE LARGER KITS

YOU CAN PUT IN A CARGO POCKET

CARRY IT WITH YOU

YOU SHOULD ALWAYS HAVE

TRAUMATIC MEDICAL GEAR

WITH YOU

WHEN YOU GO TO THE RANGE, AND

WHEN YOU GO TO THE RANGE

MAKE SURE THAT THE OTHER PEOPLE

WHO ARE WITH YOU

KNOW WHERE THE MEDICAL GEAR IS

AND HOW TO USE IT

BECAUSE IT MIGHT BE YOU THAT'S BLEEDING

For more infomation >> Weatherby Sub MOA .308 Bolt Action - This is Rifle Country S1 Ep4 - Duration: 5:34.

-------------------------------------------

How to Failover PostgreSQL on Google Kubernetes Engine (GKE) - Duration: 7:38.

Hi.

In this demo, I want to show you how to perform a failover of a PostgreSQL database running

within Kubernetes backed by Portworx.

We already have a running Postgres deployment, which is just running one replica set or one

instance of the database.

Even though we are running just one instance, we can achieve failover and high availability

thanks to Portworx.

So let's see how to achieve HA and failover of the single database pod running PostgreSQL

database.

The first thing that we are going to do is to populate our database with some

sample data.

So for that, I'm going to grab the name of the pod by querying on the label that means

app is equal to Postgres.

So, this will get us the only pod that is running PostgreSQL and then we are going to

do an exec to get into the shell of this pod.

Now we are inside the Postgres pod and we can go ahead and execute the psql CLI.

So now we are within the Postgres shell and we can run a bunch of commands to

populate a sample database.

So let's go ahead and create a database called PX Demo.

Now we can verify this with the slash L command, and we notice that PX Demo database is now

created.

Let's quit this and then populate this with some sample data.

So we take help of the pgbench CLI to do that.

So this is going to create about 5 million rows inside the demo database that we just

created.

That's a lot of data.

So let's give it a few seconds and we should have a fully populated sample database.

Alright, let's verify the creation of this by again getting into the psql shell

and querying for the tables.

So you noticed that pgbench has created a set of tables and we can now get the count

of the number of rows from the accounts table, pgbench hyphen accounts.

And that shows about 5 millions rows.

Perfect.

Now, let's quit the pgSQL shell and also get it off the pod.

So what we are now going to do is to do something pretty crazy.

So we're going to cordon off the node that's running the Postgres database, which means

it will avoid scheduling any new pods on it.

So to do that, we need to get the name of the node that is primarily running

our Postgres database.

So when we actually do get pods with this command, we notice that it is running on one

of these nodes so we're going to grab the node name to cordon off the node to avoid

further scheduling.

What I'm trying to achieve here is to emulate a node failure by cordoning it off, and once

we cordon off the node and even going ahead and deleting the pod, we'll not disrupt our

workload because immediately Portworx is going to make sure that the newly created pod is

going to be deployed in one of the nodes that already has the data.

So let's emulate node failure by creating a cordon node.

Before that, let's take a look at the nodes.

You notice that all the three nodes are in ready state.

All of them are capable of scheduling pods and running them.

So we will now go ahead and cordon off the node that is currently running the PostgreSQL

pod.

So now if we do a "kubectl get nodes", you notice that the second node, which is primarily responsible

for running our current pod is cordoned off.

So that means no more pods are going to be scheduled.

Alright.

Now, let's also go ahead and delete the pod.

So for that, I'm going to get the pod name of the Postgres database.

So this is the pod name.

The only pod that we have in the default namespace.

So now what we are going to do is to actually delete this pod.

So "kubectl delete pod".

Now, it is going to delete the pod.

And as soon as that is done, because it's a part of deployment, Kubernetes will automatically

create a new pod because we set the replica set for this deployment as one, and now a

new pod is created, but interestingly this pod is not going to be located on the same

node, where we originally ran the pod.

Now, the node is cordoned off, that means it cannot be scheduled on this anymore instead

it has been scheduled on the third node.

So, with this complete exercise of simulating a node failure followed by deleting

the pod, in normal cases, we might actually face the risk of losing data, but not when

we are running Portworx, so let's check that.

Before that, let me make sure I uncordoned the node.

And now, let's see if our data is still intact.

So we'll now grab the name of the new pod that is scheduled in the third node, and we

will get into the shell of this pod then run psql with PX Demo and then we are going to

check for all the tables.

There we go.

Everything is intact.

And finally, the acid test where we are checking the row count of pgbench accounts and it is

still five million.

Fantastic.

So even after the node failure and pod deletion, the data is intact.

That's because of the replication factor that we created during the storage class and behind

the scenes there is also the magic of STORK, which is the storage orchestrator for Kubernetes

engine, created by Portworx.

It's a custom scheduler which will ensure that the newly created pod is always placed

on the same node that has the data available.

So the combination of STORK combined by the replication factor resulted in the high availability

of the pod even while running a single instance of the workload.

For more infomation >> How to Failover PostgreSQL on Google Kubernetes Engine (GKE) - Duration: 7:38.

-------------------------------------------

How to Deploy PostreSQL on Google Kubernetes Engine (GKE) - Duration: 8:16.

Hi.

In this demo I want to show you how to install a high availability Postgres database backed

by Portworx and Kubernetes.

Since we're going to use Portworx as the storage back-end, we don't need to configure additional

parameters to ensure high availability of Postgres which means you don't need to create

PostgreSQL as a stateful set or use any other mechanism to achieve high availability.

Since the storage back-end powering our database is already highly available and is redundant,

we automatically achieve HA of our database.

So let's see how to do this.

The very first thing that we're going to do is to create what is called as

a storage class.

If you are familiar with Kubernetes, you know that the storage class is going to associate

a specific storage back-end with our volumes and volume claims that we'll create in the

next step.

This is a storage class specific to Portworx.

While everything looks almost the same as the other storage classes, what is unique

to this configuration is the parameter called replication factor, and in this case we are

mentioning the replication factor as 3, which indicates that the data retained to any of

the Portworx volumes is going to be replicated across three nodes, and this is the magic

that Portworx will bring to achieve high availability of the stateful workloads.

So, let's go ahead and create the storage class.

So this is going to create a storage class called "px-repl3-sc".

Once we have the storage class, the next step is to create a persistent volume claim.

Now again, if you have background of Kubernetes, you know that a PVC is always bound to a PV,

which is a persistent volume.

But thanks to dynamic provisioning, we can straight away associate the PVC with the storage

class, bypassing this step to create the volume first and then creating a volume claim.

We do that by mentioning the storage class and associating it with the previous storage

class that we just created.

We're also making sure that we have at least 1 GB of claim available for the application.

So, let's now create the PVC based on the storage class that we just created.

So this is going to result in 1 GB PVC which is already bound, and this is the concept

of dynamic provisioning where we can bypass the creation of volume before claiming the

volume space.

Alright, with those two in place, the storage class and the PVC, we need to now create the

part of the deployment running pgSQL.

Because pgSQL expects username and password, we are going to follow the best practices

of creating a Kubernetes secret.

For that, I'm going to create a plain manila text file that contains a dummy password we

are going to use for this demo.

We'll ensure that we are getting rid of the newline character.

And then from this file, we are going to create a generic secret, which is called Postgres

pass.

So, when we do "kubectl get secret", we'll see that the password is available as a secret.

Now it's time for us to create the actual deployment of Postgres.

So let's take a closer look at the YAML definition.

This is configured as a deployment with replicas as one.

As I mentioned, even if we are just running this as one instance, thanks to the back-end,

we'll still achieve HA.

Then we are going to use the secret that we just created from the generic secret already

stored within the cluster and in the default name space.

Finally, we are associating this deployment with a volume resulting from the PVC.

So, the claim name is now pointing to "px-postgres-pvc", which was created here, and this is in

turn, pointing to the storage class and this is how the parts are going to be backed by

Portworx storage back-end.

Alright, so let's go ahead and create the Postgres deployment.

This is going to result in the creation of the pod, so let's put this in watch mode.

In just a few seconds, we'll notice that this pod, which is a part of the deployment, will

move into a ready state with status becoming running and that indicates the successful

configuration and deployment of PostgreSQL.

There we go.

Now we have the Postgres pod up and running.

How do we ensure that everything has been configured perfectly well and we are ready

to run our workloads on top of Postgres?

Well, let's grab the volume resulting from the creation of the PVC.

So we'll run this command to basically grab the volume name associated with this PVC.

Verifying this will show us a unique ID, which is bound to the Portworx back-end.

Now, we're going to grab the pod name, which is a part of the Daemon set running

Portworx.

And because we are pointing it to the kube-system namespace with the label key-value beta's

name is equal to Portworx.

This is going to give us the name of the Portworx pod.

On that, we are going to execute a command, which will invoke pxctl, the binary associated

with Portworx, and we're going to inspect the volume that is backing our Postgres database.

So, volume inspect, followed by the volume name that we grabbed from this, and this is

going to show us some pretty interesting details.

So, this is the name of the Portworx volume, and because it is a part of dynamic

provisioning, you will see that it is associated with the PVC, it's of 1 GB size.

Again, based on the PVC that we defined earlier, it is highly available based on three-factor

replication.

It is attached to one of the SSD disks, part of the GCP infrastructure and the GKE cluster.

And because we have set up the replication factor as 3, it's automatically available

on all the three nodes of our cluster.

Replication status is all green, which is up and running.

This is pointing us to a very healthy installation of Portworx, as well as PostgreSQL database.

In the next video, we're going to show how you can achieve high availability

by deleting a running pod and recreating it with all the data intact.

Thanks for watching.