►
From YouTube: Backing up your Kubernetes strategy - The myths & facts
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
I'd
like
to
begin
just
by
talking
about
the
kubernetes
landscape
in
2022,
so
everyone
is
is
probably
aware
of
this.
This
massive
shift
that
we've
seen
in
the
I
t
industry
over
the
past
five
to
ten
years
where
companies
are
taking
their
legacy,
applications
from
bare
metal
and
virtual
machines
and
they're
converting
these
and
and
evolving
these
to
using
containers
and
then
to
using
container
orchestration,
and
everyone
is
probably
aware
that
it
seems
that
kubernetes
has
pretty
much
won
the
war
in
container
orchestration,
and
so
we
wanted
to
share
this.
A
This
quote
from
idc
that
we've
seen
recently
that
they
predict
by
the
year
2024
that
net
new
production
grade
cloud
native
applications
will
increase
to
70
percent
and
that's
up
from
only
10
percent
were
containerized
in
2020,
and
this
is
all
thanks
to
this
shift
to
microservices
containers,
orchestration
and
the
devops
movement.
A
So,
with
you
know,
with
or
without
containers,
every
it
group
is
worried
about
the
downtime
of
their
applications.
Nobody
wants
downtime
and
downtime
costs
money
and
time,
so
these
are
some
quotes
that
we've
pulled
from
gartner.
A
That
says
that
each
minute
of
downtime
can
cost
a
business
up
to
5600
a
minute
and
91
of
organizations
that
just
one
hour
of
downtime
cost
more
than
300
000,
and
now
we've
had
the
increase
in
in
ransomware
over
the
last
five
years
and
now-
and
you
can
see
even
in
the
in
the
last
year
in
2020
that
increased
171
percent.
All
of
these
factors.
You
know
that
downtime
really
costs
money
and,
and
it's
not
just
costing
money,
it's
it's
costing
time.
A
So
I
was,
I
attended
an
I
t,
tech
talk
conference
a
few
weeks
ago
and
there
was
a
company
there.
That
was
talking
about
the
challenge
of
I
t,
keeping
up
with
the
pace
of
business
and,
and
you
know
what
that
involves
is.
Is
you
know
having
helping
having
your
items,
help
with
the
the
evolution
of
your
business
and
and
downtime
just
takes
away
from
that
time
so
aries?
You
know
every
minute
that
a
team
is
it
team,
is
spending
fixing
downtime.
A
You
know
that's
time
that
they're
not
able
to
spend
on
other
productive
things.
You
know,
I
think,
we've
all
heard
anna
dose
from
our
it
friends
saying
you
know
some
of
them.
Some
of
the
teams
just
feel
like
they're,
just
treading
water,
with
all
the
downtime
issues
and
solving
tickets,
as
opposed
to
working
on
productive
projects.
That
could
be,
you
know,
improving
and
growing
their
business.
A
So
you
know
these
are
all
things
that
we
want
to
avoid
and
all
things
that
we
want
to
address,
that's
something
that
trilio
has
been
helping.
Companies
do
since
2013.,
and
so
today
we
wanted
to
talk
about
some
myths
that
we're
hearing
in
the
kubernetes
landscape
related
to
to
to
protecting
your
applications
from
downtime.
A
So,
let's
start
with
myth
number
one
so
myth
number
one
is.
I
don't
need
backup,
because
all
of
my
kubernetes
applications
are
stateless,
so
this
may
have
been
true
a
few
years
ago.
In
fact,
I
attended
the
kubecon
trade
show
last
october,
in
los
angeles
and
over
that
three-day
period
I
talked
to
a
lot
of
companies
and
actually,
at
that
time
there
was
a
lot
of
truth
to
that.
So
there
wasn't
a
lot
of
people
that
were
doing
stateful
applications
in
kubernetes.
A
You
know,
kubernetes
was
designed
by
google
mainly
for
stateless
applications,
but
now
in
2022
that's
definitely
shifting
and
changing.
So
we
at
trillo
have
done
our
own
personal
customer
survey
about
this
to
ask
companies
how
many
you
know
how
many
of
them
are
using
stateful
volumes
in
kubernetes
and
an
overwhelming
majority
53
percent
said
yes,
they
were
and
interesting
enough.
15
said
that
said,
said
that
they
weren't
sure.
A
So
so
they
needed
to
to
see
what
the
state
of
their
applications
were
in
kubernetes,
and
then
we
also
looked
at
some
industry
statistics.
So
recently
the
cncf
did
a
similar
survey
and
again
just
over
same
results.
As
our
trilio
survey,
over
50
percent
were
saying:
yes,
we're
using
stateful
applications
in
containers
and
then
more
interesting.
A
You
know
there
was
slightly
over
20
saying
no,
but
then
there
was,
if
you
added
up
the
last
two
columns,
that
would
give
you
around
another
20
percent
that
say
they're,
either
evaluating
stateful
applications
in
containers
or
plan
to
do
it
within
the
in
the
next
12
months.
So
that
is
definitely
changing.
A
So
a
lot
of
companies
are
starting
with
that.
That's
kind
of
kind
of
the
legacy
way
of
doing
backups
is
relying
on
the
snapshots
that
come
from
your
storage
system,
but
there's
a
lot
of
limitations
and
challenges
with
that.
So
the
first
being
you
know,
if
you're
just
capturing
your
snapshots,
you
know
you're
relying
on
some,
maybe
some
scripts
to
tie
the
applications
to
those
snapshots
or
maybe
to
tie
some
databases
to
those
snapshots
so
you're,
relying
on
scripting
you're,
relying
on
individuals
that
are
writing
those
scripts.
A
It's
just
really
limitation,
so
incomplete
data.
So
you
know
if
you're,
just
relying
on
your
snapshots,
there's
a
lot
more
to
your
applications
than
snapshots.
There's
a
lot
of
metadata
associated
with
kubernetes
applications,
so
you're
not
capturing
your
entire
application,
if
you're
only
relying
on
snapshots
inability
to
scale.
So
you
know
as
these
snapshots
grow,
you
know
if
you're,
if
you
rely
relying
on
a
manual
scripting
process
to
piece
back
together
your
application
that
is
not
going
to
scale.
You
know
the
more
that
application
scales.
A
You
know
when
you
go
to
recover
that
application
and
trying
to
piece
together
what
snapshots
that
you
want
to
restore
and
how
is
that
going
to
tie
to
what
metadata
it
just
doesn't
scale
in
production
and
and
if
you're,
only
relying
on
snapshots
you're
more
successful
susceptible
to
disaster,
so
those
snapshots
typically
live
inside
the
same
storage
system.
That's
providing
storage
for
your
cluster
and,
if
that
entire
cluster,
or
that
entire
storage
system
goes
down,
you're
not
going
to
be
able
to
recover
from
that.
A
Okay,
myth
number
three:
my
legacy:
data
protection
solution
can
protect
my
containerized
applications,
so
this
kind
of
this
is
very
similar
to
the
second
myth.
You
know
where
companies
are
kind
of
going
along
with
what
they've
always
done
for
data
protection,
and
you
know,
and
in
those
days
where
you
had
siloed
applications,
monolithic
applications
that
lived
on
bare
metal
machines
or
that
lived
in
virtual
machines.
A
You
know
that
model
of
data
protection
was
very
much
based
on
the
storage
appliances.
The
storage
volumes
the
snapshots,
but
now
the
kubernetes
environment
is
so
much
more
dynamic.
It's
highly
scalable,
you
know
your
application
gets
distributed
to
some
random
number
of
worker
nodes.
That's
based
on
the
kubernetes
scheduler.
Those
worker
nodes
themselves
are
dynamic,
so
you
could
set
up
auto
scaling
such
that
worker
nodes
increase
as
your
application
grows.
A
Everything
is
highly
automated.
This
can
all
be
scripted
by
ci
cd
tools
and
policy.
Driven.
You
know,
multiple
personas
can
be
deploying
these
applications
so
really
the
traditional
data
protection
model
just
really
breaks
down
in
the
highly
evolved
kubernetes
environment.
So
you
really
need
a
data
protection
solution.
That's
been
designed
for
the
cloud
native
world
of
kubernetes
and
and
if
you
have
a
cloud
native
data
protection
solution
like
trilio,
you
know
these
solutions
will
give
you
speed.
You
know
you're
able
to
restore
your
apps
faster,
because
everything
has
been
planned
out
in
advance.
A
A
So
maybe
you
have
something
that's
on
premise
today
you
have
some
disaster
recovery,
ready
to
go
in
the
public
cloud
and
you're
able
to
restore
those
applications
very
quickly
and
then,
as
I
mentioned,
across
different
clouds,
so
you're
able
to
maybe
have
different
kubernetes
clusters
and
you're
able
to
take
point
in
time,
snapshots
and
move
those
around
to
to
different
application
clusters.
A
Okay,
myth
number
four
data
protection
is
only
about
backup
and
that
used
to
be
the
case.
You
know
you're
really
just
looking
for
things,
you
know
to
to
recover
from
any
kind
of
disaster,
and
that
was
the
reason
that
you're
taking
backup,
but
you
know,
there's
a
lot
of
other
infrastructure
challenges
that
teams
are
seeing
today.
You
know,
there's
application
uptime,
you
know
you
want
your
out.
You
want
a
lower
time
to
recovery,
both
in
cost
and
time
of
being
able
to
recover
your
application
to
any
point
in
time.
A
In
case
something
goes
wrong.
You
might
have
compliance
and
disaster
recovery
mandates.
Companies
in
different
industries
have
different
regulations
that
sometimes
they're
beholden
to
to
have
certain
rules
in
place
related
to
disaster
recovery.
Maybe
you
need
to
have
so
many
days
worth
of
backups,
and
maybe
you
need
to
keep
those
backups
for
for
some
set
retention
policy
that
could
even
be
many
years
in
some
cases
you're
able
to
quickly
bounce
back
from
outages
and
ransomware
attacks.
A
You
know
so
if
something
does
go
down,
you're
able
to
quickly
recover
from
that
in
the
quickest
way
possible,
but
it's
not
just
about.
If
things
go
wrong,
there's
also
migration
scenarios
based
on
cost
and
performance.
Let's
say
you
started
in
one
cloud
provider
and
maybe
that
cloud
providers
prices
have
have
increased
over
the
past
six
months.
Maybe
there's
certain
performance
criteria
related
to
cpu,
maybe
related
to
disk
io
operations,
and
maybe
another
cloud
provider
could
meet
those
requirements
better,
both
from
a
cost
and
performance
criteria.
A
So
you
might
need
to
move
that
application,
so
that
might
be
another
need
for
using
your
backups
as
a
way
to
move
to
move
your
application
from
one
cloud
to
another
and
you
might
have
service
level
agreements.
You
might
have
slas
that
specify
specify
things
like
uptime
or
specify
that
things
are
available,
potentially
across
different
availability
zones
or
available
certain
uptime
requirements.
So
all
of
these
all
of
these
things
are
important.
So
it's
not
just
about
backup
anymore.
A
There's
a
lot
of
other
challenges
out
there
that
having
a
good
backup
solution
can
help
you
achieve
these
other
challenges.
A
So,
let's
talk
about
the
use
cases
for
cloud
native
data
protection,
so
the
first
being
backup
and
recovery,
so
making
sure
that
you
have
an
automated
way
of
backing
up
everything,
that's
in
your
kubernetes
cluster
and
having
a
recovery
to
any
point
in
time
from
those
pre-scheduled,
point-in-time
snapshots
and
then
disaster
recovery.
So
saying
that
even
if
your
entire
cluster
goes
down,
you
have
a
way
to
recover.
All
of
that
data
and
persistent
data
that
lived
in
that
cluster.
A
You
have
a
way
to
recover
it
to
another
cluster
as
a
way
for
disaster
recovery,
but
it's
also
about
application,
mobility
and
migration.
So
their
ci
cd
tools
today
greatly
help
the
deployment
of
kubernetes
applications,
but
having
a
good
data
protection
solution
can
help.
You
move
these
applications
around
to
different
clusters.
You
know,
maybe
you
have
different
levels
of
test
and
development
environments,
and
so
you
could
using
a
tool
like
trillio,
can
help
you
move
those
applications
around
to
different
test,
dev
environments
and
then
ransomware
protection
and
recoverability.
A
So
let's
talk
about
ransomware,
so
ransomware.
As
I
said,
it's
really
been
on
the
rise
recently,
so
300
million
cases
in
the
last
year.
You
can
see
that
the
average
cost
has
increased
to
over
three
hundred
thousand
dollars
per
business.
All
of
the
all
of
these
attacks
have
increased
seventy
per
two
percent
since
the
pandemic.
A
So
it's
really
something
that
every
business
needs
to
be
planning
into
their
infrastructure,
on
how
they're
going
to
protect
themselves
from
ransomware
and
how
they
would
recover
from
a
ransomware
attack
if
it
was
if
it
was
going
to
happen
so
at
trilio.
It's
you
know.
We
believe
that
ransomware
protection
is
more
than
just
it's.
Not
a
single
software
feature
that
you
need
to
comply
to
it's
it's
kind
of
a
set
of
it's
a
framework
that
you
need
to
follow.
A
So
actually
the
nist
cyber
security
group
has
outlined
a
nist
cyber
security
framework
that
outlines
all
of
the
areas
that
application
teams
should
be
looking
at
to
make
sure
that
their
applications
are
secure
from
ransomware
and
so
trilio
helps
in
these
three
areas
to
help
companies
identify
and
protect
applications
to
detect
and
mitigate
and
to
recover
applications.
In
case
something
goes
wrong.
A
So
you
really
need
a
cloud
native
protection
that
does
many
things
you
need
it
to
be
application
centric.
You
need
to
you,
need
it
to
follow
all
of
your
kubernetes
applications
and
all
of
the
components
that
they're
spinning
up
in
those
clusters,
whether
those
are
the
metadata
pieces
or
whether
that's
the
stateful
persistent
volume
pieces
that
we
talked
about
in
the
first
myth
that
it
seems
to
be
increasing
across
the
industry
now
and
no
matter
how
those
applications
are
deployed.
A
So
whether
they're,
just
using
labels,
whether
they're
using
some
advanced
concepts
like
helm,
charts
or
operators
or
whether
you
want
to
back
up
you
know
single
name,
space
or
multi
multi-name
spaces.
You
need
a
tool,
that's
flexible
enough
to
track
all
of
these
things.
You
need
a
tool,
that's
kubernetes
agnostic.
You
know
a
tool
that
works
across
any
distribution
of
kubernetes.
That's
been
certified
certified
by
cmcf
such
that,
if
you,
maybe
that
would
enable
you
to
so.
A
A
You
should
have
a
management
console,
that's
self-service!
You
should
enable
your
development
teams,
your
users,
anyone
that's
you!
That's
consuming
your
kubernetes
applications.
If
they're
deploying
kubernetes
applications,
they
should
have
the
ability
to
have
backup
and
recovery
capabilities.
This.
This
shouldn't
be
the
old
legacy
solution,
where
only
the
storage
admin
has
the
the
ability
to
do
this.
You
know
it's
up
to
the
storage
admin
to
take
care
of
backups
and
recoveries.
A
So
your
solutions
ideally
should
be
native
to
kubernetes.
You
shouldn't
have
to
learn
any
new
tooling.
You
shouldn't
have
to
install
any
new
clis
to
do
this.
It
should
be
something
that's
just
built
into
the
kubernetes
apis
and
uses
the
kubernetes
tools,
such
as
cubectl
or
oc.
If
you're
using
the
openshift
version
of
kubernetes,
you
should
have
a
solution,
that's
enterprise
class,
so
you
should
have
a
solution
that
support
things
supports
things
like
restore
transforms.
A
So
if
you're
moving
from
one
kubernetes
type
of
kubernetes
cluster
to
a
different,
you
need
to
transform
some
of
the
base
components.
Things
like
storage
class
might
be
different
in
a
google
cloud
say
than
versus
an
amazon
cloud,
so
you
need
something
that
transforms
those
components
on
the
fly
when
you're
moving
that
application,
so
that
that
application
migration
is
seamless.
A
You
also
should
have
things
like
database
hooks.
So
if
you
have
databases
as
a
stateful
application
in
kubernetes
today,
there
are
some
procedures
that
you
need
to
do
to
properly
quiesce
those
databases,
so
that
when
you
take
a
snapshot
of
that
database
that
you're
getting
a
true
application,
consistent
backup
of
that
database,
so
that
when
you
restore
that
snapshot,
you're
restoring
that
database
to
a
proper
running
function
of
that
point
in
time,
snapshot
of
the
database.
A
So
you
need
some
hook
components
to
be
able
to
do
that,
and
ideally
it
should
be
something
that's
easy
to
try
and
install
something
that
you
could
try
in
your
own
environment,
free
for
a
period
of
time,
just
to
see
if
it
works
for
you,
so
trillio
accomplishes
all
of
those
things.
Truly.
A
vault
for
kubernetes
has
all
six
of
these
components
and
it
is
the
top
solution
for
cloud
native
data
protection.
A
A
We
have
some
exciting
demonstrations
that
I
plan
to
show
of
some
new
features
that
we're
releasing
at
cubecon,
so
so
so
come
out
and
see
us
at
kubecon,
and
also,
if
you'd
like
to,
if
you
like
what
you've
heard
today
about
our
product
and
you'd
like
to
try
it
out
for
yourself
go
to
trilio.io
and
there
you
can
see,
you
can
request
a
demo
or
you
can
download
a
license
to
try
this
in
your
own
environment.