►
From YouTube: Kubernetes SIG Storage 20190718
Description
Kubernetes Storage Special-Interest-Group (SIG) Meeting - 18 July 2019
Meeting Notes/Agenda: https://docs.google.com/document/d/1-8KEG8AjAgKznS9NFm3qWqkGyCHmvU6HVl0sk5hwoAE/edit#heading=h.mvp7r6ryf097
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
All
right
today
is
July
18
2019.
This
is
the
meeting
of
the
kubernetes
storage
special
interest
group.
So
today
on
the
agenda,
we're
gonna
go
over
the
items
that
we've
committed
to
for
q3
the
116
release
and
get
status
updates
from
everyone.
Important
upcoming
dates
that
you
should
be
aware
of
the
most
immediate
one
is
the
enhancement
freeze.
This
is
the
date
by
which
you
must
have
a
issue
in
the
kubernetes
enhancement
repo
opened.
A
So
please
keep
that
in
mind.
This
date
is
within
two
weeks,
which
means
we're
not
going
to
meet
again
before
this
date.
Please
make
sure
you
get
whatever
you
need
merged
before
the
state
arrives,
so
let's
go
ahead
and
jump
into
our
spreadsheet
and
start
doing
status.
Updates
first
item
we
have
is
CSI
migration
to
beta.
A
B
A
C
We
say
that
it
would
remain
beta,
even
if
we
fixed
all
the
known
issues
that.
C
Yeah
then
I
need
to
update
something
in
github,
but
but
yeah
we
have
a
list
of
issues
that
we're
tracking
and
working
on.
D
E
C
F
I'm
I'm
here,
one
PR
about
two.
First,
two
cases
of
a
familiar
balloon
was
merged
to
the
performance
test
of
scalability
and
I
opened
another
PR
to
add
these
test.
Cases
to
periodic
jobs
of
scalability
and
I
am
also
working
on
another
PR
for
the
last
case
cases
most
ephemeral
balloons,
one
more
point:
primal
I
am
only
working
for
ephemeral
volume.
I
think
there
are
another
person
who
work
on
the
PVC
size.
E
A
H
A
A
I
A
A
A
A
J
I
A
Thank
You
Mathewson
next
is
the
I
scuzzy
driver.
John
is
not
here
we'll
just
mark
that
as
no
updates
and
then
moving
fiber
channel
nobody's
working
on
the
fiber
channel
driver.
Anyone
interested
in
helping
move
the
fiber
channel
driver
to
a
new
home
and
updating
it
and
making
sure
it
actually
works
and
builds,
and
all
that.
A
A
A
A
B
So
the
enhancement
looks
much
better,
but
I
think
there
was
a
outstanding
there's.
A
I
was
starting
to
Michelin.
There
was
open
concern
that
only
for
offline
expansion
there's
this
chance
that
if
the
expansion
failed,
we
may
not
be
able
to
recover
the
parts
like
bring
them
back
online
because
the
stateful
controller,
the
design,
says
that
it's
it's
going
to
wait
for
the
expansion
to
finish
before
restarting
the
park.
So
I
think
you
need
to
think
on
that.
So
it.
A
A
A
A
L
D
A
A
I
A
M
I'm
here
before
that,
can
you
hear
me
yep,
okay,
yeah,
so
we're
talking
we
were
talking
about.
The
name
is
over
talking
about
the
design
and
I.
Think
I
miss
a
discussion
where
there's
an
idea
for
a
new
API
check
that
CSI
would
take
in
called
a
volume
group.
Your
object
and
I
think
I
think
what
the
context
I
have
I
think
that's
a
better
design
overall
than
kind
of
putting
a
a
metadata
annotation
into
it.
M
So
I
think
I
don't
have
the
capacity
to
do
that
whole
API,
but
I'm
willing
to
work
on
the
the
part
where
you
know
that
that's
a
related
to
the
volume
spreading
yeah,
so
I
think
just
at
first
blush
I
think
having
something
similar
to
like
a
topology
requirement.
I
think,
potentially
that
and
just
a
unique
ID
on
the
create
volume
call
would
be
the
would
be
a
way
to
do
it.
A
I'll
put
you
down
for
a
route
as
a
reviewer
for
volume
group.
If
I
can
find
volume
group,
let's
see.
A
Okay,
I'll
do
that
later,
but
for
number
2030
I'll
just
go
ahead
and
scratch
that
for
now,
thanks,
Haley
yeah
feel
free
to
sync
up
with
Shing
or
Jing
on
the
volume
group
stuff
sure.
Thank
you.
Next
item
is
CSI
entry,
read-only
handling.
We
were
looking
for
somebody
to
help
own
this
John
I
think
you
preliminary
put
your
name
down
any
progress
or
renewed
commitment
here.
L
A
K
K
A
A
A
A
A
A
B
G
A
E
J
A
A
A
On
to
the
rest
of
the
agenda,
as
a
reminder,
please
make
sure
your
enhancement
issue
and
keps
are
approved
and
merged
by
July
30th
frame.
Those
features
that
you're
working
on
for
this
quarter
and
we
don't
have
any
PRS
to
discuss
or
designs
to
review.
We
have
a
few
miscellaneous
items
from
Michelle,
Chang
and
yon.
So,
let's
start
with
the
first
one:
deprecating
cubelet
attach
detach
Michelle.
E
Yeah
I
think
oh
did
I
point
it
a
wrong
issue.
I
think
there
is
well
in
this
issue.
I
sorry
go
back
in
this
issue.
I
have
a
link
to
another
issue
there
yeah,
but
I.
Think.
Basically,
this
option
has
pretty
much
been
untested
for
a
very
long
time
and
it's
very
likely
that,
as
we
add
new
features
and
stuff,
we're
gonna
forget
about
forget
about
this
option
and
it's
going
to
break
so
I
propose
that
we
actually
replicated.
E
M
M
E
E
N
So
I
brought
this
up
about
a
month
ago,
and
the
plan
at
that
time
was
we're.
Gonna
send
out
a
survey
in
this
sink
to
ask
who
was
still
on
who
uses
any
of
the
master.
Api
calls
for
flexo
Liam.
So
far,
I
haven't
gotten
any
responses.
My
next
step,
I
was
thinking,
is
to
send
it
out
to
a
wider
audience
broadcaster
to
convert
a
dev
and
see,
if
anything
happens.
H
So
I
announced
the
intent
to
the
perk
eight,
the
Registrar
two
weeks
ago
and
since
then
I
got
only
positive
feedback,
so
it
is
actually
mostly
like
announcement.
I
started
or
remove
operating
the
documentation
and
all
the
best
and
everything
so
the
Registrar
it
wasn't
working
seems
permit
is
114.
We
didn't
ship
it
in
114,
we
didn't
ship
in
115,
nobody
seemed
to
miss
it.
So
now
it's
officially
deprecated
and
you
should
not
use
it.
H
A
Thank
you
very
much,
yawn
I'm.
So
if
you
are
a
CSI
driver
owner
and
you've
been
relying
on
the
cluster
driver,
registrar
side,
car
container,
please
note
that
that
side
car
container
has
been
deprecated.
It's
imported
there's
a
different
mechanism
for
doing
what
it
does.
Please
make
sure
you
update
your
CSI
driver
to
handle
this
correctly,
as
you
do
updates
all
right.
That
is
the
last
item
we
have.
Does
anybody
else
have
anything
else
they
want
to
talk
about.
G
A
G
K
So
I
think
like.
If
you
have
eggs
pink
PVC
for
a
in
Crete
driver,
then
what
happens?
Is
everything
stays
the
same
as
far
as
the
user
is
concerned?
But
when
the
feature
flags
for
migration
is
enabled,
then
the
entry
has
a
bunch
of
shims
that
he
direct
all
the
operations
from
the
in
Creek
ode
to
the
CSI
code,
yeah.
A
A
G
A
K
G
Provisioning
seems
a
little
easier
then,
so
we
try
to
approach
one
that
you
mentioned,
create
new
PDS
with
CSI
someone
on
our
team.
You
know
notice
that
couplet
has
a
cache
and
even
though
we
updated
the
PV
Seavey's,
sometimes
we'll
get
a
call
to
the
CSI
driver.
Sometimes
we'll
get
a
call
to
the
Flex
driver,
depending
on
the
Kubla
cache.
A
G
G
E
Think
you
can
migrate
in
place,
but
then,
as
you
mentioned,
it
might
call
it
might
still
call
the
Flex
driver
or
a
might
call
the
csi's
driver
depending
on
how
it's
cashed,
but
once
you
drain
the
pods
from
that
node,
then
you
know
cubelet
no
longer
you
know
all
that
information
should
be
cleared.
Okay,.