►
From YouTube: Kubernetes SIG Storage - bi-weekly meeting 20200507
Description
Meeting of Kubernetes Storage Special-Interest-Group (SIG) Bi-Weekly Meeting - 07 May 2020
Meeting Notes/Agenda: -
https://docs.google.com/document/d/1-8KEG8AjAgKznS9NFm3qWqkGyCHmvU6HVl0sk5hwoAE/edit#
Find out more about the Storage SIG here: https://github.com/kubernetes/community/tree/master/sig-storage
Moderator: Xing Yang (VMware)
A
C
A
A
B
B
That
is,
we
are
going
to
discuss
in
the
call
after
this
meeting,
then
we
have
the
recovery
from
resize,
for
which
there's
a
cap,
open,
I,
don't
know
if
Zadar
Michelle
or
have
time
to
review
this,
but
it's
been
open
for
a
while,
now
and
and
the
third
one
is
the
improve
handling
of
lead.
Only
one
expansion
that
also
I
have
proposed
the
CSS
change
for
that.
Hopefully,
we'll
have
a
chance
to
discuss
that
today.
After
the
call,
then
the
the
PVC
could
be
deleted.
B
While
the
reason
is
spending
that's
the
fourth
issue,
and
for
that
there
are
multiple
ways
to
fix
this
and
we'll
talk
about
that.
I
was
talking
with
Michelle,
Indian,
offline
and
I.
Don't
think
any!
We
need
any
change
for
that
and
it
should
be
fixable.
So
that's
all
I
have
for
now
and
there's
a
PR
in
flight
that
michelle
has
been
reviewing
for
updating
new
CSS
speaking
communities,
and
I
have
to
work
on
that.
You
didn't
get
it
more
than
one
eighteen,
we'll
try
to
get
as
much
in
190.
B
So
there's
a
kept
open
for
it
and
I,
don't
know
if
you
can
mark
it
and
started,
because
this
is
kept
open
and
we
we
had
a
consensus
that
that
kept
is
the
way
forward
for
for
implementing
recovery
and
I'm
scheduled
a
call
tomorrow
as
well.
So
just
for
the
community.
Si
si
si
si
people
so
that
we
can
take
another
look,
but
yeah
I
think
that
cap
should
be
linked.
There.
A
A
A
A
A
D
D
D
D
A
B
C
A
D
A
A
G
So
to
just
to
get
a
brief
summary
to
me,
a
storage
glasses
me
in
something
like
what
qualitative
aspects
does.
Storage
has
like
performance,
characteristics
and
storage.
Pools
are
different,
they
describe
where
the
storage
is,
and
those
two
are
different.
But
it's
my
understanding
at
this
point,
and
that
also
means
that,
for
example,
in
the
state
full
said
you
can
reference
a
storage
cross,
and
you
know
that
the
volume
wherever
it
will
get
created
has
the
right
characteristics
for
your
app
and
Cuba
has
been
takes
care
of
of
picking
your
storage
pool.
D
G
A
A
G
A
G
C
G
D
A
G
C
A
Okay,
next
one
is
the
Warren
Group
API.
So
yesterday
we
had
a
design
review
at
the
data
protection
work
group
meeting
I
actually
forgot
to
send
send
that
out
to
DeSoto
minimus
so
yeah
we
had
a
good
discussion.
There
are
a
lot
of
comments.
This
is
a
complicated
issue.
So
so
sorry
I
see
that
you
added
an
item
on
the
agenda.
You
want
to
talk
about
that
later.
A
A
A
Explain
move
out,
AFS,
parishioner
and
and
also
move
out
and
his
client
provision
also
covering
this.
What
found
us
is
quranic,
all
no
okay,
so
and
not
date,
then
I
think
no
sure
I'd
know
that
he
was
working
on
this
one
before
and
the
next
one
is
deprecation
of
vanities
incubator,
external
storage.
Does
anyone
know
you
have
any
update
on
this?
One
I
think.
A
A
H
H
A
A
How
do
you
name
it
there?
Thank
you
next,
one
execution
hook
for
application
snapshot,
so
I
think
I
think
last
update.
We
okay,
we
met
with
Tim,
so
we
Shanti,
Anna
I,
went
to
one
of
the
signaled
meeting
and
showed
them
our
our
draft
proposal.
Of
course
they
have
lot
of
concerns,
so
they
have
a
lot
of
questions
like
how
are
you
going
to?
A
Are
we
going
to
make
sure
that
the
call
is
successful
and
how?
How
long
are
you
going
to
be
try
how
to
do
garbage
collection?
So
there
are
a
lot
of
questions
that
we
joint
you
and
so
their
questions,
and
there
is
given
someone
at
a
meeting
saying
that,
should
this
be
done
by
an
higher-level
application
operator,
which
is
you
know
funny,
because
that
was
actually
what
we
were
June
before
in
our
marriage,
the
tab
and
so
so
I
initially
didn't
really
bring
up
our
you
know
original
cap,
which
is
in
CRT.
A
A
B
A
A
B
D
A
B
B
D
D
A
B
A
F
D
A
A
A
Next
one
is
a
vSphere
Seattle
migration,
they
would
have
debian
and
a
call
so
so
TV
on
has
started
working
as
he
has
or
dump
EOC
think
he
yesterday
I
think
he
asked
some
questions
on
the
cell
migration
channel
because
there
are
a
few
things
that
inch
we
driver
supports,
but
we're
not
supporting
in
a
CSI
driver.
So
he
is
this
asking:
what
is
the
beta
criteria
for
those
two
things?
I
think
Michelle
and
so
bad.
So
this
is
a
working
progress.
A
J
J
C
J
D
J
A
J
C
A
C
A
A
D
D
A
A
F
So
Shing
held
a
kept
review
for
this
volume
groups
API.
Yesterday,
it's
very
interesting
new
proposal
and
it's
aiming
to
kind
of
tackle
a
number
of
use
cases
where
it
would
be
useful
to
group
volumes
somehow
and
the
use
cases
are
around
being
able
to
create.
You
know
group
consistent
snapshots
where
you
have
a
number
of
volumes
and
you
snapshot
them
all
together
at
once
and
they're
all
consistent
being
able
to
do
spreading
across
some
sort
of
set
of
volumes.
F
What
we
really
need
is
input
from
storage
vendors
on
this
one,
because
what
does
a
volume
group
look
like
from
storage
system
to
storage
system
is
going
to
vary?
I
posted
a
comment
in
there
kind
of
talking
about
some
of
the
possible
open
questions.
What
would
be
useful
is
if
vendors
on
this
call
can
jump
in
and
say
you
know:
I
have
a
storage
system
foo,
and
here
is
how
we
do
volume
groups.
F
So,
for
example,
do
you
expect
a
do
you
allow
for
an
empty
volume
group
to
be
created
and
then
have
existing
volumes
added
one
by
one
to
it,
or
do
you
expect
a
volume
group
to
be
created
at
provision
time
when
all
the
volumes
are
created
and
all
variations
of
that?
Similarly,
what
type
of
restore
snapshot
restore
for
volume
groups
do
you
allow?
Is
it
one
by
one
person
app
shot
or
is
it
as
an
entire
group?