►
Description
Meeting of Kubernetes Storage Special-Interest-Group (SIG) Workgroup for Container-Storage-Interface (CSI) Implementation - 11 March 2019
Meeting Notes/Agenda: -
Find out more about the Storage SIG here: https://github.com/kubernetes/community/tree/master/sig-storage
Moderator: Michelle Au (Google)
A
All
right
today
is
Monday
March,
11th
2019,
and
this
is
the
kubernetes
CSI
implementation
meeting.
Let's
jump
straight
into
114
items
so
looks
like
the
issue
with
reconstruction
of
CSI
volumes
has
just
merged
a
few
minutes
ago.
So
we'll
continue
to
monitor
this
and
watch
if
it
makes
if
it
fixes
the
flaky
tests.
B
Okay,
yeah,
so
I'm
still
nervous
some
été
test
error
that
I
am
working
on
I
think
he
said:
I
need
to
set
that
see
as
a
driver
history
in
the
cupola
device,
I'm
working
on
that
right
now,
just
running
the
test
locally,
and
so
some
still
working
on
that.
Okay,
great
so
the
test.
If
a
do
you
think
it's
because
of
their
eyes,
I
think
because
the
cupola
is
not
getting.
This
information
is
not
getting.
This
parameter
set
yeah.
B
C
A
B
B
B
So,
okay,
yeah
I,
will
take
a
look
and
yeah
I.
Think
it's
just
a
not
it's
a
yes
something's,
not
not
past.
Just
it
was
due
so
yeah.
Well,
okay,.
B
A
All
right,
so
the
other
thing
that
I'm
trying
to
work
on
now
is
to
update
all
the
side,
cars
to
use
the
new
beta
objects
and
so
I've
already
merged.
The
cluster
driver.
Registrar
changes,
I'm
working
on
the
external
provisioner
changes,
but
before
I
can
do
that,
I
need
to
also
update
the
snapshot
ER
because
snapshot
or
the
external
provisioner
has
dependencies
on
the
snapshot
or
so
that
was
something
I
wanted
to
discuss
here,
because
I
think
she
you
had
some
concerns
about
updating
the
or
removing
the
the
constraints
on
the
CEO.
B
A
Main
thing
with,
like
external
snapshot,
her
or
the
main
thing
in
general,
what
I
see
is
like
with
all
the
side
cars
is.
We
depend
on
some
version.
We
depend
on
some
minimum
version
of
kubernetes,
so
I
think
the
the
main
thing
with
what
this
current
constraint
does.
Is.
It
sets
a
constraint
on
the
maximum
version
of
kubernetes,
so
I
think
by
removing
it,
then
we
can
at
least
keep
we
can
handle
upgrading
without
having
to
always
update
the
constraint
every
time
I.
B
D
D
B
B
A
B
Thank
you
for
just
attitudes
like
this
right
is
a
Russian
equal
to
it's
still
what
go
up
her
than
this
one
so
like
it
could
go
to
one
13.1
or
something
I,
don't
think
it
hasn't
happened
to.
It
happened
to
me
and
then
I
have
to
add
a
equal
sign
next
June
colbern
eighties,
when
I
said
he
not
doing
so
completely.
A
A
A
A
A
B
B
D
B
D
Have
tests
and
that's
why
we
don't
update
dependencies
unless
we
know,
but
we
want
to
update
basic
there's
a
slight
confusion
here
between
locking
onto
a
specific
version
via
the
log
file
and
locking
onto
specific
versions
via
the
Tamil
file.
The
Tamil
file
is
basically
a
logical
constrains.
My
code
doesn't
work
unless
it
meets
these
constraints
and
the
other
file
is
documenting,
which
version
is
supposed
to
be
used
at
the
moment,
and
Deb
will
stay
to
that
second
version.
Unless
you
explicitly
tell
it
to
update.
A
A
B
D
Connect
well,
if
that
particular
package
is
API,
compatible,
I,
guess
it.
It
won't
hurt
too
much
but
I
in
the
past,
I've
seen
breakages
that
exactly
came
from
mixing
kubernetes
packages
from
different
releases.
So
it's
not.
Actually
you
are
you're,
basically,
assuming
that
the
API
will
stay,
but
it
will
be
will
be
compatible.
Even
if
we
go
to
master
and
my
experience-
that's
not
currently
guaranteed
by
the
Q&A.
His
API
lie
packages
they
are.
They
are
only
compatible
with
in
a
certain
release
number
in
a
release
branch,
but
not
necessarily
across
releases.
A
Okay,
I
think
that
makes
sense,
then
I
guess
in
order
to
proceed
with
this.
What
I
need
to
do
is
to
add
instead
of
using
cuz.
The
version
I
want
is
not
tagged.
So
what
I
need
to
do
is
put
a
very
specific
commit
here
and
sync
up
all
of
these
to
the
specific
commits,
which
version
do
you
need
I
know
it's
a
114.
A
E
B
D
A
D
Might
be
a
bit
more
complex
if
you
add
packages
that
have
new
dependencies
and
cases
vet
triggers
an
update
for
some
it
may
it
may
trigger
an
update
to
some
packages,
but
usually,
if
you
just
add
a
new
package,
it
doesn't
so
it's
somewhere
between
those
two
things
that
actually
happens.
A
Okay,
so
to
move
forward
with
this
I
think
the
best
option
we
can
do
right
now
is
to
add
the
constraint
to
a
release
branch
and
get
the
latest
releases.
I
still
feel
like.
For
the
most
part,
we
shouldn't
even
have
to
have
restrict
constraints,
because
that
means
every
single
kubernetes
release.
We
have
to
go
and
update
this
again
update,
remove
the
constraints
and
we're
going
to
still
have
this
dependency
chain
from
external
provision
or
to
external
snapshot.
Er.
B
A
A
B
A
B
Another
around
assist
I
know:
Anju
is
working
on
the
leader
in
action.
So
talking
about
you
know
it's
kind
of
difficult
to
make
all
the
dependency
right.
Do
we
really
want
you
to
do
that
or
we
energy
brought
it
up
about
that?
So
basically
we'll
add
in
the
dependencies.
You
know.
If
you
move
this
election,
don't
you
and
then
everybody
will
be
dependent
on
that,
so
they'll
be
yeah.
A
A
A
B
F
F
I
was
trying
to
build
external
provisioner
I,
pretty
much
ran
into
the
conflicts
exactly
that
Michelle
ran
into
because
the
provision
it
depends
on
the
snapshot.
But
the
thing
is
for
CSI
migration.
We
need
thing
from
the
API.
It's
basically
I
think
a
label
that
says
what's
the
what's
the
standard
name
for
zone
parameters
and
that
got
staged
into
a
specific
file
as
part
of
the
API
staging.
F
A
B
A
C
A
G
B
B
A
B
B
Kubernetes
api
does
that's
fine,
because
they
are
actually
also
entry,
and
then
you
build
them
together
and
they
you
test
them
together,
and
then
you
publish,
publish
that
separately.
I
think
that
would
be
fine,
because
it's
actually
always
the
same
version
that
I
carry
and
the
kubernetes
that
you
know
the
core
communities
nate
guy
that
always
actually
had
the
same
version
they
released
actually
together.
G
B
G
B
Oh
I'm
sick.
What
I'm
saying
is
you
you
could
a
do
it
the
same
way
as
the
kubernetes
api
do
still
put
them
in
the
in
Bob.
At
the
there
is
always
a
so
usually
when
there
was
a
change
happens,
yuri-chan
the
change
happens
in
the
snapshot,
part
first
and
then
and
the
day
it
affects
the
the
parishioner.
The
only
time
I
see
that
it
happened
almost
at
the
same
time
was
because
Rosa
CSS
back
up
date.
That
was
the
only
time
that
we
would
have
to
don't
want
to
delay
the
permission.
G
G
B
I'm
just
saying
that
a
week
we
could
I
so
I'm,
not
against
saying
publish
that
in
a
different
place
like
what
we
did
with
kubernetes
api,
but
I
am
against
at
completely
removing
that
out
of
out
of
the
external
snapshot
of
people,
because
when
we
are
running
in
those
which
what
general
he
knows
fast,
the
informers
and
Lister's
you're
you're
doing
those
together.
The
controllers
of
article
always
together
so
stop
running
them
out
would
be
pretty
pretty
bizarre.
B
A
B
A
B
C
C
He
created
a
I
created
a
an
issue
to
follow
up
with
some
the
suggestions
that
Dave
Dave
had
on
the
on
the
merge
TR.
So
that's
what
I'm
working
on
now
and
I
heard
you
just
mentioned
the
documentation
so
for
is
the
internal
documentation
of
that
is
after
you
today,
no.
C
A
C
Yes,
the
that's
another
thing:
I'm
working
on
I
I
didn't
get
a
chance
to
do
it
Friday,
but
the
the
only
driver
that
I
have
is
from
from
Kevin.
So
that's
that's
what
I'm
using
to
test
it
so
I'll
report
findings
on
that.
So
I'll
I'll
move
that
as
far
as
a
priority
and
get
that
done
today
with
and
I
couldn't
work
on
the
the
other
stuff.
Later.
Oh,
the.
C
H
H
F
G
G
A
D
That's
my
next
step
to
actually
try
out
things
that
I've
been
testing
locally,
also
in
brow,
so
it
adds
a
periodic
job
which
are
tests
against
the
latest,
given
it
is
master
and
a
second
job
configuration
for
pool
requests
of
its
future
changes
to
our
components,
get
tested
with
a
stable
kubernetes
version
and
again
latest
master
of
kubernetes.
At
the
same
time,
before
merging
a
pull
request,
you
had
some
questions
on
that
I
think
I
answered,
so
you
might
have
never
look
on
the
pull
request.
Ok,
great.
H
D
E
Yes,
I'm
just
locked
on
to
PRS
I
think
they
both
have
merge
conflicts,
but
I
wanted
to
get
a
thumbs
up
on
the
period
before
I
go
ahead
and
resolve
those
I
think
for
the
leader
election.
One
I
was
just
waiting
for
the
114
beta
release,
which
I
think
is
out
now
so
I'll
update
that
to
use
beta
release
and
then
for
the
external
snap,
shutter
yeah
I
still
need
someone
to
just
look
at
it
and
make
sure
it's
good
to
go
before
I
serve
it.
Ok,.
E
B
E
B
H
A
One
alright
yeah
these
are:
these
are
not
in
any
huge
hurry
to
get
in
so
I
think.
That's
fine!
Alright,
thanks
for
the
updates,
I
think
we
don't
have
anybody
here
to
give
an
update
on
drivers
all
right
other
than
that
I
think
that's
all
we're
tracking
for
114!
Is
there
any
other
topics?
Anyone
wants
to
bring
up.