►
From YouTube: Kubernetes SIG Storage 20200227
Description
Kubernetes Storage Special-Interest-Group (SIG) Meeting - 27 February 2020
Meeting Notes/Agenda: https://docs.google.com/document/d/1-8KEG8AjAgKznS9NFm3qWqkGyCHmvU6HVl0sk5hwoAE/edit#heading=h.423bmxgp6tsk
Find out more about the Storage SIG here: https://github.com/kubernetes/community/tree/master/sig-storage
Moderator: Saad Ali (Google)
A
All
right
recording
started,
so
let
me
share
my
screen.
All
right
today
is
February
27
2020.
This
is
the
meeting
of
the
kubernetes
storage
special
interest
group.
As
a
reminder,
this
meeting
is
public
recorded
and
posted
on
YouTube.
So
today,
on
the
agenda,
we're
gonna
go
over
the
q1
2020
planning
spreadsheet,
to
figure
out
what
folks
are
working
on
for
this
release
and
what
the
status
is.
If
you
have
any
PRS
that
need
attention
or
designs
that
need
review,
feel
free
to
add
them
to
the
agenda
doc.
A
The
link
is
in
the
meeting
invite
and
if
there's
anything
else
that
you
want
to
discuss,
please
feel
free
to
add
it
to
the
bottom
of
the
agenda.
We
are
having
issues
with
our
favorite
spreadsheet,
so
we're
gonna
chase
that
down
after
the
meeting
to
figure
out
what
happened
in
the
meantime,
my
slightly
cumbersome
workaround
is
to
look
at
the
previous
meetings
recording
and
just
have
a
temporary
spreadsheet
where
we
put
in
the
current
status.
So
please
bear
with
me
as
I.
Do
that
so.
A
B
Yeah
I
will
be
updating
the
happy
Robin
and
David
heads
up
come
in
so
I'm
going
to
update
the
PR
by
to
the
end
of
day,
I'm
working
on
peer
for
readwrite
multi
resizable,
that
I
should
have
in
by
wareness
T
or
something
mystic.
But
both
of
these
fixes
are
bug,
fixes,
don't
require
any
feature
gates
and
we
I'm
still
I'm
yet
to
schedule
a
call
for
desiring
the
recovery
from
research
failure
meeting
but
I'll
do
it
sometime
next
week.
I
think.
A
C
D
E
E
B
F
A
A
A
G
I'm,
getting
a
fair
number
of
test
failures
after
I
tend
to
update
all
of
the
files
that
you
use
for
cycle
mode,
I've
rolled
back
that
commit
and
I'm
trying
to
get
the
test
to
pass
and
just
with
the
API
changes
and
the
updated
files.
If
those
pass,
then
I'll
reintroduce
all
of
the
changes
and
then
go
through
the
test
failures
one
by
one,
it's
still
in
progress.
G
A
E
So
there
was
a
CSI
PR
that
is
being
reviewed.
So
sad.
If
you
can
go
ahead
and
review
that
ok
great
there
was
a,
there
was
a
off
our
API
PR
that
isn't
actually
from
James.
The
Waterhouse
PR
has
a
dependency
on
that
one.
Oh,
so
we
got
it.
Repo
was
created
under
a
quantity
CSI
for
the
son
wanted
to
in
control
an
agent.
E
I
This
one
yeah,
all
the
code
is
done,
except
for
my
unit
tests
and
the
PR
role
yep
today,
I'll
be
looking
for
reviews.
It's
a
very
small
change
that
the
tests
will
probably
be
by
far
the
largest
part
of
it,
and
so
I
just
wanted
to
mention.
I
I
looked
at
this
spreadsheet
like
two
or
three
days
ago
and
like
half
the
rows
were
missing.
Yeah.
A
I
think
the
mistake
that
we
made
was
give
everybody
right
access
to
it
in
SIG's
storage,
which
was
a
bad
idea.
We've
had
issues
of
people
moving
around
roads
and
things
like
that,
and
you
have
to
undo
it
so
I'm
gonna
hunt
down
the
owner
of
the
spreadsheet
and
see
if
they
still
have
access
to
it
and
then
get
things,
reverted
and
fixed
and
then
probably
remove
permission
for
generics
for
sig
and
just
give
it
to
the
leads.
Why.
I
E
I
A
J
Yes,
so
I
got
two
volunteers
for
the
NFS
driver
and
two
for
the
ice
cozy
drivers,
a
couple
of
PRS
were
put
out
to
update,
go
mod
and
import
our
release
tools.
Infrastructure
I
need
to
follow
up.
I
need
to
follow
up
with
the
I
need.
Yeah
I
need
to
follow
up
to
look
at
the
next
steps.
Oh
come
on
actually
getting
out
builds,
oh.
A
A
J
So
I
think
the
main
goal
for
this
release
is
to
try
to
get
the
other
clouds
and
moving
towards
a
beta,
I
believe
so
OpenStack
I
think
has
CI
running
in
things,
I'm,
not
sure.
If
they're
ready
to
move
to
beta
this
release,
we
will
need
to
follow
up
with
I
forgot.
If
is
Erin
on
the
line,
I
think
Erin
volunteered
to
be
an
openstack
spokesperson.
J
J
E
Yeah,
so
we
so
not
for
not
for
this
release,
but
for
the
the
next
release
we
are
going
to
go
beta,
but
but
then,
when
we
read
the
requirement
it
requires
patek
CI.
So
we
still
need
to
use
for
that
out,
because
if
we
can't
set
up
a
public
CI,
we
can't
really
go
beta
right.
Then
that
means
even
human
da
19
will
still
be
alpha.
That
kind
of
late.
Isn't
it
so?
Do
you
have
some
like
requirements
because
eventually
in
1.21
it
will
be
the
entry
drivers
will
be
removed?
E
Do
you
what
is
I
remember?
You
said
something
like
to
releases.
So
let's
say
'if
went
on
and
he
was
still
are
far.
Is
that
enough?
That's
and
then
that
means
I
went
out
twenty.
They
but
I
think
the
what
definitely
won't
get
the
code
ready
for
follow
beta.
You
went
down
ninety,
but
I
think
the
puppy
Sam
right
now
it's
the
one
that
we
need
to
figure
out.
Why
did
you
sure
yeah.
J
H
E
A
E
J
H
A
H
A
C
C
A
E
A
F
F
A
A
A
That
way,
we
can
kind
of
distribute
the
load
a
little
bit.
So
I
wanted
to
thank
all
three
of
them
for
volunteering
and
helping
helping
out
here
and
please
feel
free
to
reach
out
to
them
offline
to
thank
them
as
well,
and
if
there's
nothing
else,
then
we'll
call
it
for
today
and
we'll
reconvene
in
two
weeks,
I.