►
From YouTube: Kubernetes SIG Storage 20180215
Description
Kubernetes Storage Special-Interest-Group (SIG) Meeting - 15 February 2018
Meeting Notes/Agenda: https://docs.google.com/document/d/1-8KEG8AjAgKznS9NFm3qWqkGyCHmvU6HVl0sk5hwoAE/edit#heading=h.bgrmir7r9zs7
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
welcome
this
is
the
kubernetes
storage
special
interest
group
meeting
today
is
February
15
2018.
Let's
go
to
the
agenda
and
get
started
so
today
we're
going
to
go
through
the
work
items
that
were
planning
for
this
quarter.
If
you
have
any
design
reviews
that
need
to
be
looked
at,
please
post
them
in
the
agenda
doc
and
if
you
have
any
PRS
that
need
to
be
looked
at
that
are
not
getting
attention.
A
You
can
also
post
them
in
this
dock
to
bring
attention
to
them
and
then
Muhammad
from
IBM
has
an
announcement
that
he'd
like
to
make
and
we'll
finish
off
with
Aaron,
given
an
update
on
the
onboarding
to
storage,
one
off
meeting
that
we're
going
to
do
alright.
So,
let's
go
to
the
planning
spreadsheet
first
off.
Is
generic
storage
topology
solution
that
works
well
with
CSI
and
local
storage
Michelle?
Are
you
online.
B
B
The
part
that
is
approved
is
the
topology
specification
for
persistent
volumes.
This
is
for
the
static
static,
Lee
created,
persistent
volumes
that
part
is
approved
and
beta
API
is
also
out
and
final
review.
The
part
that's
still
pending
is
the
dynamic
provisioning
design
which
is
I'm
working
on
right
now.
Okay,.
A
B
A
A
C
So
I'm
shelling
I
were
able
to
go
to
the
container
identity
workgroup
to
clarify
the
direction
which
the
one
they
would
like
to
go
with
her
pod
identity,
and
there
sounds
like
the
consensus
is
with
more
and
more
use
cases
showing
up.
They
would
like
to
eventually
have
completely
to
do
this,
and
so
with
with
that,
where
again
we
can
just
keep
the
Sonia
as
it
is
today,
with
the
demon
set
without
and
make
sure
a
centralized
component,
and
when
that's
available
we
can
modify.
C
A
You
next
up
is
the
CSI
volume
implementation.
We
have
a
separate
meeting
and
doc
that
we
keep
track
of
detailed
status.
The
important
bits
are
that
the
core
API
has
been
moved
to
beta
and
there
are
I
think
one
other
big
item
that
I'd
like
to
get
in
for
beta,
which
is
moving
the
volume
attributes
to
first
class.
That's
still
in
progress
and
then
there's
a
handful
of
extra
features
that
I'd
like
to
add
things
like
credentials
device
mount
device
calls
these
require
changes
in
the
CSI
spec
itself.
Some
of
these
changes
have
gone
in.
A
Some
of
them
have
not
so
considering
code
freeze
for
kubernetes
entry
is
February
26,
just
about
a
little
more
than
a
week
away.
We
may
or
may
not
get
to
all
of
these,
but
the
hope
is
that
we'll
be
able
to
move
the
core
at
least
into
beta,
so
that
folks
can
start
creating
drivers,
and
then
we
can
continue
to
add
features.
On
top
of
that.
A
D
A
Okay,
next
up
is
block
volume,
support
the
tasks
here
were
adding
additional
volume,
plugins
and
adding
more
tests,
and
we
broke
out
the
volume,
plugins
and
additional
work
that
needed
to
be
needed
to
happen.
The
volume
refactor
I
took
a
look
at
this
week
and
a
prude
that's
a
hero
that
looks
good
to
me.
A
E
A
E
A
C
A
A
A
F
A
A
Okay,
I
think
I
can
give
an
update
on
Jing's
behalf
I
believe
the
the
PR
for
this
was
sent
out
and
it
was
awaiting
review.
G
A
A
A
I
C
A
B
I
think
Ian
can't
make
the
meeting
today,
but
he
told
me
that
this
is
in
progress
and
there
should
be
a
PR
out
by
next
week.
Okay,.
A
A
A
Cool
so
as
a
reminder
code
freeze
is
coming
up:
February
26
there
is
going
to
be
a
code
slush
that
goes
in
a
week
before
that
I
believe
Monday,
the
22nd
the
purpose
of
code
slush
is
that
only
feature
feature
related
work
will
allow
be
allowed
to
merge,
so
just
things
like
random
reef
actors
will
no
longer
be
accepted.
This
is
to
kind
of
remove
the
noise
from
the
merge
queue
and
your
feature
should
still
be
able
to
get
in
until
February
26.
A
A
A
A
H
So,
basically,
the
conference
is
just
a
gathering
for
developers
working
on
micro
services.
Kubernetes
is
geo,
blockchain,
surrealists,
ai
and
other
things,
so
there
will
be
like
different
keynotes
from
from
different
companies
and
and
talking
about
different
different
items
in
the
end,
the
conference,
and
so,
if
you're
kind
of
interested
yeah
the
day
that
you
yo
are
you
open.
Sad
I
should
be
a
code
that
you
can
use
to
register
and
it
is
kind
of
full
pass
for
the
for
all
in
the
conference.
H
So
if
you
are
interested
I,
just
add
your
name
there
now
for
logistics
and
into
the
registration,
and
we
can
discuss
about
the
at
the
agenda.
So,
for
starters,
as
discussed,
we
saw
the
simple
agenda
is
just
to
get
to
know
each
other
and
to
do
some
saw
some
work
there,
like
bug,
triage
and
and
so
on.
So.
A
I
wanted
to
make
it
clear
that
this
is
not
a
official
cig
face-to-face
meeting.
We
didn't
have
enough
time
to
plan
something
like
that
and
we
don't
want
folks
to
be
excluded.
Who
can't
make
it
to
this
to
this
event,
so
we're
calling
this
admit
event
to
meet
up.
We
want
to
do
work
here
that
you
know
folks
aren't
going
to
miss
out
on
second
comment.
Mohammed,
could
you
make
this
document
share
it
with
the
sig
storage?
Yes
looks
like
we
don't
have
permission
to
edit.
Oh
okay,
sorry.
H
A
I
Did
she
no
she's
there?
Well,
I
can
tell
you
that
at
least
Aaron
and
I
did
meet
and
we
created
a
kind
of
an
outline
of
a
document
of
what
we
call
almost
like
a
one-on-one
or
two
classes
that
we
plan
to
share
with
the
rest
of
the
team.
We
have
a
I,
don't
know
if
she
shared
that
noona,
but
we
should
share
it
soon
and
what
we
plan
to
do
is
that
each
of
these
are
about
five
to
ten
minutes
max.
I
We
want
them
to
be
short,
we
want
to
be
clear
and
we
want
it
to
be
efficient,
small
meetings,
so
we
will
be
sending
out
this
document
out
be
approaching
a
certain
number
of
people
to
see
who
can
bound
here
to
these
classes.
Sorry
not
classes
small
presentations,
and
we
can
be
as
simple
as
no
slides.
You
know
something
on
command
line
or
just
a
few,
so
there
you
are.
I
E
I
you've
covered
it
well,
Luis
I,
don't
know
that
everything
more
to
offer,
but
we
didn't
want
it
to
be
a
burden
on
the
volunteers,
doesn't
mean
we
don't
want
the
content
to
be.
You
know,
helpful
I,
think
it's
important.
We
give
back
to
the
community
and
help
more
people
on
board,
so
I
hope
everyone
you
know,
considers
it
giving
back
and
getting
more
people
on
board
and
quicker
and
as.
E
Doesn't
have
to
be
slides,
what
we'll
do
is
we'll
put
it
on
the
sig
storage
calendar,
so
people
can
attend
to
the
recording
that
way.
We
could
include
any
questions
that
come
up
because
I
think
it's
always
helpful
to
have
those
as
part
of
the
recording,
but
we're
not
gonna.
Do
it
during
this
normally
scheduled
a
cig
meeting
time.
I.
Just
don't
think
we
have
time
for
that.
J
E
Yeah
I
think
we're
flexible.
However,
the
presenter
wants
to
volunteer
and
do
it
that's
fine
if
they
just
want
to
contribute.
The
content
is
a
pre-recorded
video,
totally
fine
with
that
we
just
weren't
gonna
open
it
up
in
case.
We
also
wanted
to
capture
questions
around
it,
but
if
you're
gonna
volunteer
I'll,
let
you
do
it.
However,
you
want
and.