►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
A
So
if
data
protection
is
something
that
you
think
about
a
lot,
I
encourage
you
to
take
a
look
at
the
white
paper,
so
I
talked
about
data
protection
today.
Why
bother
in
2021
cncf
survey
reported
that
64.69
of
the
respondents
said
that
they
are
currently
running
stateful
applications
in
containers
in
production,
kubernetes,
considering
the
number
of
organizations
running
kubernetes
in
production
today
this
is
not
a
small
number.
A
A
A
A
A
A
A
A
A
A
So,
let's
go
straight
into
the
demo,
we
will
be
using
an
eks
cluster.
I
have
pre-installed
a
postgres
database
on
the
cluster
and
the
pod
has
a
pvc
and
a
pv
attached
to
it
and
it's
backed
by
an
actual
ebs
volume
on
the
right
side
of
this
diagram.
You
see
that
during
the
demo
I'll
be
using
canister
to
manage
the
csi
volume
snapshot
and
volume,
stationary
content
resources
to
create
and
manage
the
actual
ebs
snapshots.
A
The
flow
of
the
demo
is
pretty
simple:
we're
going
to
start
off
with
using
a
tool
called
cubester
to
discover
and
verify
our
volume
provisioners
and
the
different
csi
storage
solutions
on
our
cluster.
Then
we're
going
to
go
ahead
and
deploy
our
postgres
blueprint
and
from
there
we'll
dive
into
specific
individual
actions.
A
A
So
in
this
demo
I'll
be
using
a
script
to
automate
the
typing,
otherwise
we
are
targeting
a
real
live
eks
cluster,
so
the
first
command
I
want
to
run
is
to
use
cube
cuddle
to
confirm
that
I
am
indeed
working
with
the
right
eks
cluster,
so
great.
So
now
we're
going
to
use
cubester
to
discover
and
verify
the
volume
provisions
and
the
csi
solutions
on
our
clusters.
A
A
A
A
A
A
In
addition
to
faces,
we
also
recently
added
something
called
a
differ
face.
You
can
think
of
a
different
phase,
as
that
always
run
final
phase.
So,
regardless
of
what
happened
to
previous
phases,
this
phase
will
always
be
run
at
the
end
if
you're
familiar
with
go.
This
is
very
similar
to
the
goal
deferred
statement,
so
this
deeper
phase
says
whatever
happens
previously,
always
reset
the
database
back
to
read,
write
mode
so
put
things
back
to
where
we
found
how
we
found
it
before.
A
A
It
is
expecting
a
number
of
input
parameters
so
later
I'll
show
how
we
can
use
the
output
from
the
create
snapshot,
action
and
feed
that
into
the
restore
snapshot,
action
as
input
parameters.
A
A
So,
as
I
mentioned
earlier,
an
action
set
is
that
run
time,
execution
trigger
point
or
entry
point.
This
is
what
the
yamo
of
the
create
snapshot
action
set
looks
like.
It's
basically
provide
information
on
what
action
to
run
and
where
the
blueprint
is
and
then
also
a
set
of
input
parameters
that
will
be
fed
into
the
canister
function.
A
A
A
A
So,
as
you
can
see,
with
that
action
set
being
applied,
we
now
have
a
new
pvc
restore
to
the
same
namespace
that
my
original
postgres
database
is
running
in
the
status
of
this.
Pvc
will
remain
pending
because
by
default,
the
storage
class
that
we
are
using
has
the
binding
policy
set
to
wait
for
a
first
consumer.
A
A
A
A
A
If
backup
and
restore
is
something
that
you
have
to
deal
with
a
lot,
I
encourage
you
to
check
out
canister
source
code
is
on
github
feel
free
to
join
us
on
slack
I'm
always
there
answering
questions
and
talking
to
you
about
your
use
case
join
our
community
meeting.
We
meet,
we
meet
every
other
thursdays
like
16
hour
utc.