►
From YouTube: Kubernetes SIG Storage 20190815 (Part 1/2)
Description
Kubernetes Storage Special-Interest-Group (SIG) Meeting - 15 August 2019
Meeting Notes/Agenda: https://docs.google.com/document/d/1-8KEG8AjAgKznS9NFm3qWqkGyCHmvU6HVl0sk5hwoAE/edit#heading=h.3me3hi5v72yu
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
Alright,
let's
go
ahead
and
get
started
today
is
August
15,
2009
teen.
This
is
the
meeting
of
the
kubernetes
storage
special
interest
group.
As
a
reminder,
this
meeting
is
public
recorded
and
published
online.
So
today,
on
the
agenda,
we
have
primarily
planning
going
over
the
items
that
the
the
cig
is
working
on
for
the
q3
1.16
release
of
kubernetes
will
get
status
updates
from
folks
who
are
working
on
items.
The
important
dates
to
remember
are
here:
the
next
upcoming
one
is
August
29,
which
is
code
freeze,
which
is
about
two
weeks
from
now.
A
So
if
you
have
features
that
are
pending,
please
keep
that
date
in
mind.
I,
don't
see
anything
in
PRS
to
discuss
or
design
reviews
or
any
other
miscellaneous
items.
But
if
you
have
anything,
please
feel
free
to
add
to
the
agenda
and
once
we're
done
with
planning
we'll
go
over
those
items,
switching
over
to
planning,
let's
go
ahead
and
get
started
here.
I
cleaned
up
the
spreadsheet
a
little
bit
last
time
to
fix
the
the
sorting
issues,
so
that
should
be
good
to
go.
B
That's
a
work
in
progress.
The
second
one
is
the
CSI
spec
change
around
less
volume,
improvements
to
make
sure
that
the
volumes
are
has
seen
and
the
Third
Point
is
completely
disabling,
all
plug-in
code
within
with
an
increase
so
that
at
some
point,
when
we
do
plan
to
remove
the
code,
there
are
no
unexpected
results.
A
C
So
there's
a
PR
open
for
fixing
the
bug
about
the
block
volume
and
Fabio
I
had
his
fieldwork
helped
me
out
with
the
tests
actually
to
make
sure
that
we
are
running
the
resizing
test,
I'm
working
on
in
a
bring
the
feature,
gate
and
I.
C
We,
we
discovered
it
a
small
issue
with
with
raw
block
resizing
where
we
should
not
resize
the
volume
if
it
was
if
it
is
being
used
in
Rob,
lock
mode,
and
it
has
a
file
system
on
it.
So
all
the
driver
author
should
fix
it.
I
was
going
ahead
and
filing
issues
in
my
file,
issues
for
AWS
and
GC
driver.
There
was
already
Mitchell
open
issue.
Is.
C
C
Like
and
I
have
opened
sorry
I
have
opened
a
PR
in
CSI
repository
for
like
in
the
long
run.
We
want
to
have
the
capability
available
in
the
both
node
expansion
and
controller
expansion.
Calls
actually
show
that
right
now
it
is
possible
to
detect
the
volume
mode
by
checking
the
volume
path
like
if
it
is
Rob
Lowe.
A
D
A
E
C
A
small
thing
to
add
on
to
this
wonder:
I
would
request
I,
don't
know.
What's
the
best
way
to
communicate
this,
but
I
would
request
all
the
driver.
Csa
drivers
have
a
CLI
parameter
that
allows
the
limits
to
be
overridden
actually
because
this
was
intended,
but
but
I'm
not
sure
if
all
the
plugins
support
it
and
the
reasoning
is
like
sometimes
the
limits
that
we
read
from
a
new
cloud
provider
may
not
be
sufficient.
So
it's
something
to
call
out
our
to
discuss
this
problem.
Csf,
lamentation,
Cup,
okay,.
F
C
C
Similarly,
it
may
be
like
you're
running
on
GC
GC
PD,
and
you
have
other
volumes
you
are
using,
like
maybe
for
running
a
separate
volume
for
your
darker
darker
volume
is
separate,
or
something
else
that,
for
example,
of
in
ship
transient,
then
it's
useful
to
be
able
to
override
that
limit
so
that
the
maximum
limit
is
actually
lower
than
what
was
reported.
So
its
user
should
be
able
to
like
like
not
use
it,
but
admin
should
be
able
to
configure
that
limit
and
when
they
install
the
driver
on
the
node.
A
In
general,
my
feedback
tends
to
be:
let's
avoid
adding
any
new
knobs
parameters
to
expose
to
end-users
in
general.
We
should
try
to
automatically
do
the
right
thing,
but
I
realized
in
some
cases
we
might
not
be
able
to
do
that,
and
that
might
be
a
requirement
that
we
should
be
very
careful
when
we,
when
we
do
that.
A
A
G
A
A
A
A
C
A
A
A
A
A
Had
a
couple
of
PRS
already
merged,
one
was
clarification
PR
so
that
it
didn't
apply
to
and
then
a
second
was
updating
the
spec
build
process
so
that
didn't
apply
either.
So
this
is
kind
of
a
wait-and-see
until
we
have
a
feature
that
it's
going
to
need.
This
next
item
is
for
CSI
for
Windows,
the
storage
proxy
last
status
was
the
cap
was
merged
and
repo
was
created
deep.
Any
updates
on
that.
Yes,.
B
I,
have
the
entry
and
there's
been
a
couple
of
reviews
and
to
the
process
and
the
CSI
proxy,
like
an
initial
version
of
the
G
RPC
API
between
the
plugins
and
the
proxy
has
been
submitted.
So
that's
out
for
review
and
another
update
is
Jane
is
trying
to
create
a
work
group
around
this
as
well.
A
lot
of
people
might
be
interested
so.
G
G
G
We
had
a
couple
runs
with
with
the
team
already
we
need
to
make
some
changes
and
that
will
be
a
whole
bunch
of
code
change,
because
we
are
renaming
some
of
the
wearables
be
moving
in
some
of
the
fields
moving
some
field
from
the
one
in
snapshots
of
worms,
natural
content,
I'm
working
on
this
gene
shin
has
been
continuing
and
working
on
separating
the
controller
out.
Unfortunately,
this
piece
also
has
a
strong
dependency
on
the
pipes.
G
Toto
change,
so
I'll
go
for
probably
this
week
and
next
week
is
try
to
get
card
slot
okay
chip
in
and
then
we
can
finish
the
controller
piece
and
the
third
piece
is
the
end-to-end
test.
Unfortunately,
there's
no
one
working
on
this
activity.
If
anyone
wants
to
contribute,
please
feel
free,
and
this
is
basically
to
make
any
message.
Great
changes.
G
After
we
separated
controller
out
the
deploy
in
mode
deployment
model
needs
to
be
changed
and
the
first
piece,
the
first
major
piece
will
be
up:
upgrading
updating
all
the
command,
all
the
comments
and
updating
all
the
document
in
open
areas,
including
the
webpage.
This
is
also
another
easy
work
as
well.
It
also
depends
on
the
type
of
code
and
the
last
tip
are
not
lists.
G
There
will
be,
they
will
be
changes
in
external
probationer,
maybe
in
other
controllers
as
well
to
adapt
all
the
type
style
changes
so
that
it
doesn't
break
so
easy.
There's
a
whole
bunch
of
work
over
there
so
far
would
be
help
in
focusing
on
one,
because
those
are
the
most
heavy
lifting
pieces
and
three.
We
don't
have
anyone
working
on
that.
Unfortunately,
at
this
point,
yeah
other
than
that
I'm
also
working
on
having
a
design
talk,
that
table
can
be
beneficial
to
the
community.
A
G
A
All
right
all
right,
thank
you
so
much
for
that
update
Shawn.
This
is
very
ambitious
and
for
folks
on
the
call
who
are
very
interested
in
snapshots,
there
is
help
needed
here
to
move
this
to
beta.
If
we
don't
get
help
it
may
slip.
So,
if
you're
interested
in
helping
move
this
feature
along
quickly,
because
you
have
some
sort
of
vested
interest
now
might
be
the
time
to
step
up
and
help
out
here.
Shawn,
Jiang
and
Shang
would
be
happy
to
onboard
you
and
kind
of
point
you
where
you
can
help
out.