►
From YouTube: Kubernetes SIG Storage 20190801
Description
Kubernetes Storage Special-Interest-Group (SIG) Meeting - 01 August 2019
Meeting Notes/Agenda: https://docs.google.com/document/d/1-8KEG8AjAgKznS9NFm3qWqkGyCHmvU6HVl0sk5hwoAE/edit#heading=h.z954sxirzsq2
Find out more about the Storage SIG here: https://github.com/kubernetes/community/tree/master/sig-storage
Moderator: Saad Ali (Google)
Chat Log:
None
A
A
As
a
reminder,
this
meeting
is
recorded
and
published
on
youtube
so
on
the
agenda
today,
primarily
we're
going
to
be
going
over
the
planning
spreadsheet
to
get
status
updates
on
the
items
that
the
cig
is
working
on
for
the
1.16
release
and,
of
course,
feel
free
to
add
to
the
agenda
any
PRS
that
you
think
need
attention,
designs
that
need
to
be
reviewed
or
any
miscellaneous
discussions
that
you
want
to
have
we'll
come
back
to
those
after
the
planning
session.
So
let's
go
ahead
and
jump
into
the
spreadsheet
and
start
getting
status.
A
B
B
We
did
discover
that
a
couple
of
things
are
needed
with
regards
to
bulk,
verify
and
verify
volume
attachment,
so
that
may
require
going
down
to
the
CSI
spec
and
making
some
improvements.
And,
finally,
the
the
last
thing
or
one
of
the
other
things
we're
looking
at-
is
disablement
of
the
CSI
of
the
entry
plug-ins
altogether
from
the
entry
code.
C
A
D
A
A
F
A
A
Next
item
is
block
volumes,
support
which
will
remain
in
beta
this
port,
but
we're
looking
into
doing
stress,
testing
and
fixing
known
issues
last
update
was
PRS
was
out
to
move
the
entire
mount
Lib
to
the
utilities,
repo,
which
is
the
wrong
status.
Update
I
think
we
just
put
that
in
the
wrong
place
then
or
Brad
any
updates
on
this
sure.
G
A
A
Number
five
interesting
things
have
been
all
switched
around:
okay,.
H
The
current
update
we
have
been
producing
test
results
for
one
load
test
cases
of
a
few
more
volumes
on
PVC
for
cluster
wide
test
cases.
Test
cases
are
implemented,
but
for
the
jobs
PR,
we
are
waiting
for
a
test
in
front
promote
to
run
one
job
with
many
test
cases,
because
otherwise
we
are
facing
some
resource
problems.
A
H
A
A
A
H
A
And
just
to
make
sure.
Okay
next
item
is
volume,
snapshot
transfer,
so
I
dropped
the
ball
on
this,
because
I
did
not
review
the
kept
in
time.
So
I
apologize
for
that
John
I
think
we
want
to
switch
this
to
design
as
the
goal
for
the
quarter
and
the
goal
will
be
to
get
a
cap
merged
and
if
we
get
it
merged
early
we
can
start
coding
it
and
and
then
we
can
move
it
to
alpha
next
quarter,
actually
get
it
merged
next
quarter.
Does
that
sound?
Okay,
yep.
A
D
A
D
A
F
A
D
Just
as
idiom
the
PR,
actually
it
was.
We
requested
the
the
author
of
the
pr2
to
just
handle
just
to
offline
resizing
as
us
to
begin
with,
because
it
was
getting
complicated
and
and-
and
he
addressed
the
change
like
to
the
morning
or
something's,
but
I
think
it
missed
the
enhancement,
freeze,
deadline,
I,
don't
know
if
he's
going
to
request
a
exception
or
not
I
don't
know,
but
but
it's
been
approved
and
lgt
and
okay.
A
J
A
A
A
Next
item
is
CSI
spec
alpha
beta
GA
designation.
So
there
are
a
new
set
of
new
proposals
going
out
for
the
CSI
spec
David
Zhu
has
some
changes
that
he
wants
to
get
in
for
CSI
migration,
which
deep
alluded
to
earlier
around
bulk
volume
attach
a
volume
attached
verify
and
bulk
volume
attach
verify,
and
then
there
were.
D
A
B
A
J
A
J
A
A
J
A
A
I
Yeah
so
ran
into
a
couple
of
things:
ete
test
exposed,
there's
a
bug
in
the
external
provision
area
and
a
bug
in
the
hospital
itself.
Prs
are
up
for
both
of
those
I
just
need
to
get
merged
and
we
can
do
backwards
and
we'll
be
fixed,
so
I
think
we're
good
I
think
we're
still
good
to
try
and
hit
beta
for
this
release.
Unless
Michelle
disagrees.
A
E
A
A
E
Anyway,
which
item
with
the
CS
I
prefer
g8
yeah,
it's
assigned
to
me,
I,
haven't
been
able
to
start
on
it,
but
yeah
I
plan
to
get
to
it
sometime
in
the
next
month.
Okay,.
A
B
H
H
C
C
However,
this
potential
block
over
here,
which
is
a
couplet
at
agent,
attach
workflow
I
discussed
with
Michelle.
Briefly,
on
that,
a
fair
comment
on
that
synthesis
to
be
deprecated
workflow,
we
just
don't
care
about
that.
Okay,
let
me
know
if
you
guys,
you
know
how
many
comings
and
that-
and
thank
you
very
much
for
inviting
me
to
insert
of.
A
J
A
J
A
E
A
A
J
A
J
A
This
is
actually
I,
think
Michelle
and
I
started
thinking
about
volume
group
API
last
late
last
quarter.
Okay
and
the
angle
that
we
were
thinking
of
that
was
four
volumes
spreading,
basically,
storage,
topology,
and
we
think
that
this
would
be
a
very
nice
way
to
be
able
to
handle
that
use
case
as
well,
and
Haley
was
looking
into
that
last
quarter
as
well,
and
so
based
on
that,
okay.
J
J
Yeah,
so
I
did
have
a
calling
card,
except
asking
her
for
a
use
case,
so
it
looks
like
for
the
spreading
I
think
he.
She
still
needs
a
custom
scheduler
to
do
that
because
she
wants
you
basically,
so
the
volumes
seen
the
same
safer
set
has
to
go
to
like
different
racks
right.
So,
but
if
it's
in
the
same
group,
usually
you
want
them
to
be
together,
I
mean
I
at
least
I.
Haven't
the
fun,
haven't
a
on
a
way
to
say,
you're
different.
A
J
Yeah
sure
so,
I
think
when
I
talk
to
her
I
thought,
you
know
I
think
that
she
still
needs
the
group
concept.
I.
Think
right
now
she
used
some
annotation
for
that
I
think
she
can
still
use
the
group,
so
she
is
interested
in
in
helping
out
so
the
scheduling
part
of
spreading
for
them
I
still
but
yeah.
Let's
talk
about
it.
Yeah.
I
A
I
mean
so:
that's
that's
the
plan,
that's
what
we
want
to
do,
but
I
think
before
we
do
that
I
kind
of
wanted
to
think
through
all
the.
How
would
somebody
go
and
implement
this
thing
and
how
do
we
do
the
PvP
BC
hold
off,
meaning
prove
key,
getting
all
of
that
yeah
I
guys
figure
out
that
design,
and
once
we
have
that,
then
we
can
I
think
it's
that
the
easy
part
is
just
lifting
that
validation.
Okay,.
E
A
A
A
I
A
I
I
Yeah
that
one
I
mean
I
think
that
one's
ready
for
people
to
try
and
use
it.
Quite
frankly,
there's
there's
been
some
debate
about
direction
and
enhancing
it
to
use.
Go
plugins
I'm,
not
a
fan
of
that
so
but
yeah,
it's
it's
it's
ready
for
use
and
then,
if
we
wanted
to
take
it
further,
we're
certainly
in
a
spot
that
we
can
do
that.
Okay,.