►
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Kubernetes 数据保护工作组的介绍和深入研究 | Kubernetes Data Protection WG Intro & Deep Dive - Xiangqian Yu, Google
数据保护工作组致力于促进 Kubernetes 的数据保护支持。该工作组一直致力于确定缺失的功能，并在多个 SIG 之间进行协调，设计能在 Kubernetes 中实现数据保护的功能。在此次讨论中，该工作组的联席主席将讨论 Kubernetes 中数据保护的当前情况及其未来的发展方向。他们还将讨论各利益相关方（包括备份和存储供应商、应用开发者和最终用户等）如何能加入这个工作组并为之做出贡献。有关本工作组的详细信息，请参阅：https://github.com/Kubernetes/community/tree/master/wg-data-protection.
Data Protection WG is dedicated to promoting data protection support in Kubernetes. The Working Group is working on identifying missing functionalities and collaborating across multiple SIGs to design features to enable data protection in Kubernetes. In this session, the co-chairs of this WG will discuss what is the current state of data protection in Kubernetes and where it is heading in the future. They will also talk about how interested parties (including backup and storage vendors, application developers, and end users, etc.) can join this WG and contribute to this effort. Details of the WG can be found here: https://github.com/kubernetes/community/tree/master/wg-data-protection.
A
B
Hi
everyone
thanks
for
coming,
my
name
is
sean
chen.
I
work
in
for
google,
I'm
right
now,
co-leading
the
data
protection
working
group
with
shin
next
slides.
Please,
today,
shin
and
I
will
go
through
these
topics
and
listening
on
the
agenda.
We
will.
I
will
go
through
what
what
motivated
us
to
establish
this
working
group
and
who
are
the
parties
that
are
getting
involved
in
this
data
protection
working
group
and
explain
a
little
bit.
B
What
do
we
think
data
protection
is
in
the
kubernetes
context
and
go
through
what
are
the
existing
building
blocks
or
modules
that
allows
application
owners
or
cluster
owners
to
protect
the
stateful
workloads
and
what
exactly
are
the
gaps
that
this
working
group
is
looking
to
build
or
propose
to
help
providing
data
protection
in
the
kubernetes
context,
and
the
very
last
shin
will
go
through
how
to
get
involved
in
this
data
working
group
that
this
working
group?
Next,
please,
as
you
many
of
you,
may
be
or
very
well
aware
of
the
day.
B
It's
been
there
for
a
couple
of
years
and
is
very
stable
with
that.
The
direct
impact
is
more
and
more
stateful
workloads
like
databases,
message
queues,
etc,
etc,
are
looking
forward
to
utilize
those
constructs
as
well
as
kubernetes,
very
nice
feature
of
scanning,
scalability,
etc,
etc.
To
move
into
the
kubernetes
environment.
B
B
B
B
The
main
purpose
of
this
group
is
to
propose
and
design
modules
to
ensure
an
application
like
database,
including
its
config
and
data,
to
be
restored
to
a
previously
preserved
state,
meaning
a
backup
if
the
in
case
there's
any
disaster
happen
to
that
application
that
could
be
lasting
of
a
cluster
or
clumsy
hands
just
delete.
The
whole
namespace,
where
the
application
is
wrong,
etc
in
kubernetes
context,
mainly
basically
involves
two
pieces.
The
one
piece
is
the
api
resources
that
describes
the
application
and
the
other
piece
which
is
more
critical.
B
B
B
That
means
it
needs
is
needs
to
be
able
to
quiet,
basically
freeze
itself
from
writing
before
the
backup
is
taken
and
unfreeze
itself
after
the
backup
is
taken.
That's
the
quietest
and
quiet
hooks
of
stock
that
in
the
slides
talking
about,
and
then
lastly,
what
is
the
orchestration
look
like
at
the
name,
space
level
and
a
cluster
level
next
slides,
please
so
talking
about
all
the
definitions,
let
now,
let's
drill
down
a
little
bit,
what
are
the
common
use
cases
all
right?
B
There
are
three
listed
over
there,
but
definitely
more,
but
those
three
are
very
typical
and
it
covers
a
different
layer.
So
more
typical
thing
is
that
you,
as
a
mysql
database
owner
right,
you
want
to
protect
your
mysql
database
to
cover
cover
like
common
failure
scenarios,
for
example
a
bad
rollout
right.
You
have
a
bug
in
your
your
system
and
they
corrupted
your
data.
You
want
to
go
back
into
the
previous
state
and
the
other
scenario
is
more
about
migrating
or
geo
expansion,
meaning
that
okay,
you
have
a
database
running
in
europe.
B
Now
you
want
to
expand
your
business
into
asia.
In
this
case,
you
want
to
migrate
whatever
the
data
from
one
area
to
another
area.
Those
are
the
common
use
cases
as
an
sql
database
owner
or
application
owner.
If
move
up
a
little
bit
to
the
class
owners
row,
not
typically
a
name
space
owner.
Typically
that
is
owned
by
a
class
administrator.
B
So
with
this.
Let's
I
want
to
walk
you
through
what
exactly
a
backup
workflow
look
like
so
within
the
kubernetes
context,
so
the
on
that
workflow
starts
from
the
left
and
it
ends
up
in
the
right.
So
basically,
a
user
kicks
off
a
backup
process,
and
this
process,
as
mentioned
previously,
includes
two
pieces.
B
One
is
the
kubernetes
resource
that
that
backup
can
contain,
may
be
scoped
to
a
certain
application.
For
example,
this
resource
will
is
most
likely
in
many
cases,
just
a
simple
api
resource,
yaml
file
dump
and
getting
exposed
into
some
remote
repository.
That
has
the
independent
life
cycle
to
your
cluster
and
the
other
major
piece.
Is
this
so-called
data
backup
right?
There
are
many
ways
you
can
do:
data
backups
right
one.
One
of
this
is
using
that
application
native
data
dump
typical
two
is
like
a
mysql
dump
or
kafka
dump,
etc.
B
This
kind
of
thing
you
basically
dump
whatever
your
data
into
a
backup
location
and
then
there's
some
remote
there's
some
local
process
that
copies
this
dump
data
to
a
remote
location.
Again,
this
remote
location
has
to
be,
like
kind
of
you
know,
have
independent
lifecycle
to
your
cluster
so
that
you
can
restore
from
it.
B
Another
way
is
the
so-called
controller
coordinated.
So
it
is
a
module
that
the
community
is
looking
forward
to
providing
the
future
as
well.
Basically,
it's
a
good
agnostic
to
what
kind
of
application
it
is.
What
it
does
is
that
it
it
gives
it
first
go
ahead
and
check.
Okay,
should
I
acquire
this
application
so
that
no
more
rights
is
accepted
and
then
it
conducts
williams
snapshot
using
the
worm,
snapshot,
api,
etc
and
doing
the
one
backup,
and
then
I'm
quite
there
unquers
the
application.
B
After
all,
this
is
done,
then,
the
william
delegate
transported
again
to
an
external
location
so
that
it
can,
you
know,
have
independent
lifecycle.
This
is
basically
describes
the
whole,
like
really
1000
foot
view
of
the
backup
workflow
moving
to
restoration.
Next
slice,
please
it's
kind
of
the
reverse
right.
So,
basically,
the
user
starts
a
restoration
and
then
the
first
thing
is
to
import
whatever
the
backup
from
a
remotely.
B
So
what
are
the
modules
needed
to
accomplish
all
these
workflows
right?
There
are
a
couple
of
existing
building
blocks
in
disk
in
the
kubernetes
community
to
already
support
that
in
the
application
layer
you
we
have
stateful
sets
and
deployment
demons
which
are
really
well
established,
workload
apis
and
those
workload
apis
can
easily
tell
you
what
are
the
resources
contained
for
a
content
for
this
application
by
doing
a
simple
label?
Query
there's
also
an
application
crb
which
tells
you
what
are
the
components
compose
this
a
particular
application
in
the
storage
layer?
B
B
Next
high
space,
but
let's,
if
you
look
at
this
picture,
though
the
workload
api
is
like
set
for
set
and
the
sick,
apps
application,
crds,
which
solves
kind
of
you
know,
solves
part
of
the
problem
of
figuring
out.
What
are
the
kubernetes
resources
that
backup
process
should
be
backing
up
and
next
slide
space
and
the
williams
snapshot
feature
is
really
fit
into
the
data
piece.
Where
there's
no,
let's
say:
there's
no
native
application
native
data
dump.
B
The
controller
can
go
ahead
and
create
the
worm
snapshots
from
a
pvc
and
that
inquires
the
application
with
that
next
slice.
Please
there's
a
lot
more
with
that.
In
the
restoration
process,
the
volume
snapshot
can
be
used,
natively
to
rehydrate
the
pvc
from
from
it
go
ahead
next
slides!
Please,
with
this
I
there's
still
a
whole
bunch
of
missing
building
blocks
like
a
wing
backup
or
change
block
tracking,
which
allows
very
efficient
volume,
backup
and
the
data
populator,
which
reads
the
volume,
backup
and
repopulate
the
pvc.
B
We
talked
about
a
remote
place
to
store
your
backup
so
that
it
has
such
that
it
has
an
independent
life
cycle
than
the
cluster
itself
and
requires
an
acquires
hooks
that
allows
application
level,
sorry,
application,
consistent
snapshots,
etc.
All
these
are
yet
to
be
built
fitting
into
the
workflows
next
slides,
please.
B
This
gives
you
an
overview
of
what
are
missing
components
in
this
community
right.
The
green
box
are
existing
ones.
The
yellow
box
are
ongoing
efforts
and
the
orange
boxes
are
to
be
to
be
to
be
designed.
A
shin
will
give
more
details
into
this
one.
Next
slice
talks
about
the
restoration,
similar
things
yellow
boxes.
The
cause
is
basically
an
effort
to
provide
object,
storage
interface
and
the
green
bar.
A
So
the
first
missing
building
block,
we
identify
it
as
volume
backup.
We
need
this
because
we
need
to
extract
data
to
a
secondary
storage.
We've
already
got
a
volume
snapshot
api,
but
there's
no
explicit
definition
made
in
a
design
to
have
snapshots
stored
on
a
different
backup
device
separate
from
the
primary
storage
for
some
cloud
providers.
Snapshot
is
actually
a
backup
that
is
uploaded
to
an
object
store
in
the
cloud.
A
A
A
A
A
A
A
A
Currently,
there
is
a
proposal
for
object,
store,
backup
repository,
that's
the
proposal
for
object,
bucket
provisioning
or
cosy
this
prop.
This
proposes
object,
storage,
kubernetes
apis
to
support
orchestration
of
object,
store
operations
for
kubernetes
workloads,
therefore
bring
in
object
storage
as
the
first
class
citizen
in
kubernetes.
A
A
A
The
volume
populated
feature
allows
us
to
provision
a
pvc
from
an
external
data
source
such
as
backup
repository.
In
addition,
it
allows
us
to
dynamically
provision
a
pvc
having
data
populated
from
that
backup,
repository
and
honor.
The
wait
for
first
consumer
volume,
binding
mode
during
restore
to
ensure
volume,
is
placed
at
the
right
node.
The
pod
is
scheduled.
A
A
A
A
Move
logic
in
the
pod
notification
controller
into
keyboard,
qblade,
watches,
part
notification,
objects
runs
the
command
and
updates
statuses
of
part
notification
objects.
Accordingly,
in
phase
3,
a
probe
may
be
added,
if
needed,
as
an
inline
port
definition
to
verify
the
signal
is
delivered
or
whether
the
command
is
run
and
results
in
the
desired
outcome.
A
The
next
one
is
consistent
group
snapshot,
so
we
talked
about
the
content,
notify
proposal
which
tries
to
ensure
application
consistency.
What,
if
you
can't
quiet
the
application
or
if
the
application
requires
is
too
expensive,
so
you
want
to
do
it
less
frequently,
but
still
want
to
be
able
to
take
a
crash,
consistent
snapshot
more
frequently.