►
From YouTube: Kubernetes SIG Storage - Bi-Weekly Meeting 20201022
Description
Meeting of Kubernetes Storage Special-Interest-Group (SIG) - 22 October 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
B
Yes,
sorry,
okay,
so
the
plan
for
this
quarter
is
to
keep
the
feature
in
beta
and
work
on
work
on
getting
some
of
the
enhancements
kept
actually
sorted
out.
So
we
have
two
bugs
that
I'm
working
on
fixing
it
and
one
is
kk,
volunteer
to
take
a
look
at
it,
which
is
was
pvc
deleted.
So
basically
and
then
another
one
is
read:
write
many
which
didn't
get
merged
in
the
last
quarter.
B
So
that
was
that
and
then
there's
a
pr
to
add
secrets
to
node,
expand
volume,
call
and
then
the
allow
volume
expansion
moving
that
field
to
pv
so
I'll,
open
a
cap
for
that,
but
we're
not
making
the
api
changes
for
that
in
this
release.
B
A
I
think
the
next
one
is
okay,
that's
recovering
from
resize
failure.
A
Thanks
next
one
snapshots,
so
we
are
trying
to
bring
you
to
ga.
We
had
a
api
review
meeting
so
get
some
good
feedback.
So
we're
working
on
addressing
comments
and
also
our
work
on
metrics
on
the
snapshot
controller
into
e3
tests
are
our
work
in
progress.
Next
one
is
a
non-recursive
volume
ownership.
Fs
group:
do
we
have
a
yeah
go
ahead.
B
B
A
pr
to
move
the
feature
to
beta
this
week
and
like
early
like
tuesday,
so
okay.
A
Here
so
this
I
think
this
yeah,
so
I
look
at
this
this
pr
here
I
reviewed
it
star.
Can
you
also
take
a
look
because
thank
you.
There
is
one
question
on
on
this
class:
okay,.
A
A
Thanks
next
one
is
the
issues
related
to
assuming
volumes
are
mount
points.
Do
we
have
andy
chain.
F
G
H
H
A
G
A
Great
thanks
next
one
is
the
story.
Capacity
tracking,
I
don't
know
if
patrick's
here.
G
Michelle
young,
do
you
know
status
he's
been
investigating
some
of
the
the
issues
that
we
identified,
so
I
think
he's
working
on
it.
Okay,.
G
Yeah,
the
last
status
here,
I
think,
was
that
we
need
to
schedule
a
meeting
to
discuss
what
we
want
to
do
with
the
api,
because
we
have
both
this
feature
and
the
next
feature
which
sort
of
overlap
a
little
bit.
So
we
want
to
figure
out
how
to
make
the
api
consistent
and
not
confusing
yeah.
A
A
Okay,
so
next
one
starting
over
failure
domains.
I
have
not
got
an
update
on
this
because
this
actually
is
dependent
on
the
next
one
one
group
api,
so
I
just
updated
the
cap
just
for
the
for
modify
the
volume
group.
I
just
added
some
description
there
saying
that
we
are
going
to
address
that
in
the
controller
trying
to
reconcile
the
pvc
list
in
a
group
trying
to
do
like
one,
one
csi
call
to
modify
the
group.
So
so
please
take
a
look
of
the
cap.
If
you
are
interested.
G
Yeah,
I
still
haven't
gotten
a
chance
to
address
these,
but
yeah
it's
on
my
plate
to
do
I'll,
try
to
do
it
in
the
next
couple
of
weeks.
F
A
A
Thanks
next
one
is
okay,
move
out:
clusterfs
provisioner.
A
Okay,
I'll
put
no
update
here.
Unless
someone
has
an
update-
and
this
is
a
current,
do
you
are
you
there,
karen
this
isn't
about
nfs
provisional?
I
think
these
two
similar
ones
to
repose
okay,
looks
like
no
update.
C
Hi
yeah,
so
the
previous
kept
was
closed
for
lack
of
activity,
so
I
created
a
new
cap
in
the
new
format
and
hopefully
we'll
get
more
activity
here.
I'm
also
working
on
a
reference
implementation.
So
probably
so
I
think
once
that's
done
I'll
have
some
sort
of
review
great
yeah.
A
Next
one
is
boarding
house,
so
we
do
have
a
pr
on
implementing
volume
house
in
csi
postpass
driver.
So
I
think
that
one
just
needs
some
more
testing
before
we
can
get
that
in
and
next
one
is
generic
data.
Populator
then.
I
Yeah,
so
we
have
started
doing
weekly
meetings
on
this
to
get
work
done
the
invite
for
that
went
out
to
the
six
storage
mail
list.
Hopefully
you
guys
all
saw
it.
We
had
our
inaugural
meeting
this
week
and
we've
already
made
one
important
decision,
which
was
to
not
pursue
the
validating
web
hook
approach
and
to
to
go
back
to
the
original
idea
of
just
having
a
controller
that
watches
pvcs
and
generates
events.
I
So
I'm
going
to
be
updating
the
kep
to
reflect
that
approach,
updating
the
prototype
and
we'll
keep
discussing
populated,
related
issues
on
that
tuesday
meeting.
A
Next
one
is
cozy.
A
It's
jeff,
or
anyone
sit
here
or
saudi,
want
to
give
an
update
on
this.
E
Yeah,
if
no
one
else
is
on,
I
can
give
an
update.
They
have
the
cap
merged
and
they're
continuing
to
work
on
the
prototype
and
the
target.
Again
the
for
this
quarter
is
the
prototype.
E
I
think
said
it's
going
to
give
a
talk
at
cubecon
about
this
topic
and
for
the
next
release.
121
they'll
target
an.
A
A
J
Yes,
so
there's
an
open
pr
to
include
the
end-to-end
test,
there's
a
second
open
pr
to
move
this
to
beta
and
also
to
relax
validation
since
we're
planning
on
introducing
new
enums
and
a
subsequent
release
both
of
those
the
intent
test
has
been
preliminarily
reviewed,
but
it
needs
to
be
actually
get
the
lgtm
approved
and,
and
the
second
pr
hasn't
been
reviewed
just
yet,
but
we
should
be
on
track.
A
G
A
Okay
thanks
next
one
is
cs:
migration,
vsphere
is
the
deviant
here,
so
I
think
the
back
port
one
is
still
in
progress.
So
hopefully
we
can
get
some
update
on
that
soon.
G
No,
I
don't
know
the
status
I'll
go
ahead
and
sync
up
with
andy.
Okay,.
A
Thanks
next
one
see
the
migration
gce
is
maddie's
work
on
this.
G
G
A
A
A
Okay,
the
next
one
is
so
we
have
a
few
projects
that
we
co-owned
with
the
sig
apps.
The
first
one
is
address
issue.
I
A
I
C
I
A
G
A
I
don't
know
something
yeah
something's
wrong.
I
can't
hear
her
at
all.
Okay.
Next
one
is
one
expansion
for
safer
sets.
I
think
was
okay.
It's
working
on
this.
A
A
So
we
are
still
trying
to
resolve
some
of
the
review
comments
so
right
now
we
we
don't
have
one
more
update
on
this.
Yet
next
one
is
kubernetes.
Udo's
month
split
you
a
new
repo.
D
Yeah
hi:
this
is
trini
yeah.
I
haven't
done
much
work
this
these
two
weeks,
but
the
dependency
on
c
advisor
has
the
pr
has
been
merged.
So
there
is
no
other
problem
right
now.
We
just
have
to
take
the
details
mod
out
of
the
vendor
directory.
That's
the
last
piece
missing
so
I'll
work
on
it.
D
A
G
Oh,
I
haven't
seen
any
pr's
related
to
this
okay,
I
can
I'll
sync
up
with
ya
chang
on
that.
A
All
right
thanks,
okay,
so
that's
all
on
our
spreadsheet
okay,
so
we
don't
have
any
other
pr's
or
issues
that
are
added
to
the
agenda
doc.
There
anything
else.
Anyone
want
to
discuss
in
the
meeting.
A
Okay
and
if
not,
then
that
is
all
for
today
thanks
everyone
bye
thank.