►
From YouTube: Kubernetes SIG Storage - Bi-weekly meeting 20201119
Description
Meeting of Kubernetes Storage Special-Interest-Group (SIG) Bi-weekly - 19 November 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
Okay,
hello.
Everyone
today
is
november
19th
2020..
This
is
the
kubernetes
storage
sig
meeting
this
meeting
will
be
recorded
and
be
available
on
youtube.
Let's
go
through
our
1.20
planning,
so
we
have
just
passed.
The
code
freeze
deadline
november
12th
last
week.
The
next
deadline
is
no
one
november
30th,
that's
the
stock,
merge
deadline.
A
B
No
update
since
last,
actually
we
we
tried
to
build
consensus
now
recover
from
resales
failure
we
didn't
manage
to
quite
yet
we
have
some
work
to
update
the
update
the
cap
for
allow
volume
expansion
that
will
I'll
be
doing
in
next
few
days
or
a
few
weeks,
and
then
we
can
target
next
release
for
remaining
items.
A
Okay,
so
that's
the
next
item
right
next.
Okay,
thank
you,
okay,
so
I
think
the
next
one
is
one
snapshot,
so
we
actually
so
we
got
the
entry
feature
kpr
merged,
so
we
made
the
deadline.
The
ap,
the
api
change
to
move
snapshot.
Api
to
v1
is
also
merged.
A
Dock
pr
is
merged,
so
we
are
working
on
updating
the
release,
tools
and
the
various
things,
and
also
we
have
a
few
prs
that
are
being
reviewed,
including
work
on
adding
matrix
support
on
the
snapshot,
controller,
supported
server
rotation
for
the
web
hook
and
then
use
the
driver
from
tv
instead
of
a
switch
class,
and
then
we
also
have
been
working
on
eq
tests.
Those
are
the
finalizer
and
distress
test
are
merged
and
then
there's
et
test
for
secrets
that
is
being
reviewed
and
there's
also
a
test
for
metrics.
C
I
can
speak
to
this
if
no
one
else
wants
to,
or
I'm
not
I
mean
it's
just
that
like
that
tlr
is
merged
for
120.
A
Next
one
is
a
secular
linux.
Cursive
permission
handling,
so
this
says
design
yarn.
Is
there
any
update
on
this
one.
B
No
update,
actually
we
so
we
did
have
a.
We
do
have
a
broad
concern
about.
How
do
you
want
to
fix
this,
but
we
had
to
update
the
right
cap
and
capture
the
cap
and
we'll
try
to
do
this
in
the
next
release.
A
A
A
A
The
next
one
is
also
patrick's,
so
I
believe
there
is
a
meeting
for
this
one.
Does
anyone
want
to
give
an
update
pvc
inline
fm.
A
Volume,
so
sad:
did
you
attend
that
meeting?
Do
you
want
to
give
an
update
on
this.
A
This
is
the
generic
fmr
volume.
D
Oh
right,
yeah
so
update
here
is:
there
is
going
to
be
basically
a
a
new
api
for
this
and
we're
trying
to
align
it
with
the
existing
csi
ephemeral
volumes.
Patrick
is
going
to
continue
to
own
the
generic
ephemeral
volumes.
D
We
are
looking
for
a
new
owner
for
the
csi
ephemeral
volumes
to
drive
that
to
beta
and
align
that
api
with
the
generic
ephemeral
volume,
api
and
yeah.
If
anyone's
interested.
Let
us
know
otherwise
we'll
circle
back
internally
and
see
if
we
can
find.
A
A
A
A
Okay,
so
next
one
spreading
over
a
few
domains
is
the
same
same
thing.
This
is
still
depending
on
the
next
item.
So
it's
the
same
thing
and
then
for
the
next
one
voting
group
api.
So
I
will
schedule
a
meeting
after
thanksgiving.
A
Do
we
have
any
it
looks
like
we
don't
have
any
update
for
a
few
meetings
now
looks
like
michelle
is
not
not
on
the
call
right.
So
do
you
do
you
know
anything
about
this?
Is
this
still?
I
should
put
down
no
update
for
this
three.
D
What
are
the
three
items?
Sorry.
D
Yeah,
I
think
michelle
said
she
was
planning
to
get
to
the
second
to
after
code
freeze.
I
don't
think
she's
gotten
to
that
yet
and
the
first
one
is
no
update.
A
Okay,
so
the
next
one.
Oh
look,
look
at
this
one
is
dark,
move
out,
cluster
fs
provisioner,
that's
done
that's
good,
and
then
we
have
a
two
nfs
related
move
out:
nfs,
provisioner
and
nfs
client
provisioner
is
karen
on
the
call
he's
maybe
at
cubecon.
D
No,
I
don't
have
an
update
on
that.
Okay,
there's
no
update.
A
Next
one:
okay:
next
one
is
volume
house,
so
we
are
still
working
on
the
host
bus
driver,
one
house
implementation,
so
the
pr
has
been
reviewed.
Eq
test
is
pending
because
it
we
need
to
have
that
implemented
in
the
hostpass
driver.
First
and
next
one
is
the
generic
data
populator
ben.
Do
you
have
an
update
on
this.
F
There
has
been
very
little
progress
on
this,
the
last
two
weeks.
Unfortunately,
I
mean
I'm
still
working
on
it,
but
I've
had
some
big
distractions.
Unfortunately,
those
are
getting
wrapped
up.
So
look
for
progress
next
month.
Okay,.
G
Yeah
this
is
trini.
We
are
making
good
progress
on
the
coding
site.
We
are
able
to
make
good
progress
on
the
csi
adapter
as
well
as
test
driver.
We
are
waiting
for
some
decision
to
be
made
on
the
protocol
structure.
G
We
will
be
discussing
that
today
in
our
meeting.
We
don't
want
to
have
protocol
specific
fields
and
make
them
opaque,
so
that
will
be.
That
needs
to
be
decided
for
us
to
continue
with
the
work
on
the
central
controller
and
the
provisioner.
So
that's
the
status
right
now.
G
E
H
A
Thank
you.
So
I
have
a
few
items
crossed
out.
So
the
next
one
is
the
csm
aggression.
Vsphere
is
a
deviant
here
by
any
chance
yeah.
So
I
actually
have
an
update,
so
actually
the
back
part
finally
got
approved,
so
it's
so
it
so
it
won't
be
in
the
upcoming
201
release,
because
that
one
is
going
to
be
out
soon,
but
it
will
be
released
after
that.
D
I
think
michelle
said
that
andy
found
a
couple
of
bugs
in
core
that
need
to
be
addressed.
Basically,
this
is
being
worked
on.
A
B
I
gave
last
update
that
I'll
try
to
find
an
owner
and
it's
still
the
same.
If
nobody
else
steps
up,
then
the
like
our
team,
like
miyan
and
christian,
will,
will
own
this
piece.
A
A
Okay,
thank
you,
so
the
next
one,
okay.
So
those
are
a
few
projects
that
we
co-owned
with
the
sig
apps.
The
first
one
is
address
issues
pv
cd
graded
by
staple
side
will
not
be
auto
removed.
I
A
Thank
you
so
the
next
one
is
a
project
we
called
with
a
seek
node
content.
Notifier.
We
still
need
to
schedule
a
meeting
to
sort
out
some
of
the
api
design
issues
so
and
next
one
is
this:
is
I
just
had
it
the
other
day,
so
this
is
actually
signaled
enhancement,
size
memory,
backed
volume,
so
command
reviewed
it.
So
you
want
to
give
an
update
on
the
smart
command.
B
A
And
next
one
is
copenhagen,
udo's
months
blue
to
a
new
repo
srini.
Do
you
have
an
update
on
this.
G
Yeah,
actually,
I
ran
into
a
bit
of
a
problem
there
because
c
advisor
pr.
I
I
got
merged,
but
we
had
to
revert
it
back
because
the
vendor
software
cannot
use
the
staging
libraries,
so
dims
reverted
my
pr
on
c
advisor.
So
that
is
the
only
component
that
is
dependent
on
mount
details
from
the
staging.
Okay.
Eventually
dim
said
that
he'll
he'll
work
with
me
after
120
go
threes
to
to
to
make
some
progress.
G
A
A
Next
one
is
the
one
that
we
call
with
six
scheduling
prioritization
on
volume
capacity.
I
think
this
one
is
delayed
to
1.21,
because
I
think
that
he
didn't
get
time
to
finish
tests,
so
this
is
a
laid.
A
Okay,
I
think
that's
all
we
have
on
the
spreadsheet.
We
don't
have
any
more
items
here.
Are
there
anything
else
people
want
to
discuss
in
the.