►
From YouTube: Kubernetes SIG Storage - bi-weekly meeting 20201217
Description
Meeting of Kubernetes Storage Special-Interest-Group (SIG) - 17 December 2020
Meeting Notes/Agenda: -
Find out more about the Storage SIG here: https://github.com/kubernetes/community/tree/master/sig-storage
Moderator: Xing Yang (VMware)
A
A
So
the
first
one
is
delegate
fs
group
two
csr
driver
instead
of
cubelet.
Is
this
a
command
or
christian.
D
E
B
A
This
design,
what
what
should
we
put
here,
corrugated
status,.
B
Currently,
I
think
we
were
not
planning
to
put
behind
this
feature.
Gate.
A
Okay
design
or
what
what
is
this
category
okay,
is
that,
then,
should
this
be
like
a
bug
fix,
do
you
think
or
does
not
need
a
future
gate,
or
is
it
design
or
is
it.
C
I
guess
it's
it's
a
little
weird,
because
I
think
we
were
going
to
add
csi
spec
changes
right
and
those
were
going
to
be
alpha.
Oh
so,
oh.
C
C
Really
we
should
enhance
the
existing
enhancement
issue,
yep,
okay,
so
we
don't
need
a
new
one.
So
just
I
guess
just
say
now
and
we
can
link
to
the
existing
one.
B
Okay,
if
we,
if
we
do
decide
to
introduce
this
as
alpha
feature,
then
we'll
need
a
new
new
feature
grade
actually
because
all
the
existing
feature
gates
are
beta.
So
there
is
always
that,
but.
E
B
A
B
All
right
so
yeah,
it's
kind
of
one.
I
think
that's
the
reason
I
think
we
should
put
it
on
top
because
it
is
blocking
like
some
drivers
from
being
usable
with
without
true
tax
permissions.
D
C
A
All
right,
okay,
so
do
we
want
to
put
a
reviewer
here.
C
A
D
A
So
with
two
or
three
I
just
I
just
looks
like
yeah.
It
looks
like
the
other.
We
have
a
few
items
down
below
as
since
those
are
all
like
three,
but
we
can
change
this
one
later,
okay,
so
this
is
party
up.
I
think
it's
a
cap
looks
like
not
merged
yet
yeah.
That's
remember
the
enhancement
issue.
I
think.
A
Actually,
I
don't
know
if
you've
noticed
that
he
has
an
issue,
but
I
think
we
need
this.
I
found
a
cap
so
yeah,
so
this
one
yeah,
so
this
one.
I
know
this
one
yeah
this
one
is
kind
of
important.
There
is
a
cap
there.
A
I
I'm
not
sure
if,
yes
he's
planning
to
bring
this
alpha,
or
maybe
we
can
put
it
as
ava
for
now
and
then
I'll
check
with
him
he's
probably
not
on
this
call,
I
think
just
I
think
tim
has
been
reviewing
it.
I
have
some
questions
on
that,
so
maybe
we'll
just
also
put
it
as
two
for
now,
let's
see
because
there's
this
cap
and
then
there's
other
some
related
issues
right,
we
can
fix,
which
is,
may
not
be
part
of
this,
but
maybe
related
this
one.
Okay,.
A
F
F
A
Yep
sounds
good.
Okay,
should
I
put
your
name
there
as
well
sad,
I
think,
probably.
C
C
Been
a
meeting
yet
I
I
would
definitely
suggest
that
we
create
one,
because
this
is
a
very.
This-
has
a
lot
of
implications
on
csi
yeah.
A
I'll
open
him
up
because
everything
opened
him,
he
said
he's
going
to
set
up
meetings.
I've
been
waiting
for
him.
Actually
I
just
pinned
him
two
days
ago.
He
said,
oh,
maybe
after
the
new
year
and
he's
also
supposed
to
update
the
cap
as
well.
I
haven't
seen
that,
as
he
said,
he's
got
business
so
if
he
still
did
help
him
again
after
new
year,
if
he
still
didn't
set
up
and
I'm
going
to
go
ahead
and
start
a
meeting
yeah,
I
think
it's.
A
This
is
important,
but
the
current
cap-
I
do
have
a
lot
of
questions.
I'm
not
really
sure
how
that
would
work
yet
so
yeah.
So,
let's,
let's
follow
up
with
that.
So
probably
I
will
move
this
one
lower
together
with
the
other
there's
a
few
other
signals
and
seek
apps
features,
probably
should
move
them
together
and
okay.
So
the
next
one.
So
now
it's
this
online
offline
resizing,
so
guess
we
should
go
to
ricochet.
B
So
the
main
thing
was
that
the
the
we
have
in
this
release
there's
a
two
things
that
I
want
to
address.
Primarily
one
was
like
the
csi
node
expansion,
there's
a
pr
out
to
add
secrets
to
that.
If
we
want.
H
B
B
G
I
I
A
A
H
A
G
B
D
C
Need
I
I
think
it
this
mostly
comes
down
to
the
api
machinery
like
for
skus
like
when
you
have
aha
api
servers,
it's
possible
to
have
version
skew
and
there
might
be
some
api
machinery
limitations
on
like
the
when
a
field
is
introduced,
and
so
I
think
we
just
need
to
check
with
api
machinery
folks,
if
it's
required
or
not.
C
A
All
right
so
and
then,
if
it's
added
to
csi
and
now
that's
also
known
as
the
alpha
and
right.
E
B
Second,
item
that
we
had
here
was
like
the
moving
the
or
not
moving,
but
copying
the
allow
volume
expansion
field
to
not
this
one.
But
the
separate
item.
Oh.
B
Was
discovered
during
one
of
the
resizing
call
like
we
want
to
copy
the
alarm
volume,
expansion
field
from
storage.
A
B
A
B
And
doing
previous
thing.
A
Okay,
right,
okay,
so,
okay,
so
there
are
a
few
things.
So
what
do
we
do
with
we
this
this
one?
Can
this
one
go
j,
or
do
we
wait
for
this
yeah?
I.
A
A
B
B
We
got
some
guidance
from
tim
and
jordan,
but
we
haven't
got
any
traction
in
terms
of
like
the
problem
is
that
the
recovery
solution
is
is
like
the
parting
line,
resizing
that
we
are
asked
to
follow.
It's
it,
at
least
in
120
timeline.
It
was
not
decided
yet.
So
it's
like
we
don't
know,
but
I
haven't
seen
a
conclusion
that
how
do
we
reuse
that
design
for
pvc
resizing
and
it's
in
120
time
frame,
121
time
frame?
B
Sorry,
I
would
like
to
work
on
a
design,
but
and
if
we
can
get
a
consensus
on
this,
that'll
be
great,
but
okay,
it's
a.
I
think
it's
a.
I
need
to
schedule.
Some
follow-up
calls
once
the
solid
is
after
the
halt
in
the
new
year
for
for
this
item
actually
and
where
we
can,
what
we
can
do
and
write
a
design.
So,
okay,
I
want
to
leave
this
as
a
design
for
now.
H
B
H
H
A
All
right,
okay,
so
next
one
is
do
we
do
we
have
a
do?
We
have
more
for
this
two
things
we're
done.
A
B
We
have
a
rough
agreement
on
how
it
should
be
implemented,
but
I
don't
know
if
jan
will
have
time
to
implement
this.
That's
the
the
tricky
thing
so,
okay.
A
B
A
Thanks,
okay,
so
next
one
csi
entry
read
only
handling,
so
this
one
is
a
bug
fix
that
humble
has
a
pr
that
I
think
we
several
offers
are
reviewed
and
but
we
just
haven't
heard
from
because
I
think
waiting
for
him
to
address
the
comments
right.
I
don't
know
if
assad
have
you
heard
anything
from
humble.
F
Yeah,
let's
keep
it
on
for
this
quarter
and
we
can
get
updates
periodically
and
hopefully
wrap
it
up.
This
quarter.
A
C
So
andy's
fixes
in
there
is
one
more
fix
related
to
this,
that
we
merged,
but
then
had
to
revert
because
it
revealed
a
bug
in
a
different
area,
and
so
I
think
this
release.
We
should
figure
out
how
to
resolve
that
bug
so
that
we
can
continue
on
this,
but
like
basically
that
last
pr
is
blocked
on
resolving
the
other
issue.
Okay,
so.
B
C
Put
you
can
put
it's
no
longer
andy
who's
working
on
this.
It's
the
hit
all
right,
I'm
not
sure
how
to
ch.
Sorry,
c-h-a-I-h-I-t,
I
think,
is
that.
B
D
D
A
Okay
thanks
next
one
storage
capacity
tracking
for
part
scheduling
patrick,
do
we
have
any
plans
for
this
feature
in
1.21.
A
A
Okay,
so
next
one,
I
think
next
one
is
also
patrick.
The
next
two
are
also
patrick.
J
Just
just
number
eleven,
that's
the
generic.
J
A
F
Matt,
were
you
interested
in
picking
up
number
12?
I
forget
sorry,
you
put
you
on
the
spot.
F
K
We,
yes,
we
are
planning
on
picking
that
up,
although
not
probably
until
the
middle
of
next
year.
So
if
somebody
okay
feels
like
they
need
to
jump
on
it
sooner
then
feel
free,
but
we
can
put
my
name
in
there.
Okay,.
F
So,
in
the
meantime,
if
anyone
else
is
interested
in
helping
drive
kind
of
core
api
functionality,
this
is
a
good
opportunity
to
jump
in
and
help.
G
A
C
The
proposal
they
have
basically
means
is
saying,
is
basically
proposing
to
basically
deprecate
and
remove
beta
apis
that
don't
make
progress.
C
C
C
I
think
I
mean
the
concern.
The
concern
is
basically,
you
know
some
beta
features.
We
don't
want
people
because
you
know
bringing
a
feature
to
ga
is
like
the
hardest
part
of
things
right.
It's
really
easy
to
bring
a
feature
to
alpha
or
beta,
but
bringing
it
to
ga
is
pretty
challenging
and
what
they
want
to
avoid
is
like
you
know,
people
bringing
features
to
beta
and
it's
on
by
default
now
and
that's
great
and
then
they
leave
and
then
yeah.
C
C
C
And
you
know
that
way:
we
don't
have
consumers
depending
on
it
in
production,
that
kind
of
thing,
because
that's
also
a
risk
they
want
to
avoid.
So
they
want
to
create
a
new
api
group
for
it,
so
that
users,
don't
you
know,
get
comfortable
with
the
feature
being
perpetually
in
beta
and
then,
if
the
sig
is
not
making
progress
on
it,
then
we
just
remove
the
feature
after
some
time
right.
A
Okay,
okay,
okay,
so
we'll
leave
this
one
need
a
volunteer
for
this.
If
you
want
someone
to
work
on
this
early,
okay,
so
next
one
spreading
over
failure
domain,
that's
mine!
Okay!
I
think
it's
still
we'll
still
be
staying
design
and
then
that,
because
that
goes
with
the
next
one,
which
is
modern
group,
I
think
probably
was
still
staying
designed
trying
to.
If
we
can
nail
it
down,
then
maybe
the
next
release
we
can
try
to
go
after
because
we
haven't
done.
A
We
still
have
not
finished
the
whole,
the
whole
cap
yet
and
then
also
we
have
the
second
part,
which
is
the
spreading
of
philadelphia.
So
so
I'll
just
leave
that
in
design
for
now
and
the
next
one
csi
auto
tree
mobile
scuzzy
driver
okay.
So
this
oh
michelle
is
this:
what
is
the
status
of
this
one?
We
still
wait
for
when,
when.
C
Yeah,
I
need
to
follow
up
with
some
of
the
folks
who
had
volunteered
last
year
to
help
maintain
the
iscsi
driver.
Okay,
I
need
to
reach
out
to
them
again
and
see
if
they're
still
willing
to
to
help
do
some
of
the
set
up
the
ci
and
stuff
like
that.
Okay,.
L
D
A
L
D
C
The
notes
in
the
notes-
you
can
say
christian
may
be
willing
to
help
with
this.
D
C
Are
they
are
finally
done
all
right,
so
I'll
just
remove
the
signs.
We
don't
need
this
one.
A
Yeah
screw
things
up
now:
okay,
next
one
move
out,
and
it
says
those
of
karen.
M
C
M
M
It's
similar
yeah
I'll,
basically
follow
up
on
the
once
the
nfs
provision
is
there.
I
can
repeat
that.
A
Next,
one
volume
snapshot
name
space
transfer.
Do
we
have
mike
here.
A
Okay,
so
we
still,
we
don't
know.
I
know
he
updated
the
cap
some
time
ago,
but
we
haven't
heard
anything.
So
I'm
not
sure
so
we'll
just
leave
it
here.
Then.
F
Yeah,
let's
leave
it
unassigned.
I
think
ben
had
a
good
point
of
do.
We
actually
need
this
now,
okay,
and
if
somebody.
F
It
let's
leave
it
and
just
leave
it.
Unassigned.
A
A
Thanks:
okay,
next
one
is
that
what
in
house
so
yeah,
so
we
can
try
to
bring
this
to
beta?
Yes,
yeah,
you
know
just
change
this,
so
I
think
the
there
is
some
other
other
update
we
want
to
do,
but
then
that
probably
will
have
to
follow
some
different
future
gate
anyway.
So
this
existing
feature,
we
can
probably
try
to
go
beta,
we'll
see
right
now,
still
there's
still
some
ci
issues
just
when
we're
trying
to
add
that
support
into
the
the
hostpass
driver.
A
So
next
one
is
okay:
that's
ben's
genetic
data,
populator.
A
G
G
The
the
things
that
need
to
happen
are
we
have
to
have
the
the
external
controller
in
crd
basically
available
and
published
and
released
in
a
state
where
distros
can
pick
it
up
before
we
flip
the
feature
gate
for
that,
any
any
volume
data
source
to
beta
so
that
it
turns
on
by
default
and
that'll,
be
my
priority
in
addition
to
actually
working
on
the
populator,
guts
and
sample
itself.
G
But
the
for
the
feature
gate
is
just
that.
It's
just
that
controller
to
give
feedback.
When
you
have
a
volume
that
won't
get
populated.
H
Yeah
this
is
trini,
the
progress
is
pretty
good
in
the
last
few
weeks,
despite
of
the
holidays,
we
are
moving
the
code
to
the
official
repos
there
are.
There
is
a
good
engagement
from
the
community,
there
are
reviewers
and
a
few
bug
fixes
from
others,
and
we
also
see
good
attendance
to
the
meetings.
H
Apart
from
that,
ci
process
is
almost
in
place,
except
one
pr
is
still
waiting
for
final
approval
there
in
prague,
and
there
are
a
few
spec
updates
based
on
the
discussions
in
the
last
few
weeks,
other
than
that
we're
doing
good.
We
also
created
a
project
management
board,
so
we
are
tracking
our
progress
for
demo,
one
out
there
and
things
are
looking
good.
K
Yeah,
so
we
have
a
slight
update
here.
If
you
look
in
the
comment
for
the
zeb
lead,
there's
the
github
handle
of
this
is
grey
yeah,
who
is
going
to
take
over
the.
K
Yeah,
so
I
I
don't
have
any
like
non-procedural
update,
but
hopefully
we
we
are
hoping
to
start
on
that
next
month.
So
maybe
we'll
have
more
interesting
updates
soon.
A
K
A
So
so
this
one
are
we
targeting
ga?
You
know
this
is
already
beta
right.
A
K
So
for
ga
yeah,
oh
yeah,
I'm
sorry,
the
header
in
the
column
is.
A
Oh,
you
said:
oh
okay,
we
need
to
change
this.
Am
I
I.
C
C
C
See
a
few
of
those
sga:
is
it
okay?
I
I
guess
we
can
consider
it.
I
was
actually
thinking
because
we
we're
not
even
on
by
default,
I'm
wondering
if
we
should
have
a
release
where
we
go
on
by
default.
Before
we
go
ga
for
you
to
go.
A
C
To
be
on
by
default,
nothing
really
so
I
guess
the
main
thing
is
like
we
want
to
make
sure
that
I
think
I
don't.
I
don't
think
we
should
move
the
core
migration
to
ga
without
actually
a
plug-in
going.
Ga
to
you
know
validate
that
the
core
migration
is
actually
ga
ready,
but
I
think
actually
you
know
turning
core
migration
on
by
default,
but
if
none
of
the
plug-ins
actually
turn
on
it's
fine,
okay,
so.
A
C
Guess
it
just
depends
on
if
any
plug-in
thinks
they're
ready
to
go
ga
and
I'm
wondering
if
none
of
the
plug-ins
so
far
are
on
by
default.
I'm
wondering
if
there
should
be
a
release
where
the,
if
a
plug-in
wants
to
go,
ga
I'm
wondering
if
they
should
wait
a
release
to
go
on
by
default
and
then
one
release
later
go.
Ga
okay,.
C
So
I
know
openstack
has
been
pushing
hard
to
go
ga,
but
I
also
know
they
don't
really
have
like
a
lead
on
this.
So
what
is.
B
See
yes,
so
this
is
an
item
that
we
have
been
internally
tracking
actually
and
we
want
to.
We
have
an
interest
to
move
this
to
ga,
but
it's
like
we,
I
I
said
if
nobody
else
comes
up,
will
will
think.
B
It
might
still
get
replaced,
so
there
are
other
teams
within
this
thing
that
who
are
like
working
on
standards
so
I'll
ask
them,
and
if
okay.
A
C
I
think
is
matt
here,
matt
wong,
I
was
speaking.
I
was
talking
to
matt
wong
earlier
and
he
intends
to
work
on
it.
I
I
think
they're
gonna
do.
I
think
they're
gonna
follow
the
same
procedure
where
they
on
by
default
first
and
then
go
ga.
C
I
think
yeah
and
then
gm
and
122.,
because
I
imagine
you
know
once
we
on
by
default.
We're
gonna
like
we're.
Gonna
uncover
all
of
the
test.
Ci
issues.
Okay,
so
I
imagine
you
know
just
the
process
of
turning
on
by
default
is
gonna
require
a
fair
amount
of
work
to
fix
all
our
ci.
B
A
Keyboard;
okay,
for.
A
Okay,
oh,
I
think
we
skipped
a
few
all
right
yeah.
I
think
this
video
is
you're
trying
to
know
the
the
the
thing
that
yeah,
the
back
four
is
approved.
I
think
we're
trying
to
get
that
into
your
release
so
yeah.
This
is
your
beta
and
as
you
disk,
so
we
should
okay,
we
move
this
back
then
data,
and
then
we
do
the
same
thing.
Basically,
we
just
say
that.
A
D
D
A
C
Okay,
so
so
out
of
all
of
these
plugins
azure
file
is
still
alpha
and
they.
C
To
they
tried
to
go
to
beta
last
release,
but
they
hit
some
bugs
okay,
so
I
think
I
think
andy
will
be
working
to
target
beta
this
release.
Okay,
so
this
is
correct.
All
right.
C
F
C
A
A
A
A
All
right,
all
right,
so
now
we
get
to
this
joined
projects,
immutable
secrets
and
config
maps.
Is
it
already
beta
michelle?
You
know
yes
and
they
plan
to
move
the
ga?
Oh
okay,
cool,
gee,
okay!
A
Next
one
is
okay,
so
we
have
two
projects
with
sick
apps.
Those
are
all
have
to
do
with
staple
set.
Is
I
think
kk
is
kkk.
Here
looks
like
he's
not.
C
A
A
K
A
Okay,
yeah,
I
actually
should
remove
my
name.
I
didn't
really
remove
this
one,
so
this
is
yeah
that
is
revealing.
Okay,
yeah!
That's
right!
Thank
you!
Thank
you,
jen,
okay,
so
the
next
one,
this
one
is
still
probably
designed,
then,
because
I
think
he
said
he's
going
to
get
the
first
one
down.
First,
so
probably
assume
this
one
is
still
designed
right.
B
Yeah,
I
think
it's
still
designed
because
we
haven't
he
yeah.
He
got
busy
in
last
quarter,
so
we
have
to
kind
of.
D
A
A
Okay,
so
next
one
okay,
so
this
is
a
content,
notifier,
so
yeah.
We,
I
think,
we'll
try.
I
think,
we'll
try
to
go
offer
again.
Let's
see
so
I
think,
there's
still
a
few
issues
that
we
need
to
get
resolved
on
the
api
part.
So
there
are,
I
think,
team
has
a
few
questions
that
we
still
need
to
address.
So
I
think
we
need
to
set
our
meeting
with
him
to
figure
out.
A
It
mainly
has
to
do
with
the
status
update.
It's
some
performance
concerns
on
those
okay.
Next
one
is:
is
this
still
a
okay
yeah.
H
Okay,
this
is
trinity
yeah.
Basically,
there
is
one
item.
Probably
the
last
item
is
to
move
see
advisor,
not
use
the
util
mount
because
render
packages
cannot
use
staging
modules,
so
I
have
they
asked
me
to
come
back
and
after
120
release.
So
probably
what
I'm
thinking
is?
I
open
up
an
issue
on
c
advisor.
K
H
Have
a
dialogue
there
and
see
if
they
are
willing
to
take
up
moby
library
as
a
alternative.
Sir.
D
H
I
can
I
can
work
with
them
and
make
that
happen,
for
if
they
agree,
that's
right
so.
A
Okay
thanks:
okay,
now
last
one
privatization
voting
capacity,
so
I
think
probably
will
still.
I
think
this
one
didn't
make
it,
but
I
think
it's
getting
really
close,
so
I
think,
should
be
still
talking
alpha.
C
A
C
C
I
mean
theoretically,
we
own
the
secrets
and
config
maps
stuff
for
volumes,
but
we
will
definitely
have
to
work
with
sigoth
on
on
the
design
of
this.
So
we'll
just
put.
C
All
right
do
we
have
anyone
jahweh
plans
to
look
at
this?
Oh
okay,
so
you
can
put
down
design
for
120.
C
A
I
think
it's
this
is
the
corner,
believe:
okay,
all
right,
thanks,
okay,
any
anything
else
on
this
spreadsheet.
A
Okay
back
to
here,
so
the
next
two
meetings,
the
the
next
meeting
will
be
canceled,
because
that's
the
new
year's
eve
and
coming
back
in
new
year
january
14th.
We
will
go
over
this
splashes
again
to
confirm
the
1.21
planning
and
so
there's
one
item.
So
I
actually
added
this
item.
I
don't
know
if
phone
is
here
just
want
to
bring
this
to
everyone's
attention.
So
this
is
something
that
the
data
protection
work
group
has
been
working
on.
A
A
So
if
you
know
the
storage,
vendors
can
take
a
look
and
see
you
know
whether
the
the
proposed
api
works
or
not
so
it's
you
know
we
look
at
vmware,
aws,
azure,
so
yeah
saf,
so
look
at
a
few
and
then
there
is
some
we
proposed
something
but
want
to
see.
If
the
century
works
for
everybody,
if
you
can
take
a
look
and
at
comments
it'll
be
great,
I
think
there
are
some.
There
are
some
questions
about
aws.
A
I
don't
know
if
anyone
working
on
aws
is
here
on
the
course
it
so
their
api
is
a
little
different
from
the
rest
of
those
apis.
So
we
like
to
get
their
feedback
and
see
if
whatever
we
propose
to
work
for
this
at
all
and
then
also
have
a
question
for
azure
disk.
A
So
since
the
kkk
looks
like
it's
not
on
the
com,
not
sure,
if
there's
anyone
else
who
is
working
on
azure
disk,
so
they
have
an
api,
but
it
looks
more
like
an
internal
api,
so
we're
not
sure
if
they
actually
have
an
api
that
can
be
used
for
this
purpose
yeah.
So
if
anyone
interested
in
this
take
a
look-
and
please
add
your
comments
there,
so
this
is
something
that
we
have
been
discussing
at
the
the
production
group.
F
Is
the
goal
basically
designed
this
quarter.
A
I
don't
think
we
are
there,
yet
we
still
have
okay
yeah
yeah,
this
yeah
this
quarter
is
designed.
Actually
so,
oh
maybe
should
we
also
yeah.
We
can
actually
also
add
that
it's
going
to
be
designed,
I'm
just
saying
I
was
actually
trying
to
say
we
won't
be
ready
for
alpha,
yet
yeah
so
design
we
can
yeah.
We
can
add
that
here
as
well.
So
yes
right
now,
it's
still.
I
think
it's
still
at
a
pretty
early
stage,
because
it
looks
like
aws.
Api
is
very
different.
A
So
unless,
if
we
have
like
two
different
options,
it
seems
to
be
a
little
hard,
but
we
also
want
to
get
input
from
other
vendors
to
just
to
see
what
works.
And
then
this
is
only
for.
This
is
for
blogs
is
that
we
are
not
addressing
the
change
file
list
yet
so
yeah
so
yeah.
I
will
add
entry
there,
so
we
actually
can
get
some
status
in
this
meeting
as
well.
A
Okay,
anything
else
we
want
to
discuss
in
today's
meeting.