►
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Take the Kubernetes Back Up User Survey at https://velero.io/survey
Velero is an open source project providing tools to backup, restore, and migrate your Kubernetes cluster resources and persistent volumes. It is a cloud native, Kubernetes optimized approach to backup and restore enabling data protection use cases no matter where your cluster is running. If you’re ready to see how backup evolves in the world of cloud native applications, this webinar will provide a clear view of that future. Join Velero tech lead, Steve Kriss, and product manager, Tom Spoonemore as they provide a technical walkthrough of the project and demonstrate Kubernetes application migration across clusters using Velero.
• During this session, we will cover:
• An overview of Project Velero
• Use cases from basic backup to ephemeral clusters
• Strategies for protecting cloud native applications
• Live demonstration migrating an application between Kubernetes clusters
A
A
All
right,
I
think
we're
gonna
go
ahead
and
get
started.
I'd
like
to
thank
everyone
for
joining
us
today.
Today's
webinar
kubernetes
backup
in
migration
strategies
using
project
frilair,
oh
I'm,
sorry,
Blackman,
I'm,
CN,
CF,
ambassador
and
security
engineer,
dr.
and
I'll
be
moderating
today's
webinar.
We
would
like
to
welcome
our
presenters
today,
Steve
Chris
and
Tom
spume,
or
from
Project
Valero
few
housekeeping
items.
Before
we
get
started
during
the
webinar.
You
will
not
be
able
to
talk
as
an
attendee.
Everyone
is
muted,
there's
a
Q&A
box
at
the
bottom
of
your
screen.
A
B
B
B
B
So
today's
agenda
is
we'll
be
talking
about
kuba
knees
back
up
and
restore
migration.
Use-Cases.
How
to
think
about
backup
and
restore
in
a
cloud
native
world
will
be
an
introduction
to
velaro.
The
project
will
talk
about
strategies
for
protecting
your
applications
and
cloud
native
way.
Steve
will
also
be
doing
a
demo
of
migration
and
and
velaro
backup
restore.
B
So
there's
a
number
of
use
cases
that
you
need
to
be
prepared
for
disaster
recovery,
data
protection,
data,
migration
and
and
project
Valero
is
is
one
way
to
help
do
that.
So
in
the
disaster
recovery
use
case,
there's
a
you'll
be
considering
ways
that
you
can
rebuild
your
clusters.
If
something
happens,
your
cluster
or
if
you
choose
to
rebuild
it,
to
take
backups
of
your
applications,
point
in
time,
backups
or
store
those
backups
for
a
variety
of
different
reasons
or
provide
recovery.
B
In
the
case
of
in
the
case
of
a
failure
of
some
kind
on
the
data
protection
side,
you
have
to
be
concerned
about
data
losses
with
any
data
application.
It's
possible,
you
could
have
data
option,
applications
could
could
applications
or
hardware
could
could
go
bad
could
create
corruption.
You
could
have
other
reasons
why
your
data
becomes
corrupted
and
you
have
to
go
back
to
a
certain
point
in
time
of
restoration
and
for
a
number
of
industries.
B
Archival
retention
is,
is
critical
in
the
legal
industry
and
and
other
regulated
industries.
Just
having
archives
of
data
is
a
regulatory
and
compliance
issue
that
has
to
be
planned
for
and
in
the
world
of
public
cloud
private
cloud.
We
see
a
data
migration
use
case
from
our
customers
as
well
and
for
data
migration.
B
To
be
able
to,
you
know,
provide
responses
for
each
one
of
these
use
cases,
so
project
Valero,
just
a
little
bit
of
background
on
Valero
Valero,
is
an
open
source
tool
for
backing
up
your
kubernetes
clusters
and
persistent
volumes
for
your
applications.
It
works
both
on-premise
and
in
public
and
natively
on
kubernetes,
so
Valero,
unlike
many
backup
and
restore
utilities,
isn't
Driss
concerned
with
passing
a
file
system
and
picking
up
the
files.
B
But
it
also
is
aware
that
kubernetes
itself
is
a
really
a
running
state
machine
that
is
managing
the
state
of
all
of
your
applications.
The
deployments
of
the
deployment
manifest
for
all
those
applications
and
all
that
is
considered
data
to
Valero.
That
needs
to
be
it
needs
to
be
backed
up
currently
we're
well
over
2,500
stars
on
on
github.
We
are
at
version
1.0
and
and
as
of
this
week,
we're
a
hundred
contributor
strong
in
the
project
and
we're
super
happy
about
that.
B
Valero
itself
has
a
couple
of
different
components.
One
of
them
is
a
command-line
interface
that
you
can
use
to
install
velaro
to
also
initiate
backups,
to
create
backup
schedules,
who
you
know,
add
backup,
locations
and
targets,
as
well
as
to
perform
restore
operations.
So
then,
the
on
the
server
side
is
a
server
application,
a
controller
that
operates
on
a
number
of
CR
DS
that
are
created
by
the
Valero
command
line
that
give
instruction
to
the
server
as
to
how
it
should
how
it
should
go
about
performing
backups
and
restores.
B
So
Valero
seeks
to
address
each
of
the
the
use
cases
that
we
spoke
about
before
so
the
disaster
recovery
side
of
things
Valero
reduces
the
time
to
recover
your
clusters
in
the
case
of
some
kind
of
infrastructure,
loss,
data,
corruption
or
other
kind
of
service
outage
Valero
backs
up.
You
know
all
of
the
objects
in
your
cluster
and
can
in
a
very,
very
easy
way
recover
the
cluster
to
a
new
target
cluster
for
data
migration.
B
Valero
does
have
a
lot
of
capabilities
to
allow
portability
of
of
the
objects
on
your
cluster
from
one
cluster
to
another,
there's
also
techniques
which
Steve
will
go
into
a
little
bit
later
for
doing
things
like
I,
like
transforming
data
objects
as
they
move
from
one
cluster
to
another.
Perhaps
you
know
data
objects,
like
you
know,
storage
classes
etc
need
to
change
from
one
from
a
source
to
a
target.
Cluster
Valera
has
all
these
kinds
of
capabilities
and
an
understanding
of
how
to
make
those
migrations
successful.
B
The
other
thing
Valero
is,
you
know
like
kubernetes
itself
and
many
other
cloud
native
tools.
Is
it
integrates
with
your
DevOps
workflow?
So
you
can.
You
can
use
get
ops
kind
of
strategies
to
to
drive
Valero.
You
can
also
create
kind
of
ephemeral
clones
of
the
native
namespaces,
so
you
need
to
do
an
operation
on
a
namespace
or
you
need
to
transform
a
namespace
from
one
cluster
to
another
or
or
otherwise
make
it
available
to
another
team
or
set
of
users.
B
What's
in
a
namespace,
all
the
objects,
how
to
reconstitute
those
objects
and
data
volumes
into
another
namespace
successfully,
and
so
this
kind
of
sets
us
up
for
what
we
really
think
is
kind
of
a
future
for
ephemeral
clusters
and
Valero
provides
a
capability
to
really
rebuild
clusters
in
a
in
a
very
easy
and
scriptable
way,
so
that
you
know
we
can
start
thinking
of
clusters
in
ways
that
we're
thinking
of
cloud
native
applications
where
the
application
can
be
completely
removed,
restored,
and/or
components.
The
application
are
resilient
because
of
strategies.
B
You
know,
like
consistency
and
declarative,
declarative
llamo,
so
Valero
allows
you
to
start
thinking
of
your
entire
clusters
in
this
way,
so
that
it
unlocks
the
abilities
to
be
able
to
easily
reconstitute
clusters
and
and
again,
as
I
pointed
out
before
you
know,
you
can
think
in
terms
of
these
clusters
being
so
easy
to
reconstitute
that
you
don't
really
even
need
to
do
upgrades.
You
can
just
build
new
clusters
and
transition.
Your
applications
from
one
cluster
to
another.
B
So
a
traditional
backup
and
restore
you
know:
you're
really
backing
up
an
application,
and
the
application
is
really
the
hardware
that
it's
running
on
right.
So
when
you're,
so
in
a
free
cloud
native
world
you're
backing
up
a
server,
applications
ran
on
a
server
server,
had
an
OS
configurations,
configurations
of
the
application
file
system,
Stratton
structures,
etc.
B
All
of
these
things
need
to
be
backed
up
in
a
very,
very
kind
of
infrastructure
focused
way,
but
as
we
move
into
cloud
native
applications
we're
not
so
much
interested
in
the
underlying
infrastructure,
as
that's
been
largely
abstracted
away,
so
we
need
to
think
about
things
a
little
bit
differently
and
particularly
as
it
relates
to
kubernetes
crew.
Naze
itself,
like
I,
said
before,
is
a
it's
a
it's
a
deployed
application
itself.
It
is
a
stateful,
is
a
stateful.
B
Operations
platform
right,
so
there
is
data
associated
with
that,
so
your
application
can
be
deployed
across
a
number
of
nodes.
It
can
the
state
of
that
application.
Both
the
desired
state,
as
well
as
the
operation
state,
are
stored
in
database
call
that
CD
and
we
are
concerned
now
with
not
just
backing
up
the
application.
B
But
you
know
how
we
deal
with
that,
how
that
application
is
distributed
across
nodes
applications
that
are
storing
state
and
at
CD
the
the
kubernetes
itself,
storing
of
that
of
its
own
state,
a
net
CD
and
and
then
then,
of
course,
the
application
deployments
and
set
themselves
so
the
deployment
resources
themselves
and
how
they're
how
they're
handled
so
so
we
need
to
think
about.
You
know
how
all
of
this
stuff
is
deployed
and
tied
together
and
all
of
the
various
objects
that
are.
B
C
All
right
thanks,
Tom,
so
yeah,
so
things
are
definitely
a
little
bit
more
complicated
in
a
kubernetes
environment
than
in
a
kind
of
a
traditional
IT
environment
when
it
comes
to
data
protection,
and
so
you
know
the
first
step
to
developing
our
data
protection
strategy
is
really
to
think
about.
Where
is
the
state
within
a
kubernetes
system?
And
so
you
know
the
first
place
that
that
most
folks
think
about
when
they
think
about
state
in
kubernetes.
Is
that
@cd
database
that
Tom
alluded
to
so
this
is,
you
know
the
backing
store
for
the
kubernetes
api?
C
This
is
where
all
of
your
deployments
are
defined,
your
config
maps
and
secrets
and
pods,
etc.
And
so
this
is
this
is
a
dynamic
store
of
data.
That's
going
to
be
changing
as
users
are
deploying
applications
to
your
kubernetes
platform,
and
so
the
is
going
to
be
super
important
to
be
able
to
to
protect
and
to
have
backups
and
to
be
able
to
recover,
and
then,
additionally,
you
know
the
second
main
storage
state
within
this
environment
is
your
you're
persistent
volume.
So
this
is
really
where
your
applications
are
storing
their
data
and
they're.
C
Doing
this
in
a
kubernetes
native
way
using
declarative
definitions
for
these
volumes,
but
we
really
need
to
be
able
to
backup
not
just
the
configuration
of
these
things,
but
the
data
inside
them
as
well.
In
a
way
that's
linked
back
to
the
kubernetes
application
definitions
when
we
think
about
the
the
nodes
that
make
up
the
cluster,
though
so
your
masters
and
your
workers
there's
not
a
lot
of
state.
That's
inherent
in
these
things
themselves.
C
So
each
of
these
nodes
are
going
to
be
running
a
set
of
the
core
kubernetes
components,
so
you
know
on
the
master,
will
have
the
API
server
running
while
the
controller
manager
running
and
the
workers
will
be
running
the
cubed
and
cube
proxy
and
other
things
like
that.
But
these
really
aren't
changing
very
much
over
time.
C
They're
they're,
essentially
a
set
of
commodity
components
that
can
be
used
to
define
a
cluster,
and
so
when
we
think
about
the
the
approaches
to
kind
of
data
protection
for
each
of
these
components,
it's
going
to
vary
based
on
whether
they
are
in
this
kind
of
stateful
category
or
in
the
the
stateless
category.
So
next
slide,
please
Tom.
C
C
All
right,
so
you
know
starting
on
the
left
when
we're
talking
about
the
nodes
and
make
up
a
kubernetes
cluster.
You
know
it's
our
view
that
it's
less
important
to
think
about
backup
and
restore
here
than
it
is
to
think
about
really
using
automation,
to
make
it
very
trivial,
very
straightforward
to
provision
new
infrastructure
as
needed
to
replace
to
replace
existing
ones,
and
so
you
know
whether
you're
using
ansible
puppet
chef,
etc.
C
The
the
focus
I
think
here
is
really
on
making
it
super
easy
to
stamp
out
a
new
copy
of
a
worker
node
or
a
master
node,
so
that,
if
you
need
to
replace
one
in
your
cluster
you're
able
to
do
that-
and
this
applies
not
just
for
individual
nodes
but
for
clusters
as
well.
So
Tom
alluded
to
the
kind
of
concept
of
ephemeral
clusters
a
few
slides
ago.
Cluster
API
is
a
great
example
of
an
effort.
C
That's
going
on
in
the
kubernetes
community
to
really
make
it
very,
very
straightforward
to
stamp
out
new
clusters
based
on
a
predefined
template,
and
so
we
think
that's
kind
of
the
right
approach
to
think
about
how
to
deal
with
needing
to
replace
individual
nodes
or
clusters
within
a
node
and
then
once
you
do
that
there
are.
You
know
there
are
tools
that
kubernetes
provides
that
cube.
C
Control
provides
for
safely
taking
unhealthy
nodes
out
of
your
clusters
and
swapping
in
a
new,
healthy
node
that
you've
been
able
to
stamp
out
from
your
template
on
the
right
side,
though,
things
are
a
little
bit
more
complicated.
So
with
that
CD
and
persistent
volumes,
you
can't
just
reproduce
these
from
a
template.
These
are
they
store
dynamic
data
and
they're
changing
over
time,
and
so
we
do
really
need
to
think
about
how
to
be
able
to
back
these
up
and
recover
to
specific
points
in
time.
Next
slide
all
right.
C
So,
let's,
let's
dive
into
each
of
those
stateful
components
a
little
bit
and
talk
about
some
strategies
for
for
data
protection
here,
so
starting
with
Etsy
D.
You
know
there
are
a
number
of
different
approaches
we
can
take
to
protecting
this
data
and
the
first
two
you
know:
block
and
filesystem
backups
basically
mean
that
you're
you're
taking
either
block
or
file
level
backups
of
the
device
that
that
EDD
is
storing
its
data
on-
and
this
is,
you
know,
kind
of
a
good
basic
approach.
C
It's
kind
of
the
lowest
common
denominator
and
it'll
get
you
a
certain
level
data
protection
for
that
data,
but
EDD
itself
is
a
distributed.
System
typically
runs
multiple
replicas,
and
so,
if
we
really
want
to
get
application
consistent
backups
of
this
data,
it
makes
sense
to
look
at
at
the
at
CDC
TLS
capabilities
for
doing
snapshots
of
the
cluster
in
this
one.
C
This
will
give
you
application
consistent
backups
of
the
entire
data
set
that's
stored
within
at
CD,
but
there
there
isn't
another
approach
to
backing
up
this
data,
and
so
we
know
that
within
kubernetes
that
CD
is
used
to
store
the
data
for
your
API
resources,
and
so
you
another
approach
to
backing
up
this
data
is
to
use
the
kubernetes
api
itself
to
actually
access
the
data.
That's
in
that
CD
and
store
it
in
a
backup.
The
kubernetes,
the
kubernetes
api,
provides
something
called
a
discovery
API
which
enables
you
to
kind
of
dynamically.
C
You
discover
all
of
the
different
resource
types
that
exist
within
the
API
and
then
from
there
you're
able
to
to
capture
the
full
definitions
of
each
of
those.
So
this
is
another
viable
approach
for
for
accessing
that
data.
That's
in
that
CD
to
back
it
up,
and
then
on
the
persistent
volume
side.
We
again
we
have
a
few
different
approaches,
so
the
first
one
you
know
is
to
really
rely
on
your
storage
provider.
C
Now
this
may
be
a
public
cloud
provider
or
may
be
an
on-premises
provider,
but
to
rely
on
snapshots
as
a
way
to
capture
a
point
in
time,
references
to
your
data
and
then
to
be
able
to
potentially
create
durable
backups
from
those
so
that
you're
able
to
restore
if
you
need
to
this
is
typically
kind
of
a
block
level
function.
But
you
can
also
look
at
taking
filesystem
backups
of
the
persistent
volumes
that
you're
using
this
you
know
would
be
particularly
useful
if
you're
looking
at
doing
kind
of
single
file
recovery.
C
If
that's
an
important
use
case
for
you
and
then
the
you
know,
a
third
option
here,
that's
emerging
is
is
looking
at
the
container
storage
interface,
which
is
becoming
a
standard
for
kubernetes
and
other
container
orchestration
systems
and
looking
at
the
emerging
snapshot,
api's
that
are
being
added
to
those
now
those
are
currently
in
an
alpha
state.
The
upstream
storage
community
is
looking
at
moving
these
to
beta
relatively
quickly,
but
this
this
provides
another
kind
of
integration
point
for
being
able
to
take
point
in
time.
Snapshots
of
the
persistent
volumes
you're
using
next
slide.
C
Alright.
So
so,
with
that
background,
let's
talk
a
little
bit
about
Valero
and
its
approach
to
data
protection.
So
first
of
all,
Valero
enables
you
to
back
up
both
your
kubernetes
objects.
So
all
the
kubernetes
api
data
that's
stored
in
at
CD,
as
well
as
your
applications.
Persistent
volumes
so
Valero
covers
both
of
these
stateful
components
that
we've
been
talking
about.
As
far
as
the
the
kubernetes
objects
go,
Valera
uses
the
the
kubernetes
discovery
API
to
access
this
data.
C
You
know
the
first
one
is
that
on
a
lot
of
managed
cloud
provider,
kubernetes
platforms
you're
not
going
to
have
direct
access
to
at
CD,
so
in
in
things
like
google
kubernetes
engine
or
a
Jers
kubernetes
engine,
as
a
user
you're
not
going
to
have
direct
access
to
at
CD,
and
so
there's
there's
not
actually
a
way
to
do
a
direct
backup
there.
So
we
need
an
alternate
approach
beyond
that,
though.
The
the
API
gives
us
a
lot
of
capabilities
that
we
wouldn't
have.
C
Even
if
we
were
doing
direct
at
CD
backups
so
using
the
API,
we
can
do
sort
of
fine-grained,
filtering
and
selection
of
the
resources
that
we
want
to
backup.
And
this
also
mean
that
when
it
comes
time
to
restore,
we
can
be
much
more
precise
about
what
which
applications,
which
particular
resources
we
want
to
restore
and
then
using.
The
API
also
enables
us
to
to
kind
of
transform
this
data
as
we're
doing
backups
or
restores.
C
So
that,
if
you,
if
you
lose
a
cluster
or
you
need
to
migrate
to
an
additional
cluster,
you
have
kind
of
a
central
location
where
that
backup
data
exists
and
then,
as
far
as
persistent
volume,
backup
and
restore
so
Valera
uses
the
cloud
provider
snapshot.
Ap
is
the
laura,
has
a
an
extensible
plug-in
system
so
that
additional
providers
can
be
added
as
supported
velaro
providers
without
without
needing
to
modify
the
core
velaro
code.
But
but
this
is
really
our
primary
approach
to
backing
up
persistent
volumes.
C
Maybe
you
just
the
little
plugin
hasn't
developed
been
developed
yet
for
your
provider,
or
this
is
also
really
useful
if
you're
doing
cross
provider
migrations,
because
you
do
get
a
generic
provider
agnostic
format
for
your
backups
and
then
beyond
that.
You
know,
Valero
has
a
variety
of
different
features
that
that
help
with
your
backup
and
restore
workflows.
So
it
supports
both
ad
hoc
and
scheduled
backups,
as
I
mentioned
before,
there's
there's
some
sophisticated
filtering
that
you
can
do
as
you're
backing
up
or
restoring
resources.
So
you
can
select
specific
namespaces
to
backup
specific
resource
types.
C
C
Alright
next
slide,
so
just
a
kind
of
a
quick
overview
of
what
a
what
a
standard
velaro
workflow
might
look
like.
So
in
this
diagram
we
have
two
different
kubernetes
clusters,
one
on
the
left,
one
on
the
right
and
starting
on
the
left
in
kubernetes
cluster
8a
we're
using
the
Valero
CLI
to
take
a
backup.
C
We
have
another
instance
of
Valero
and
so
in
this
case
we're
doing
sort
of
a
migration,
so
this
cluster
is
configured
to
be
able
to
restore
backups
from
the
same
location
where
cluster
a
was
creating
them.
So
on
the
right,
we're
running
a
Valero
CLI
command
to
create
a
restore
we're
specifying
the
name
of
the
backup
that
was
created
from
cluster
a
and
the
Valero
controller.
C
C
So
the
the
first
thing
I'll
show
here
is
a
backup
and
restore
within
an
individual
cluster,
and
so
what
I
have
here
is
a
cluster
running
in
gke.
You
can
see
from
my
command
prompt
here
that
it's
labeled
as
cluster
1
and
within
this
cluster
I'm
running
an
instance
of
the
WordPress
application.
That's
using
my
sequel
as
the
data
store,
and
so
the
the
first
thing
I
have
showing
here
is
that
we
actually
have
a
service
up
to
access
that
WordPress
instance.
C
C
Now
we
see
that
that
ran
pretty
quickly,
and
so,
if
I
use
Valero
back
up
yet
I
can
see
here's
our
backup
title
WP
it's
completed
and
I
can
also
run
the
lair
Oh
backup
describe
WP
and
I
can
use
the
details
flag
to
see
some
additional
information
about
it.
So
there's
a
variety
of
information.
That's
shown
here
in
this
top
section.
We
just
see
some
information
on
the
kind
of
the
spec
for
the
backup
that
we
created.
C
So
the
main
main
thing
to
see
here
is
that
we
have
a
namespaces
section
that
defines
which
namespaces
were
include
in
the
backup
and
since
I
used
that
flag,
while
I
created
the
backup.
We
see
that
the
that
was
the
included,
namespace
and
then
scrolling
down
towards
the
bottom.
You'll
see
this
section
here
which
describes
the
persistent
volumes
that
were
backed
up
as
part
of
this
Valero
back
up
and
so
Valero
found
that
there
were
two
different
PVCs
that
were
being
used
by
that
WP
namespace
and
so
for
each
one.
C
It
created
a
snapshot
using
the
GCP
api's,
and
so
here
we
have
references
to
those
snapshot.
Ids
and
some
additional
metadata
that'll
be
useful
when
we
need
to
restore
those.
So
the
next
thing
I'm
going
to
do
is
is
sort
of
simulate
a
disaster,
and
so
the
you
know
the
most
straightforward
way
to
do.
This
is
just
to
delete
and
delete
in
the
namespace,
the
wordpress
namespace-
and
you
know
this
this
really.
This
is
going
to
take
a
minute
to
delete.
But
really
you
know
you
could
imagine
a
number
of
different
scenarios
here.
C
Maybe
you
know
a
user
accidentally
applied
a
configuration
to
this
namespace
that
that
messed
up
your
your
application
definition
and
you
want
to
be
able
to
roll
back
to
a
previous
state.
Maybe
you
know
there
was
another
incident
and
you're
persistent
volume
data
got
got
corrupted
and
you
want
to
restore,
and
so
there
you
know
a
number
of
different
ways
that
you
can
think
about
this
use
case.
C
But
in
general
we
look
at
just
the
leading
the
namespaces
kind
of
the
primary
issue
that
we
would
need
to
recover
from
all
right,
so
the
namespace
has
been
deleted
and
I'll
just
take
a
quick
look,
so
we
no
longer
have
that
WP,
namespace
and
I'll
just
pop
back
to
my
browser
window
and
do
a
refresh
and
you'll
see
that
we're
we're
not
able
to
connect
at
this
point
in
time.
The
service
no
longer
exists.
The
odds
no
longer
exist
so
going
back
to
the
terminal.
C
What
I'd
like
to
do
now
is
actually
restore
that
namespace
using
velaro,
so
I'll
just
take
another
look
at
the
backups
I
have
so
my
one
backup
is
called
WP,
so
I
will
now
say:
Valero
store,
create
and
I'll
say
from
backup,
WP
and
I'll
kick
that
off
and
now,
while
this
is
running,
we
can,
we
can
get
a
little
bit
of
information
on
what's
happening.
So
if
I,
if
I
put
a
watch
on
the
persistent
volumes
in
this
cluster,
well
you'll
see
that
they
actually
were
already
created
so
that
that
happened
pretty
quickly.
C
I
can
use
the
Valero
restored,
get
command
to
look
at
the
status
of
my
my
restore
and
we
can
see
that
it's
completed
and
take
one
more
look
and
see
if
the
pods
are
up
and
running,
they
are
they're
up
and
running,
and
so
now
what
I
need
to
do
is
get
the
IP
address.
For
my
my
service,
this
will
change
since
we
restored
it,
and
so
WordPress
now
has
this
external
IP
address.
You
can
see
it
was
just
recreated
under
a
minute
ago,
and
so,
if
I
go
back
to
the
browser.
C
Alright.
So
so
that's
great
for
kind
of
restoring
within
a
single
cluster,
but
I
also
want
to
take
a
look
at
another
scenario,
which
is
migrating
an
application
not
just
to
a
different
cluster,
but
also
to
an
entirely
different
cloud
provider,
and
so
to
do
this.
We're
going
to
use
Valero's,
rustic
integration,
which
I
I
talked
about
a
couple
of
minutes
ago.
C
So
the
first
thing
we
need
to
do
is
we
need
to
tell
Valero
that
we
want
to
use
rustic
to
backup
the
persistent
volumes
rather
than
using
GCP
snapshots,
and
we
need
to
use
rustic
in
this
scenario,
because
I'm
gonna
be
migrating.
This
application
into
an
azure
cluster
and
azor
has
no
way
of
knowing
how
to
restore
GCP
snapshot.
So
rustic
will
give
us
kind
of
that
provider
agnostic
backup
of
our
data
so
that
we
can
restore
it
into
another
platform.
C
So
the
first
thing
I'm
going
to
do
is
actually
I
in
order
to
tell
the
lair,
oh,
that
I
want
to
use
rustic
I
need
to
add
some
annotations
to
the
the
word
press
and
the
my
sequel,
pods
and
so
I
have
some
llamo
definitions
here.
So
I'll
just
uncomment
this,
this
annotation,
which
tells
Valero
to
use
rustic
to
backup
this
persistent
volume.
So
I'll
do
that
from
my
sequel
and
also
for
WordPress,
and
then
I'm
gonna
go
back
here
and
just
reapply.
C
Those
manifests
will
actually
get
a
new
set
of
pods
that
are
scheduled.
So
just
put
a
watch
on
that,
so
that
I
know
when
those
are
completed.
But
so
what's
gonna
happen
from
here.
Is
that
we'll
we'll
take
another
backup
and
this
one
will
will
actually
use
rustic
to
backup
those
persistent
volumes
and
then
I'll
switch
over?
To
my
add
your
cluster
and
show
you
how
to
configure
it
to
be
able
to
the
backup
from
the
place
where
this
gke
cluster
is
currently
putting
backups?
C
C
Sometimes
this
goes
a
little
faster.
Sometimes
it
goes
a
little
slower,
so
apologies
for
the
delay
there,
but
it
looks
like
the
pods
are
up
and
running
now
so
I'm,
just
gonna
clear
my
screen.
So
at
this
point,
I'll
take
a
new
backup,
so
I'm
gonna
use
a
similar
command
to
the
last
time.
So
I'll
save
velaro
backup
create
this
time.
I'll
call
it
WP
rustic
so
that
we
know
we're
using
rustic,
backups
and
again.
I
just
want
the
WP
namespace,
all
the
resources
in
there
and
I'll
use
the
wait
flag
as
well.
C
Alright,
so
we
have
a
backup
now
I'm
going
to
actually
use
this
command.
That's
that's
given
to
me
here
to
look
at
some
of
the
details
of
those
I'll
use
the
details
flag
and
so
the
most
important
thing
to
notice
it's
different
years
on
the
bottom.
Instead
of
having
a
list
of
persistent
volume
snapshots,
we
actually
have
a
section
called
rustic
backups,
which
tells
us
the
the
pods
and
the
volumes
within
those
pods
that
were
backed
up
alright.
So
we
have
our
backup
now.
C
So
now
we
want
to
switch
over
to
the
azure
cluster
that
we're
going
to
restore
into
and
get
it
configured
to
be
ready
to
restore.
So
you
can
see
here
that
I'm
on
cluster
Azure
and
if
we
look
at
the
namespaces
we'll
see
I,
don't
have
a
wordpress
namespace
right
now.
So
the
first
thing
I
need
to
do
is
create,
what's
called
a
backup
storage
location
which
tells
this
cluster
where,
where
these
backups
are
stored,
and
so
to
do
that,
I
can
say,
velaro,
backup,
location,
create
I'm,
going
to
call
it.
C
G
CP
need
to
give
it
a
provider
which
is
G.
Cp
I
also
need
to
tell
it.
The
name
of
the
bucket
is
the
lair
of
backups
and
then
the
final
thing,
which
is
a
new
feature
that
hasn't
been
released
yet
but
will
be
coming
out
in
1.1,
is
an
access
mode,
and
so
I
want
to
set
this
location
up
to
be
read-only
from
the
perspective
of
the
azure
cluster,
because
I
only
want
to
be
able
to
restore
these
backups
I.
C
C
And
so
what
we
want
to
do
here
is
just
in
the
data
section.
For
this
config
map.
Add
a
new
mapping
from
the
standard
storage
class
to
the
managed
premium
storage
class.
So
I'll
save
that,
so
we
should
be
set
up
now.
And
so,
since
we
added
that
backup
location
pointing
to
the
GCP
bucket,
we
should
actually
be
able
to
see
now
if
I
run
a
Valero
backup
get
those
two
backups
that
we
just
created
from
the
GCP
cluster.
And
so
this
WP
rustic
backup
is
the
one
that
we're
going
to
want
to
restore
here.
C
So
we
can
take
a
look
at
what's
going
on
with
the
persistent
volumes
while
this
restore
runs
alright,
so
we
we
see
that
we
just
actually
got
the
to
persistent
volumes
created
in
this
cluster,
and
so,
if
you
look
here
under
the
storage
class,
you'll
see
that
those
were
successfully
remapped,
so
they
now
have
the
managed
premium
storage
class
within
the
azure
cluster
and
then
take
a
look
at
the
pods
that
are
running
in
the
WordPress
namespace.
So
these
were
just
created
and
you
can
see
there
they're
currently
running
in
a
NIC
container.
C
So
this
is
part
of
the
rustic
restore
process
that
Valero
is
executing.
Now
this
may
may
take
a
minute
or
two
in
the
azure
cluster
were
dynamically
provisioning.
Empty
volumes
were
then
running
the
rustic
restore
process
to
actually
take
the
contents
of
those
persistent
volumes
from
the
GCP
cluster
and
we're
storing
them
into
these.
These
new
empty
TVs,
so
this
may
take
a
minute
or
two
so
just
bear
with
it.
C
Just
going
back
to
the
the
storage
class
mapping,
does
this
new
feature
that
we
added
in
1.1
is
something
that
we
heard
a
lot
from
users,
particularly
for
this
migration
scenario,
because
a
lot
of
times
as
you're
migrating
across
different
providers,
the
storage
class
names,
don't
don't
line
up,
and
so
you
need
a
way
to
be
able
to
modify
those
as
they're
coming
into
the
new
provider.
So
we're
pretty
excited
to
be
able
to
to
support
this
natively
going
forward
all
right.
C
C
So
looks
like
this
one
just
taking
a
little
bit
longer
to
provision
the
disk,
but
it's
it's
finally
coming
up
so
alright.
So
now
that
WordPress
pod
is
up
and
running
and
I
just
take
one
more
look
at
the
status.
The
restore
will
see
that
it's
completed,
so
that's
a
good
sign,
and
so
now
the
last
thing
that
I
need
to
do
is
actually
look
at
the
services
in
the
WordPress
namespace,
because
I
need
to
get
the
IP
address
for
this
new
service.
It's
running,
Ian's,
Azure
and
so
I'll.
C
Take
that
and
just
switch
over
to
a
browser
window
and
I'll
pull
it
up
and
boom
there
we
go.
So
we
have
our
WordPress
site
up
and
running.
We
have
our
CNCs
blog
post,
and
this
is
this
is
now
being
hosted
from
Azure,
so
yeah,
so
that
pretty
much
concludes
the
demo.
I'm
gonna
stop
sharing
my
screen.
Tom.
Do
you
want
to
reshare
the
presentation.
C
Right,
so
just
quickly,
so
as
I
mentioned
we're
currently
on
velaro
1.0,
we
added
a
handful
of
stability
and
usability
features
in
that
release.
So
one
of
the
main
ones
was
the
Valero
install
command
to
make
it
really
easy
to
get
up
and
running
with
falero.
We
also
did
some
work
on
the
Community
Supported
home
chart,
so
we're
now
officially
supporting
the
home
chart
going
forward
as
an
installation,
mech
mechanism,
and
then
we
also
improved
our
our
plugin
integration.
C
So
we
improved
stability
and
the
developer
experience
there
and
our
rustic
integration
for
doing
file
level
backups
is
is
considered
beta
as
with
Watteau
and
we're
currently
working
on
on
1.1.
So
this
should
be
coming
out
by
the
end
of
the
summer.
We
have
a
handful
of
different
features
here,
so
we
have
been
doing
some
prototyping
of
an
integration
between
velaro
and
the
CSI
snapshot
api's.
B
Okay,
fantastic
Steve.
Thank
you
so
much
the
demo
was
was
really
great
and
glad
nothing
got
stuck.
So
that
was
a
live
demo
folks.
So
one
thing
I
wanted
to
draw
your.
You
know
we're
very
involved
with
community.
We
encourage
community
involvement
with
with
Valero,
and
one
of
the
things
that
we're
doing
right
now
is
it's.
Launching
literally
today
is
we're
doing
a
data
protection
survey.
So
this
is
a
data
protection
survey
for
for
cloud
native
backup.
B
B
So
speaking
of
the
Valero
IO
website,
that
is
where
you
can
find
Valero
and
any
blog
posts
and
and
other
valuable
links
like
to
our
github.
You
can
find
us
on
github
at
hefty
o
Valero.
Also,
please
follow
us
on
Twitter
at
Project
Valero,
for
the
latest
news
and
I'm
certain
that
we'll
be
tweeting
out
about
the
survey
and
also
once
the
survey
results
are
posted,
so
go
ahead
and
follow
Project
Valero
there
for
all
the
latest
news
on.
B
B
So
the
other
thing
you
can
do
is
you
can
join
our
mailing
list
at
project
molera,
which
is
on
the
on
Google
Groups
and
the
Valero.
We
also
community
meetings
twice
a
month.
We
just
had
one
a
couple
of
days
ago,
they're
the
first
and
third
Tuesday
of
every
month,
and
you
can
find
out
more
about
that
on
our
github
at
hep.
B
D
Of
it,
if
you
could
answer
these
questions,
we
get
have
some
good
ones,
so
we
have
about
eight
minutes
in
the
lobby.
If
we
could
blow
through
all
of
them,
we
have
about
six
I'm
going
to
try
to
start
with
a
straight
forwards
first.
So
if
we
need
a
time
for
the
discussion,
we
have
a
little
bit
of
time.
So.
C
Yeah
I
can
tackle
that
one
syllable
yeah,
so
we're
looking
at
integrating
velaro
with
the
snapshot,
ap
eyes
that
are
being
added
to
CSI,
and
so
the
the
snapshot
api's
mean
that
for
anyone,
any
storage
provider
who's
implementing
CSI,
if
they
implement
the
snapshot
API,
then
than
any
consumer
of
CSI,
will
be
able
to
take
advantage
of
that.
And
so
we're
looking
at
basically
adding
integration
between
velaro
and
those
snapshot.
B
Yeah
I
would
just
add
you
know
in
a
CSI
world
it
vastly
increases
the
number
of
storage
providers.
It
can
be,
can
underpin
your
kubernetes
clusters,
which
also
means
that
Beth
slowly
expands
the
number
of
storage
providers
that
we
can
provide
backup
for
so
so
so
CSI
is
very
promising.
We're
following
it
very
closely.
B
Yeah,
so
so
on,
prim
there's
there's
a
number
of
ways
to
do
it.
First
of
all,
you
know:
backups
are
kept
into
and
and
an
object
store
and
so
on
prim
you
can
run
a
an
s3,
compatible
object
store,
or
if
your,
if
your
storage
provider
has
an
s3
compatible
object
store,
you
can
store
your
your
backup
data
there.
You
can
also
install
a
an
open
source
project
like
Mineo,
for
instance,
to
provide
that
backup,
location
and
run
that
either
in
your
cluster
or
alongside
a
cluster
in
your
own
frame
environment.
D
C
I'll
take
that
so
there
are,
you
know
there
are
a
set
of
of
kind
of
standard
orders
that
need
to
be
respected
during
a
restore.
So,
for
example,
you
typically
want
to
restore
a
persistent
volume
before
a
persistent
volume
claim,
and
so
Valero
is
aware
of
those.
But
it's
also
user
controllable.
So
there
there
is
a
flag
to
the
server
command
so
that,
if
you
have
any
sort
of
custom
orderings
that
that
you
need
to
follow
that
you
can
specify
those
there
and
then
I
guess
one
other
one.
C
Other
angle
to
that
is
that
if
you
are
writing
a
plug-in
for
Valera
or
restore
item
action
to
customize,
how
Valera
restores
a
resource
you're
able
to
have
that
plug-in
kind
of
return,
additional
related
resources
that
should
be
restored,
and
so
using
that
you
can,
you
can
have
some
additional
control
over
how
things
are
restored,
so
happy
to
dig
into
that
some
more
in
detail
offline.
But
that's
that's
kind
of
the
overview.
C
D
I
have
there's
a
good
product,
really
good
question.
The
question
is:
how
can
is
their
plan
to
make
Valero
more
complete
by
having
features
to
support
snapshots
retention
policy
in
templating
and
as
far
as
templating?
It
would
be
so
that
you'll
be
known
what
it's
being
backed
up
and
the
steps
that
need
to
be
performed
in
the
container
before
the
backup
is
being
created.
B
Yeah,
actually
so
we
we
have
features
for
a
noun
to
solve
for
a
number
of
those
we
have
for
deciding
what
what
is
included
or
excluded
from
a
backup
we
do
have
included,
exclude
actions
that
you
can
that
you
can
use.
We
also
support
snapshotting
both
on
cloud
providers
today,
which
some
of
the
features
that
that
Steve
showed
in
the
first
in
the
first
example
of
the
demo
today
also
our
CSI
support
would
be
is
looking
specifically
at
doing
snapshotting,
for
instance,
so
so
I
think
and
currently
feel
was
there
another
things
I
had.
B
So
retention
policy
is
really
really
good,
so
you
do
have
the
ability
within
Valera
to
put
what's
called
a
TTL
or
time-to-live
on
your
backups
and
velaro.
Will
when
it
backs
those
things
up,
will
automatically
do
garbage
collection
and
and
remove
those
ancient
backups.
So
that's
effectively
cleaning
up
your
backup
targets
as
it
goes
along.
So
if
you
wanted
to
save
something
for
30
days,
that's
the
default
TTL.
B
D
C
Yessir,
I
would
say,
within
within
a
major
version,
so
all
one
dot,
X
versions
will
support,
restores
of
any
backup
created
with
with
say
one
dot.
Oh,
it's
possible.
There
could
be
breaking
changes
over
major
versions,
but
I
think
will
always
provide
data
migration
scripts,
if
that's
the
case,
so
that
users
always
have
a
path
to
be
able
to
restore
their
older
backups
yeah.
B
B
Wikipedia
you
can
find
out
on
the
wiki.
You
can
find
that
those
things
and
use
those
concepts
to
make
a
backup
plan
that
suits
your
own.
Your
own
particular
use
case
and
then
use
Valero
schedules
to
you
know
effectively
codify
that
policy
and
Valera
will
will
adhere
to
that
and
and
and
be
able
to
manage
to
that
particular
your
set
of
recovery
time
objectives.
B
Okay,
I
want
to
thank
everybody
very
much
for
attending
today's
webinar.
It's
been
fantastic
for
us
to
get
the
word
out.
Please
take
our
survey.
I
would
love
to
hear
more
from
the
community
on
how
they're
thinking
about
back
up
visit
us
on
Valero
IO
and
for
additional
questions
you
can
come
visit
us
on
the
kubernetes
slack
channel
at
at
Valero
on
the
kubernetes
slack
we'd
love
to
love
to
interact
with
each
of
you.
Thank
you
very
much
for
your
time
today.