►
From YouTube: Data Protection WG's Bi Weekly Meeting for 20200423
Description
Data Protection WG's Bi Weekly Meeting for 20200423
A
A
Today
is
April
22nd
2020,
and
this
is
the
kubernetes
telephone
protection
working
group
meeting.
This
meeting
will
be
recorded
and
wearable
in
YouTube
once
uploaded.
The
ink
will
because
in
the
dark
you
anyone
who
is
interested
and
a
little
bit
there
today,
we
mainly
have
one
major
topic
to
go
through.
She
is
and
two
more
things,
it's
more
about
one
more
thing
about
more
about
info
met,
Mary,
which
is
the
people
in
model,
and
she
is
kind
of
what
we
go
through.
The
execution
could
update.
A
We
had
a
couple:
we
had
a
one
meeting
with
Jim
Hawkins
and
some
other
contributors
in
the
company
risk
and
some
feedbacks
and
she
was
trying
to
work
in
alternative
I
will
let
him
get
started,
and
then
we
will
discuss
what
is
going
on
with
snapshot.
Controller
deployment,
I
think
been
nicer
pain,
where
the
pains
here
ask
the
same
question
as
well:
how
to
vendors
actually
found
out
of
three
important
controllers
with
kubernetes
and
how
to
take
it
informed
how
to
the
support
different
versions?
Isn't
really
majorly
foreign
for
your
information?
A
A
A
B
This
your
gender
doc,
so
we
have
reviewed
the
stock
before
I
nation
last
time
that
we
had
some
discussion
about
this
and
then
we
got
some
feedback
so
now
this
is
the
new
proposal,
so
mainly
because
other
than
us
who
want
to
be
able
to
acquire
us
and
our
class
to
do
a
application
snapshot,
they
were
also
other
use
cases.
So.
B
B
Sometimes
you
want
to
be
able
to
send
a
signal
to
the
pod
or
reloading
configuration
or
to
start
an
upgrade
profile
prepare
for
some
other
things.
Like
data
migration,
there
could
be
more
things,
I
think.
Actually,
this
Reeves
cases
are
also
listed
in
our
previous
execution
hook
cap.
That
was
that
one,
the
Mercia
one
also
mentioned
those,
but
in
this
new
draft
proposal
we
are
trying
to
make
this
even
more
generic,
because
the
the
other
proposal
and
our
new
xpl
proposal,
or
very
very
much
focusing
on
the
snapshot
use
case.
B
So
now
this
one
is
written
in
a
way
that
is
more
generic
it
because
there
are
other
use
cases
so
because
there
are
other
use
cases,
we
want
to
find
a
way
that
is
more
generic,
that
is
more
generally
usable
and
more
secure,
so
help
you
bleed
do
most
of
the
work
that
requires
to
you
that
is
required
to
run
this
command.
Is
it's
a
better
way,
so
this
part
actually
is
same
as
what
we
have
proposed
in
this
other
dock,
the
new
extra
Pozzo,
but
that
API
part
is
different.
B
B
B
So
this
is
a
inline
pas
definition,
I
think
previously
we
were
proposing
to
add
something
inside
the
lifecycle
itself.
So
this
is
a
part
of
the
container
struct,
which
is
already
there
in
the
core,
a
P
I.
So
now,
instead
of
adding
something
inside
this
lifecycle
saying
we
are
adding
a
new
container
notifier
this
this
will
be
in
a
list
list
of
container
notifiers
will
allow
us
to
have
a
multiple
comments:
Ching
yeah.