►
From YouTube: Data Protection in a Kubernetes Native World
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
Welcome
to
today's
cncf
live
webinar
data
protection
in
a
kubernetes
native
world,
I'm
libby
schultz
and
I'll
be
moderating.
Today's
webinar
we'd
like
to
welcome
our
presenter
today,
michael
cade,
a
technologist
from
castin
a
few
housekeeping
items
before
we
get
started
during
the
webinar
you're,
not
able
to
talk
as
an
attendee.
There
is
a
chat
box
at
the
top
right
corner
and
underneath
there's
a
subcategory
of
q,
a
chats
if
you
can
put
all
of
your
ch
all
of
your
questions
there
we'll
get
to
as
many
as
we
can
at
the
end.
A
A
B
B
So
my
life
is
very
much
around
data
management
data
protection
and
I
very
much
like
probably
many
of
you
on
the
on
the
call
or
listening
to
the
recording
come
from
that,
I'm
not
going
to
call
it
traditional
too
much
and
I'm
going
to
try
not
to,
but
that
virtualization
space
around
vmware
hyper-v
and
being
able
to
leverage
that
that
the
infrastructure
that
we've
that
we've
come
to
know
over
the
last
10
15
years.
B
As
our
as
our
platform
to
to
get
things
done,
I
have
a
huge
focus
around
the
community,
not
only
sharing
a
lot
of
content
from
both
that
world,
as
well
as
into
the
new
cloud
native
and
kubernetes
world,
but
also
around
just
generally
helping
others
like
answering
those
questions
and
just
being
present
and
and
helping
others
through
this
ever
ongoing
learning
journey
that
we
all
have
in
here.
So
by
doing
that,
I'm
either
blogging
on
my
personal
site
that
you
can
see
listed
there,
either
creating
demos
and
walkthroughs.
B
On
my
youtube
channel
articles
and
etc,
on
linkedin
and
just
generally
being
present
on
on
social
media,
not
only
learning
from
the
community,
but
also
trying
to
give
back
as
much
as
I
possibly
can.
That's
got
me
into
the
position
that
I'm
that
I'm
in
today
so
yeah.
I
have
a
key
focus
around
technology,
such
as
cloud
native,
as
I've
mentioned
around
automation,
infrastructure
as
code
etc.
But
predominantly
I
focus
around
data
management,
both
both
new
and
old
and
and
everything
in
between
so
with
that,
let's
jump
into
it.
B
I've
been
hovering
around
this
world
for
the
last
two
years
and
only
really
just
recently
moved
over
to
to
casten
to
really
focus
in
efforts
around
the
data
management
space
in
this
in
this
area.
So
very
much
recently
moved
over
with
a
with
a
complete
intention
of
of
being
being
part
of
this
space
and
helping
educate
the
the
requirements
around
data
management
here.
So,
as
I
mentioned
around
having
a
very
traditional
infrastructure
landscape
background,
but
we
can
all
see
that
there
is
a
fast
adoption
of
kubernetes
and
it's
really
taking
off.
B
Whilst
today
the
automated
deployment,
the
scaling
is
in
a
good
place
and
consumable
for
for
anyone
by
our
on-premises
or
in
the
public
cloud.
Well,
there's
still
so
much
more.
That
can
be
done
and
should
be
done.
B
Although
we're
going
to
touch
on
some
of
the
some
of
those
points
that
are
going
to
help
us
accelerate
and
this
as
a
community
accelerate
into
leveraging
kubernetes
more
for
for
the
wider
goals
around
container
orchestration
automated
deployment,
but
whilst
also
thinking
about
some
of
those
some
of
those
topics
that
we
maybe
don't
think
about
very
much
top
of
mind.
Or
traditionally
we
haven't
thought
about
top
of
mind.
B
So
today
we're
going
to
talk
about
today,
as
in
the
kubernetes
that
we
that
we
have
today,
what
where
we
are
and
and
how
big,
how
important
adoption
rates
are
and
and
how
they're
growing
we're
they're
going
to
look
at
the
future
and
how
we
see
this
space
going
from
a
data
management.
A
specific
data
management
point
point
of
view
and
a
key
part
that
goes
hand
in
hand
with
that
data
management
is
the
storage.
The
kubernetes
storage
is,
is
your
kubernetes
storage
ready?
Are
people
using
it
in
production
and
what
we're
really
getting
at?
B
So
I
feel
like
it's
very
similar
to
what
we
saw
from
a
virtualization
point
of
view.
I
say
quite
a
bit
around
for
those
that
remember
things
like
vsphere
3.5
and
taking
that
that
early
step
into
into
the
into
the
water
there
and
then
to
see
how
that
evolved
over
time
and
how
everything
was
made
very
simple
and
easy.
B
I
remember
those
days
back
in
the
3.5
days
where
we
were.
I
was
a
professional
services
consultant,
so
I
was
going
out
and
I
was
implementing
vsphere.
I
don't
believe
that
you
potentially
need
that
that
level
of
service
anymore
with
vsphere,
because
it's
it's
generally
or
any
virtualization,
because
they're
very
much
hit
hit
the
easy
button
and
the
adoption
is,
as
far
out
grown,
the
the
industry
so
whereas
kubernetes
we're
probably
there,
but
I'm
going
to
touch
on
some
of
the
some
of
the
areas
where
and
why.
B
We
think
that
this
world
is
going
to
accelerate
much
faster
than
what
we
saw
from
a
from
a
virtualization
era.
And
one
of
the
first
things
to
to
note
is
obviously
the
cncf
landscape
that
has
been
evolving
over
the
last
year
and
the
few
years
that
I've
at
least
been
been
looking
at
this.
B
This
very
noisy
but
relevant
chart
of
all
of
the
different
areas
that
are
associated
to
kubernetes
and
containerization,
but
also
like
just
in
general
cloud
native
workloads,
and
this
is
growing
exponentially,
but
within
reason
it's
allowing
us
to
do
so
much
more
with
that
platform,
and
this
is
something
this
ecosystem
is
much
wider,
much
broader
than
what
we
potentially
saw
in
the
virtualization
journey
as
well.
B
So
what
we're?
What
I'm
basically
saying
here
is
that
this
is
really
a
testament
to
all
of
the
projects
along
this
board
that
are
enabling
the
customer
or
the
end
user
or
us
on
the
call
to
have
choice
and
the
flexibility
of
choice
when
it
comes
to
delivering
on
a
service,
whether
it's
databases,
whether
it's
messaging,
whether
it's
application
deployment,
whether
it's
continuous
integration
or
or
delivery,
all
of
them
give
us
options
and
choice
and
choice
is
always
a
good
thing,
and
it's
maybe
something
that
we
didn't
have
in
that
in
that
world.
B
Before
and
again,
as
I've
already
mentioned,
I'm
very
much
coming
from
an
operations
point
of
view
and
something
that
we're
definitely
going
to
get
into
is
around
how
why
this
adoption
is
growing
so
fast
as
we
as
we
as
we
move
through
the
next
few
slides.
So
this
is
from
a
from
a
a
bit
of
research
that
vmware
carried
out
in
in
2020,
so
obviously
2020
happened.
B
But
ultimately,
you
can
see
here
that
60
of
the
people
that
were
asked
are
running
less
than
half
of
the
containerized
workloads
on
kubernetes,
and
this
this
number
actually
shocked
me
quite
a
bit
is
around
so
almost
that
same
60
are
running
fewer
than
10
kubernetes
clusters,
and
when
you
think
about
that,
okay,
a
cluster
doesn't
need
to
be
a
as
a
sizable
number
of
worker
nodes
that
enable
us
to
put
our
applications
on
there.
They
could
be
relatively
small,
but
to
have
10
of
them
kind
of
indicates
that
there
is
a.
B
There
is
clearly
an
adoption
here,
and
a
large
amount
of
those
are
are
running
more
than
10
kubernetes
clusters.
So
you
can
probably
guess
where,
where
and
who
are,
are
running
these
these
workloads
and
then
to
to
really
drill
down
into
that
those
respondents
that
are
running
kubernetes
in
production.
So
again,
almost
60
percent
of
those.
B
So
the
60
of
the
60
are
running
those
kubernetes
clusters
in
production
and
then
a
further
20
of
those
have
a
huge
50
or
more
clusters,
which
again
just
highlights
how
how
big,
how
big
of
a
footprint
could
be
out
there
in
in
the
kubernetes
world
and
how
people
are
vastly
adopting
this
new
newish
technology.
I'm
not
saying
it's
new.
B
I
would
probably
wager
that
that
we
saw
maybe
five
years
for
virtualization
to
really
become
the
standardized
approach
for
for
a
platform
for
an
environment,
and
this
is
the
exciting
piece.
Is
that
with
the
numbers
that
we
just
mentioned
the
vmware
gleaned
from
that
that
report?
This
gives
us
the
the
visibility
of
well,
it's
going
to
be,
and
it's
only
going
to
continue
to
carry
on
being
faster
and
faster
than
than
we
maybe
once
thought,
because
we've
we've
lived
through
that
virtualization
piece
as
well,
and
one
of
the
big
influences
around.
B
B
So
what
we
mean
by
day,
one
is
the
initial
challenges
around
provisioning,
installing
rolling
out
the
kubernetes
clusters
have
kind
of
been
addressed.
It's
really
quite
I'm
not
going
to
say
simple,
but
it's
relatively
easy
to
get
up
and
running
from
a
day
one
perspective
and
have
have
the
ability
to
start
leveraging
a
kubernetes
cluster
and
the
orchestration
methods
behind
it
for
your
applications.
B
B
Things
will
obviously
be
working
towards
making
that
even
simpler
and
more
and
easier
for
for
the
operations,
but
also
for
the
developers
to
consume,
but
the
likes
of
the
public
cloud
have
definitely
enabled
that
that
that
easy,
spin
up
and
and
spin
down,
if
need
be,
of
of
a
kubernetes
cluster,
but
where
we're
seeing
a
huge
focus,
which
is
again
quite
refreshing
from
a
backup
guy,
is
now
we're
focusing
well
we're
getting
to
focus
on
day
two,
but
also
focusing
on
day
two
much
sooner
in
that
race
to
having
that
standardized
approach
to
having
kubernetes
as
a
platform.
B
So-
and
it's
not
just
backup,
I
put
backup
in
that
data
management
piece
and
highlighted
that,
but
also
it
gives
us
chance
to
highlight
things
like
security
and
observability,
and
one
of
the
things
that
we've
seen
throughout
2020
with.
Obviously
everything
else
that's
gone
on
is
the
increased
news
around
security
things
like
ransomware
things
like
just
outages
around
malicious
activity
with
inside
your
business
data
management
challenges
around
access
of
accessibility
of
data,
and
these
are
all
that.
B
How
do
we
bring
that
further
or
closer
to
the
top
of
the
list
and
start
thinking
about
this
before
we
think
of
it?
As
an
afterthought
like
we
potentially
have
done
in
the
in
the
past,
it's
always
been,
and
this
is
my
experience-
is
that
it's
always
been.
We
look
at
the
shiny
new
tin.
We
look
at
the
shiny
new
stuff.
First,
the
the
storage,
the
compute,
the
networking
before
we
then
get
down
the
line.
Then
we
look
at
oh
now,
we'll
look
at
the
backup.
Now
we'll
look
at
the
security.
B
B
They
that's
how
they
believe
and
then
everything
else
and
then
there's
another
group
that
think
about
stateful-
and
you
can
just
see
here
that
there
are
a
huge
percentage,
half
and
sometimes
more
than
half,
where
a
stateful
set
is
being
used
in
their
containerization
in
their
kubernetes
environment.
So
there
is
clearly
a
use
case
there
for
protecting
and
working
with
that.
B
And
so
then
we
look
at
more
more
data
points.
So
55
of
organizations
indicate
that
half
or
more
of
their
container
applications
are
stateful,
so
that
last
report
that
last
slide
that
I
was
touching
on
is
a
there's
a
report.
That
systig
did,
I
think
in
maybe
in
2019.
So
obviously
we
would
expect
this
to
have
risen
quite
dramatically
in
in
2020,
whereas
this
is
going
back
even
further
and
this
is
from
451
and
they
say
that
55,
but
we're
roughly
around
the
same
numbers
in
terms
of
adoption
and
people
using
stateful
applications
and
generally.
B
Another
potential
misconception
is
that
when
we're
talking,
stateful
workloads
or
stateful
applications
deployed
on
kubernetes,
we're
thinking,
just
databases
we're
thinking
of
those
traditional
sql
or
nosql
databases
we're
not
necessarily
thinking
of
of
things
like
message.
Queues
like
batch
and
data
streaming
and
leveraging
other
other
tools
like
like
kafka
out
there
so-
and
this
is
just
going
to
give
you
an
understanding
of
well
these.
This
is
happening
and
people
are
using
these.
These
applications
out
there
in
a
stateful
stateful
way.
B
We
have
to
work
together
to
make
sure
that
we're
all
working
together
to
make
sure
that
the
application
is
is
being
looked
after
in
the
best
possible
way
and
it
needs
to
be
updated
regularly.
It
needs
to
be
improved
and,
and
all
of
that
good
stuff
that
really
kubernetes
enables
us
to
do
but
again
not
having
to
be
separated
like
it.
B
Maybe
once
was
before,
and-
and
this
might
be
the
same
resource
like
there's
a
lot
of
devops
engineers
out
there
that
have
been
been
able
to
grasp
both
the
application
development
cycle,
as
well
as
the
the
infrastructure
or
the
platform
and
the
hardware
resources
underneath
or
at
least
the
resources,
and
that's
obviously
fine
or
in
bigger
larger
environments.
There
might
be
still
a
developer
team
and
an
operations
team
that
that
carry
both
both
flags
or
at
least
each
flag,
and
they
they
just
simply
have
to
work
together.
B
So
as
an
opera
as
an
operations
person
myself,
understanding
the
requirements
and
goals
of
development
helps
me
better,
prepare
the
infrastructure
platform,
and
then
this
day,
two
operation
we
speak,
of
which
in
turn
means
I'm
not
getting
an
application
stack
over
the
fence
and
getting
told.
Well
you
deal
with
that
you're
on
call.
B
Now
you
make
sure
that
the
app
that
you
have
no
idea
about
has
to
stay
up
and
running,
so
what
we're
gonna
drill
into,
and
one
of
the
biggest
things
here
and
again
I'll
talk
about
where
I've
come
from,
because
I
think
it
shines
a
light
on
not
much
has
changed
in
in
regards
to
at
least
data
management
security-
probably
not
as
not
so
much
as
well.
In
that
we
still
have
to
secure
our
environments.
B
So
how
do
we
look
at
this
from
a
kubernetes
native
data
management,
because
this
is
one
of
the
things
we're
definitely
going
to
touch
on,
because
a
lot
of
the
conversations
that
I've
been
having
is?
Could
I,
if
I'm
running
a
a
node
based
cluster,
that
I
have
access
to
the
nodes
in
one
of
the
public
clouds
or
potentially
on
premises?
B
Could
I
not
just
use
the
same
tool
that
I
did
in
my
virtualization
environment
to
protect
my
workload
today?
In
kubernetes,
and
just
look
after
that
and
to
a
certain
degree-
yes,
you
can
but
not
to
the
same
effect
as
something
that
has
the
full
visibility
in
the
api
access
as
something
that's
natively
built
for
data
management
in
that
space.
So
when
I
say
about
backup
recovery,
ultimately
backup
is
is
a
form
of
a
an
insurance
policy.
B
It's
about
having
a
point-in-time
copy
of
your
data
in
a
secure
location
that
allows
you
to
recover,
based
on
a
failure
scenario,
and
you
could
literally
drag
and
drop
that
that
description
into
any
of
the
previous
platforms
that
we've
ever
come
across,
whether
it's
physical,
whether
it's
virtualization,
whether
it's
kubernetes
and
whatever,
comes
later
on
down
the
line
as
well,
but
in
terms
of
a
kubernetes
native
or
a
cloud
native
data
management
perspective.
B
The
kubernetes
platform
could
be
running
anywhere;
it
could
be
anywhere
well.
What
about
that?
Application?
Mobility,
we've
just
said
about
it
being
much
more
focused
and
brings
in
that
developer
team
or
brings
in
the
operations
team
to
now
work
together
to
make
sure
that
you've
got
the
best
of
both
worlds
so
that
you
can
work
together
to
give
your
application
the
the
best
best
treatment
it
needs,
but
what
we
also
need
to
do
with
our
data
management
hat
on.
We
need
to
think
about.
B
B
We're
now
thinking
about
cloud-based
workloads
such
as
availability
zones
and
regions
and
multi
and
hybrid
cloud,
so
you
might
still
have
site
a
and
that
site
a
might
end
up
being
your
test
and
development
environment,
but
your
production
is
now
in
one
of
the
public
clouds
and
but
from
a
disaster
recovery
point
of
view.
They
might
all
mean
something
if
you
were
to
lose
access
to
the
public
cloud
or
lose
access
to
site
a
on
premises.
B
B
But
now,
if
you
spin
that,
on
its
head
around
a
virtual
machine,
a
large
operate
so
an
operating
system
sitting
on
an
abstracted
layer
of
hardware
and
an
application
that
lives
on
there,
maybe
that's
a
sql
database.
Maybe
it's
a
database
of
some
description.
Maybe
it's
another
application,
and
now
we
look
at
kubernetes.
Well,
it's!
No!
B
It's
not
the
same,
an
application
I'm
going
to
get
into
this
in
a
little
bit
more
detail
when
I've
got
some
visuals
to
share,
but
it's
not
the
same,
because
an
application
is
now
broken
down
into
many
different
microservices
that
enable
so
much
more
from
a
dynamic
point
of
view.
So,
whether
that's
from
a
rescheduling
point
of
view,
whether
that's
from
an
update
point
of
view,
it
gives
you
so
much
more
flexibility
to
not
have
to
treat
that
virtual
machine
like
a
pet,
which
we
know
we
all
have
done
in
the
past.
B
So
where
does
that?
I
mentioned
around
vm
based
backup
and
where
does
that
fall
short.
So,
first
of
all,
if
you've
got
a
virtual
machine
and
you've
got
an
application
on
each
one,
then
great
virtual
machine
backup
is
the
way
to
be
able
to
protect
that
that
workload
and
I
kind
of
touched
on
traditionally
we
were
taking.
B
We
were
able
to
take
your
agent-based
backup
for
your
physical
machines
and
bring
that
into
your
virtual
world,
but
you
were,
you
were
losing
so
much
of
the
benefits
of
the
underlining
hypervisor,
so
the
virtualization
host,
by
not
being
able
to
go
in
there
and
take
out
and
leverage
those
apis,
which
is
a
very
similar
point
to
what
we're
going
to
get
across
here
as
well.
When
we
walk
through
this
because
as
soon
as
we
start
putting
kubernetes
across
our
virtual
machines,
well,
then
the
vm-based
solution
loses
all
application
visibility.
B
We
have
no
idea
what
that
application
is,
or
even
where
it
lives,
especially
because
it's
not
a
one
app
to
one
host
situation
when
it
comes
to
kubernetes,
it's
generally
split
out
and
potentially
here
in
the
diagram,
you'll
see.
Okay.
This
is
a
this
is
a
perfect
scenario.
If
you've
got
app
one
that
lives
on
node,
one
and
you've
got
app
two
that
lives
on
node,
two
and
and
so
on
and
so
forth.
But
that's
also
not
the
case.
B
We
split
those
those
applications
down
into
microservices,
which
gives
us
so
much
flexibility
and
choice
and
all
of
the
scalability
of
containerization.
B
But
it's
not
always
it's
not
always
as
simple
as
everything
lives
on
the
same
host.
So
what
you'll
see
there
on
the
diagram
that
no
single
vm
has
a
complete
application.
Those
applications
are
spread
across
multiple
virtual
machines
or
multiple
worker
nodes
within
your
kubernetes
cluster.
So
as
soon
as
you
were
to
take
that
virtual
machine,
one
backup,
yeah,
okay,
you'd,
get
a
bit
of
that
one
and
a
bit
of
that
two
and
a
bit
of
app
three,
but
I
know,
and
potentially
the
storage.
That's
also
connected
to
that.
B
B
So
it's
not
so
not
such
a
great
way
of
being
able
to
protect
those
those
workloads
and
then
not
only
that
is
that
break
down
that
application,
even
more
into
all
of
the
secrets,
all
of
the
artifacts
that
that
come
with
that
that
application,
that
name
space
all
of
the
things
that
build
up
the
the
componentry
of
that
of
that
application
and
being
able
to
protect
those
as
well
as
part
of
that
same.
This
is
where
that
vm
based
backup
will
fall
short
considerably.
B
Is
that
well
you're
just
not
going
to
have
visibility
into
what
that
is
unless
you've
got
direct
access
into
the
api,
the
kubernetes
api
to
be
able
to
achieve
that
so
again,
what's
different
in
that?
Is
that
because
we're
abstracting
the
the
layer
of
we're,
not
abstracting
the
hardware
so
much
anymore,
we're
abstracting
the
operating
system,
which
then
allows
us
to
really
focus
in
on
the
application
scale,
and
a
focus
on
that
that
application
scale
is
a
key
part
of
the
wider
kubernetes
ecosystem
and
also
being
able
to
dynamically.
Do
that?
B
B
I
don't
really
care
so
much
in
a
kubernetes
world
where
that's
living
what's
what's
happening
under
the
hood,
because
we're
all
leveraging
the
same
kubernetes
or
kubernetes
apis.
So
the
storage,
storage
vendor
a
and
storage
vendor
b,
just
look
the
same
to
kubernetes.
Yes,
there
might
be
a
few
bells
and
whistles
different
differently
written
into
the
csi,
but
ultimately
it
doesn't
matter
because
what
we
need
to
also
consider
is
that
restore
capability
when
we
restore,
we
want
to
be
flexible
in
how
we
restore
that
back
into
a
different
kubernetes
cluster,
potentially
with
different
storage.
B
B
In
fact,
this
customer
has
now
grown
over
the
100
node
mark,
so
the
the
capacity
everything
else
has
likely
doubled
along
with
that,
with
the
components
and-
and
really
the
key
focus
here
is
that
it
wasn't
operations
that
that
made
that
call
or
made
that
made
that
decision
it
was
based
on
the
is
very
much
developer,
ran
or
devops
ram
in
that
they're
working
together
as
a
team
to
deliver
what
is
needed
from
a
from
a
day.
B
Two
data
management
point
of
view
and
they've
got
the
the
use
case,
diversity
around
backup
disaster
recovery,
as
well
as
that
application
mobility
that
I
mentioned
across
a
multiple
subset
of
applications.
So
you
can
see
down
there.
We've
got
our
nosql.
We've
got
us
our
sql
databases,
but
also
think
about
those
other,
the
messaging
cues
that
I
mentioned,
as
well
as
the
batch
processing,
etc.
B
So
again,
that
brings
us
back
to
that
devops
and
that
shift
left
so
having
that
we're
not
really
focusing
on
the
infrastructure
anymore.
Really
we
don't.
We
don't
care
about
the
underlying
infrastructure,
we're
more
focused
around
the
application
and
the
delivery
method
of
that
application,
but
we
need
to
incorporate
that
data
management
or
our
backup
needs
into
day
one.
So
as
part
of
that
application
development
cycle,
we
need
to
include
that
that
forefront
into
into
protecting
protecting
those
workloads.
It's
not
an
afterthought
when
it
comes
to
protecting
those
applications.
B
Obviously
there's
a
lot
of
other
areas
within
the
devops
and
the
shift
left
around
infrastructure
as
code,
and
this
is
how
the
operations
team.
This
is
definitely
how
I
first
approached
the
cloud
native
world
was
around
start
learning,
other
other
tool
sets
and
other
ways
to
make
your
life
easier
around
using
infrastructure
as
code,
but
also
things
like
dynamic,
provisioning,
dynamic,
deploying
and
destroying
of
those
applications,
but
there's
also
that,
as
soon
as
you
increase,
more
automation
or
potentially
more
accidental
risk
via
self-service
becomes
that
need
for
that
backup.
B
So
then
just
quickly
moving
on
to
a
bit
around
security.
So
again
the
the
world
hasn't
changed
too
much
in
regards
to
the
requirements
around
security.
Maybe
2020
gave
us
a
a
good
indication
that
security
is
still
should
be
one
of
the
key
considerations
in
any
of
our
deployments
or
any
of
our
environments.
B
But
it
hasn't
really
changed
in
regards
to
obviously
our
backup
and
dr
requirements,
I've
kind
of
touched
on
that,
making
it
easy
to
deploy
factor
in
that
into
the
same
ci,
cicd
pipelines
that
you
have
automate
all
of
that,
because
who
wants
to
be
looking
after
backup
jobs
or
backup
policies
on
a
daily
basis?
We
just
want
them
to
work.
B
We
want
them
to
pick
up
those
those
applications
protect
them
in
the
way
that
we
want
them
protected,
and
we
kind
of
want
to
set
and
forget
that
and
make
it
extensible
so
that
people
can
hook
other
tasks
into
that
as
well
and
then,
from
a
security
point
of
view.
The
same
words
that
we
saw
the
same
methodologies
that
we
saw
in
other
platforms.
Other
environments
are
still
here.
We
still
have
the
requirement
to
encrypt
our
data.
We
still
have
access
rights
and
access
management.
B
We
still
have
role-based
access
control,
but
the
important
part
is
is
being
able
to
leverage
the
same
apis
that
as
used,
whether
it's
using
aws
govcloud
like
it,
is
here
to
whatever
it
is
in
another
public
cloud,
environment
somewhere
else,
and
then
brings
back
to
to
my
to
my
like
background.
If
you
like,
so
the
operator
challenges-
and
I
think
that
first
point
here-
the
skills
gap
and
the
talent
shortage
is
critical,
and
I
think
there
is
a.
B
A
an
understanding
or
a
misconception
is
probably
a
better
word
around
kubernetes
is
hard
and
okay
depends
on
the
definition
of
hard,
but,
as
we
mentioned
around
deployment,
especially
for
the
operator,
the
deployment
has
got
very
significantly
easier
to
deploy,
but
also
the
understanding
around
the
key
components
and
the
architecture
of
kubernetes
is
deemed
difficult.
B
When
actually-
and
I
can
put
my
hand
on
my
heart
and
say
this-
is
that
after
two
years
of
educating
myself
so
in
my
own
technologist
way,
educating
myself
and
then
having
to
up
skill
and
speed,
my
education
up
is
that
it's
really
not
as
daunting
as
it
maybe
first
seems
so.
B
The
the
biggest
advice
that
I
would
give
there
is
about
just
get
hands-on
and
I'll
touch
on
something
at
the
end.
Where,
if
you
don't
have
access
to
something,
then
maybe
we've
got
a
a
helping
answer
to
that,
but
I
think
being
involved
being
hands-on
and
trying
things
in
a
kubernetes
cluster
is
the
key
to
being
able
to
understand
and
and
accelerate
that
learning
curve
that
that
you
have
the
other
key
change,
and
this
will
be
difficult
for
a
lot
of
people.
B
Around
operations
traditionally
focused
around
infrastructure
and
keeping
those
the
lights
on,
making
sure
that
the
the
speeds
and
feeds
were
there
for
the
application,
but
generally
looking
at
always
the
back
end
and
keeping
the
uptime
keeping
the
hardware
or
the
keeping
the
the
platform
running.
B
B
You're
not
left
behind
from
a
from
a
scalability
point
of
view
and
yeah,
I'm
going
to
touch
on
this
a
little
bit
more
because
this
will
be
quite
alien
to
a
lot
of
operators
that
have
come
from
the
virtualization
world
and
the
being
able
to
rapidly
deal
with
the
kubernetes
releases,
but
also
everything
else.
That
comes
with
that,
because,
okay,
I'm
going
to
touch
on
the
kubernetes
release
and
how
quickly
that
moves,
but
think
about
everything
else.
B
B
So
what
you
also
need
to
consider
from
a
data
management
point
of
view
is
that
if
I
take
a
backup
in
january,
just
for
example,
here
well
come
october
october
november
december.
I
still
need
to
be
able
to
restore
workloads
from
that
january
february
march,
but
obviously
then
I
don't
also
want
to
be
left
behind
from
an
infrastructure
or
from
a
devops
point
of
view.
I
don't
want
to
be
left
behind,
because
the
amount
of
features
that
are
in
these
releases
are
completely
game-changing
for,
for
for
many
businesses
as
well.
B
Okay,
so
and
I've
realized
I've,
I've
rattled
through
quite
a
number
of
slides
so
and
we'll
get
to
the
questions
in
a
in
a
few
slides
that
I've
got
left,
but
other
data
management
concerns
to
to
watch
out.
For
so
there
is
a
difference
between
sizing,
an
application
or
deploying
an
application
with
deploying
an
application,
a
stateful
set
within
your
kubernetes
environment.
B
B
B
I
think
again
to
a
nod
to
the
operations
is
we
have
to
understand
the
entire
stack,
the
operating
system,
the
kubernetes,
the
application,
the
database,
the
networking,
as
well
as
the
security
on
that
and
as
soon
as
we
can
understand
all
of
those
areas,
then
we
have
a
better
look
at
what
that
backup
requirement
or
what
that
data
management
requirement
needs
to
look
like
as
well
as
replication
like
do
we
need
to,
if
that
isn't
running
our
mission
critical
systems,
do
we
need
to
consider
replicating
that
or
having
a
disaster
recovery
plan
that
replicates
that
from
public
cloud,
a
to
public
cloud
b
or
back
on
premises,
because
h,
a
absolutely
factor
that
in
to
all
of
your
applications,
where
possible,
on
top
of
what
you
already
get
from
the
platform?
B
B
Colleagues,
if
we
haven't
all
been
a
victim
of
some
sort
of
cyber
security
attack,
ransomware
attack,
but
we
know
that
it's
potentially
inevitable
that
we're
going
to
be
attacked
at
one
point
and
I
think
that's
the
best
way
that
I've
been
telling
people,
especially
in
the
virtualization
world,
is
that
if
you
arm
yourself
with
the
possibility,
a
high
possibility
that
you
will
be
attacked
by
ransomware.
B
B
You
have
different
plans
for
for
different
failure
scenarios,
but
making
sure
that
it's
not
just
a
piece
of
paper
and
that
you
physically
can
walk,
walk
through
that
run
book
and
make
sure
that
your
business
data,
your
important
data,
is,
can
be
up
and
running
again
in
a
in
the
desired
amount
of
time
and
then
also
making
sure
that
so
we've
spoken
about
two
or
three
different
areas:
around
storage
being
a
huge
part
of
the
data
management
piece,
whether
that's
storage
from
a
where
you're
running
your
database,
where
you're,
storing
your
persistent
volumes
or
where
you
are
actually
landing.
B
Your
backups
you're
exporting
your
backups
out
to
object,
storage
or
potentially
a
file
system.
But
looking
at
that
from
that
angle,
so
your
data
management
practice
should
be
well.
Let's
take
advantage
of
those
ecosystem
integrations
from
a
storage
point
of
view.
Also,
we
need
to
make
sure
that
we're
application
consistent
when
it
comes
to
databases
and
and
nosql
or
other
system
hooks.
Let's
make
sure
that
we're
taking
a
the
best
possible
backup
that
we
can
of
those
applications.
B
Your
workloads
today
tomorrow
in
a
year's
time,
is
completely
agnostic,
you're
able
to
run
anywhere,
but
also
consider
that
when
it
comes
to
your
data
management
software
and
how
you're
going
to
do
that
and
think
about
that,
you
want
to
be
able
to
protect
the
workload
regardless
of
which
public
cloud.
It
is
whether
it's
on
premises
which
distribution
you're
using
etc.
You
still
want
to
have
that.
B
You
don't
want
choice
to
you,
don't
want
your
data
management
choice
to
dictate
your
platform
is
what
I'm
trying
to
say
there,
and
just
before
we
wrap
up
here
and
get
to
the
questions,
there's
a
few
resources
and
they
are
very
vendor
agnostic.
So
we're
not
talking
about
our
product,
but
they
very
much
key
into
some
of
those
reasons
and
the
best
practices
around
data
management
and
also
kubernetes
native
backup,
so
very
much
a
some
resources
to
to
to
have
a
look
through.
B
Also,
if
you
are
just
beginning
and
just
starting
out
this
journey,
then
flippy
has
been
across
the
the
cloud
native
or
the
cncf
landscape
for
a
while,
and
I've
found
that
these
are
really
quite
easy
from
a
beginner's
point
of
view
to
understand
a
little
bit
more
about
cloud
native
and
in
particular,
casting
has
been
very
much
involved
from
a
the
50
in
space
and
and
focusing
around
cloud
native
recovery.
B
So
again,
there's
a
link
there
for
that
one,
and
just
to
summarize
some
of
the
points
that
we've
made
so
backup
and
recovery,
it
doesn't
change
the
importance
of
back
and
recovery.
Whether
you're
like
whether
you're
in
a
virtualization
world,
which
is
going
to
stand
by
your
kubernetes
cluster
or
at
least
you're,
going
to
be
probably
going
to
be
running.
Both
platforms
for
the
foreseeable
future,
at
least
and
backup,
is
still
important.
B
The
application
mobility,
the
ability
to
move
those
applications
freely
between
those
clusters,
disaster
recovery-
it
doesn't
stop
just
because
we've
gone
to
kubernetes,
it's
still
a
requirement,
but
also
look
at
a
platform
that
enables
the
multi
and
hybrid
cloud
or
can
work
across
multiple
environments.
It
can
work
against
multiple
storage
types
and
offerings,
and
it
also
offers
role-based
access
control.
B
It
should
be
built
for
kubernetes
leveraging
the
apis.
It
should
be
super
simple
to
use,
but
also
simple,
to
use
that
it
can
also
be
incorporated
into
the
ci
cd
pipelines
of
your
developers,
so
that
you
really
don't
have
to
have
that
that
afterthought.
When
it
comes
to
data
protection,
obviously
it
needs
to
be
supported.
B
Supportive
of
role-based
access
control,
as
I
just
mentioned,
but
also
the
native
apis
from
from
kubernetes,
and
have
a
rich
ecosystem
to
enable
that
multi
and
hybrid
cloud
approach-
and
the
one
thing
I
want
to
touch
on
here
last-
is
because
again
a
lot
of
us
won't
have
access
to
kubernetes
clusters
that
we
can
just
access
and
start
playing
around
with
player.
Might
not
be
the
right
word
or
messing
around
with
again,
probably
not
the
right
word,
but
learning
and
we've
recognized
that
at
casting
so
we
have
a
a
free.
We
have.
B
We
have
two
options:
there's
a
free
starter
edition
that
ultimately
allows
you
to
protect
those
workloads,
or
at
least
have
a
look
at
protecting
those
workloads
on
10
nodes
and
that's
free
forever.
B
But
then
also
there
is
a
hands-on
lab
that
allows
you
to
walk
through
the
provisioning
of
workloads,
applications,
postgres,
sql,
etc
and
actually
walk
through
what
that
looks
like.
So
it
gives
you
some
hands-on
experience,
rather
than
just
reading
the
white
papers.
Reading
the
resources
that
I've
mentioned
actually
gives
you
some
hands-on
there.
So
that's
where
I'll
I'll
leave
it
and
then
libby
has
there
been
any
questions.
A
A
All
right!
Well,
thanks!
So
much
michael,
that
was
a
great
presentation.
I
know
you've
handed
out
your
social
media.
So
if
anybody
has
questions
post
event,
you
can
always
reach
out
and
we
will
be
sure
to
get
this
online
and
get
the
slides
pulled
up
so
that
everyone
can
access
it
post
event
as
soon
as
possible
and
we'll
look
forward
to
seeing
everyone
at
another
cncf
webinar
soon.