►
From YouTube: Kubernetes SIG Storage - Bi-Weekly Meeting 20210520
Description
Kubernetes Storage Special-Interest-Group (SIG) Bi-Weekly Meeting - 20 May 2021
Meeting Notes/Agenda: -
Find out more about the Storage SIG here: https://github.com/kubernetes/community/tree/master/sig-storage
Moderator: Xing Yang (VMware)
A
This
is
the
kubernetes
storage
sick
meeting
today
we're
going
to
go
through
our
1.22
planning
spreadsheet
so
last
week
last
thursday
was
the
enhancement
freeze,
so
we
will
go,
go
through
the
spreadsheet
and
see
which
cap
made
it
which
didn't
and
the
next
deadline
is
code.
Freeze,
that's
coming
in
july
july,
8th
and
and
also
I
see
that
seek
release
has
opened
up
this
spreadsheet
for
future
blog.
A
B
Yeah
I'm
here
yeah
the
cap
is
mars,
is
being
tracked,
we're
still
blocked
on
csi
spec
change.
I
spoke
with
saad
a
little
bit
offline.
Then
I
spoke
with
deep
yesterday.
A
Can
you
speak
louder?
I
don't
know
if
it's
because
of
my
background
noise.
B
Right,
sorry
yeah,
so
I
the
the
cap
got
merged,
it's
being
checked
for
122,
and
but
the
implementation
is
still
blocked
on
the
csi
spec
change.
I
spoke
with
saad
a
little
bit
offline
and
I
spoke
with
deep
yesterday
in
in
great
detail
about
how
it
will
work
in
windows
possibly,
and
he
mentioned
that
the
in
windows
there's
equivalent
sids
and
you
can
use
set
acl
commands
to
lock
down
volumes.
B
Although
right
now
in
windows,
we
are
not
using
the
group
membership
for
anything
actually,
so
everything
runs
with
run
as
user
and
other
cases
like
yeah.
So
basically
like
he
says,
yeah
the
using
the
applying
the
the
sublime
gid
windows
drivers
could
use
it
in
future
if
if
they
implement
it
for
immediate
use
case,
obviously
the
use
case
is
pretty
clear
what
we
want
for
zero
file,
but
yeah.
C
Yep
I'll
take
another
look
at
that
csi
pr,
thanks
for
the
for
the
offline
conversation.
A
Thank
you
and
the
next
one
is
okay,
this
this
next
one
is
a
tracking
there's
a
copy,
a
lot
of
expansion,
one.
B
E
B
B
So
I
reached
out
to
like
api
reviewers,
because
copying
two
pvs
were
and
then
like,
ignoring
whatever
is
in
storage
class
will
is
kind
of
a
behavior
change.
So
what
is
their
guidances
and
I
haven't
heard,
but
it
was
like
from
them
actually,
since
I
reached
out
and
then
also
like,
we
spoke
whether
the
copying
allow
volume
expansion
to
to
pv.
B
If
it
is
a
blocking
item
for
resizing
going
g
or
not
so
I
think
so
far,
the
consensus
was
it
should
not
be
blocking
for
resizing
going
ga
but
yeah,
that's
the
just
so
far,
so
we
may
be
just
making
design
on
the
low
volume
expansion
copy
to
to
pv
in
this
quarter.
We
may
not
actually
do
any
implementation.
B
A
So,
okay,
so
this
one
will
just
should
we
change
the
two
design
then,
but
maybe
if
it's
still
beta
though
so
maybe
it's
still
keeping
yeah
yeah.
F
A
B
This
this
got
merged
and
yeah.
It's
big
track,
we'll
work
on
implementation,
I'll
split
the
cards
and.
A
Next
one
is
a
skill.
Linux,
recursive
mission,
handling,
okay,
says
design.
F
A
A
A
A
Okay,
assassin's
erase
okay,
something
really
got
rewarded.
Is
this
still
kind
of
a
working
progress?
Maybe
looks
like?
Does
anyone
know
any
anything
about
this?
A
G
A
A
Okay,
thank
you,
so
next
one
spreading
over
failure
domains.
So
this
one
is
dependent
on
the
next
item.
What
in
group
api?
So
I
will
need
to
update
the
cap
and
then
schedule
a
real
meeting
again.
A
B
What
was
the
card?
Sorry.
A
This
is
see
the
driver
out
of
three
move
ice
castle
driver.
H
Michelle,
mr
pr,
this
week,
we
are
seeing
builds
of
this
happen
automatically
on
staging.
I
think
what
we
need
to
do
next
is
attempt
to
promote
one
of
these
builds,
but
I
think
automatic
builds
are
already
configured
for
this,
so
we've
got
it
added
to
the
six
storage
and
kubernetes
case
that
I-
and
we
just
interpret
images.
G
I've
also
seen
humble,
has
been
doing
making
a
lot
of
prs
to
the
repo,
and
so
I
think
we
might
want
to
get
all
those
pr's
in
before
we
cut
a
release.
G
E
A
Yeah,
so
if
anyone
is
looking
for
some
work
to
do,
this
is
a
one
one
item
that
we
are
looking
for:
new
owner
yeah.
So
you
can
let
one
of
the
secrets
know,
or
you
can
also
reach
out
to
christian.
B
There
was
another
effort
by
someone
else
to
actually
open
a
different
implementation
or
different
version.
Isn't
it
christian.
H
E
E
Yeah
I
I've
commented
on
sir
cape
a
different
approach
of
transfer.
It's
almost
the
same
to
originally
proposed
by
john
griffiths.
A
A
Okay
and
then
your
your
suggestion
is
on
the
cap
and
the
cab
review.
A
A
A
A
I
think
we're
looking
at
how
to
enhance
scheduling
and
using
this
health
field
and
and
then
I
also
got
some
requests
to
expose
this
metrics.
Just
to
you
know
not
not
just
in
the
events,
but
just
like
other
volume,
stats
expose
them
in
through
a
prometheus.
So
I
think
that's
another
thing
we
can
look
into,
I'm
not
sure
if
it
makes
sense
to
have
it
both
in
prometheus
and
in
events,
but
I
think
we
can
look
into
that.
So
there
are
several
different
directions.
J
Yeah,
so
this
this
one,
the
the
cap,
was
merged
last
week
by
the
feature
freeze
or
the
enhancements
freeze,
but
after
making
a
pretty
significant
api
design
change,
which
will
require
this
to
stay
in
alpha
for
the
coming
release.
We
discussed
this
in
our
tuesday
volume
populator
meeting
and
in
yesterday's
data
protection
working
group
meeting.
We
sort
of
went
into
detail
on
what
the
exact
plan
is.
So
I
won't
recap
it
here
unless
you
guys
are
interested,
but
the
the
short
short
version
is
we're.
D
J
So
yeah
tim
tim's
response
to
the
cap
was
that
there's
a
lot
of
stuff
in
there
that,
like
isn't
relevant
to
kubernetes
at
all,
and
I
think
his
his
hope
was
that,
like
most
of
the
cozy
reaching
alpha,
work
could
be
done
entirely
out
of
tree
and
didn't
need
a
cap
at
all
to
do
that,
and
then
he
proposed
that
we
write
a
cap
just
for
the
parts
that
actually
integrate
with
kubernetes
proper
so
like
when
we're
ready
to
make
the
cubelet
side
changes
in
the
the
you
know.
J
A
J
A
A
Yeah,
we
still
need
to
get
his
api
review
done
for
this
one
to
be.
You
know
if
we
want
to
call
this
a
kubernetes
feature,
so
we
still
need
to
get
the
teams
yeah.
C
We
should
clarify
exactly
what
he
wants
in
the
spec
versus
what
he
doesn't
want.
A
It's
basically
it's
tracked.
Oh
no!
Actually
it's
yeah.
It
is
a
auto
tree,
it's
tracked,
but
out
of
three.
So
that's
what
the
that's!
The
category.
J
A
Okay,
so
next
one
is
a
change
block
tracking.
I
don't
think
we
have
any
update
on
this,
we'll
get
back
to
this
or
stupid
design.
Next,
one
is
a
new
rewrite.
Only
access
mode
chris.
K
Hi
search
on
the
unmute
button:
yes,
the
cap
is
merged
and
right
now
it's
going
through
review
for
the
csi
spec
sidecars
and
kubernetes
changes.
A
Okay,
so
next
one
is
see
the
proxy
for
windows.
There's
a
jing
or
deep
here.
L
Yeah
hey
so
for
this
one.
Last
week
we
managed
to
merge
all
the
changes
that
the
prr
populated
from
jing
and
michelle
had
a
lot
of
great
feedback
on
the
api
before
we
went
to
ga.
So
that's
basically
in
the
that's
reflected
in
the
cap
and
now
in
the
process
of
getting
implemented
in
a
backward,
compatible
way.
A
Thank
you
yeah,
so
this
one
is
the.
As
I
said,
this
is
the
same
solution
as
the
I
shouldn't
say
the
same
situation,
but
this
is
the
same
category.
This
is
like
tracked
by
auto
tree
similar
as
a
cozy.
That's,
this
is
actually
the
example
referenced
by
a
sick
release.
M
Yeah,
so
for
sesame
migration,
I
think
there
is
one
bug
around
the
volume
attachment
garbage
collection.
So
currently,
there's
already
a
fakes
out.
I'm
gonna
take
a
look
other
than
that.
I
think
there's
no
like
there
are
still
some
small
issues.
I
think
there
are
no
major
problems
around
that.
M
M
Oh,
it's
called
coal
bite.
M
A
M
The
next
the
next
step
is
to
send
out
another
pr
to
update
our
kubernetes
website.
So
basically,.
A
M
Yeah
actually
flocker,
it's
already
like
their
company
is
like
not
running
anymore.
So
it's
just
like
we
don't
we're,
not
actually
officially
deprecate
this
so
we're
deprecating
this
and
for
storing
os
and
quote
byte.
We
already
confirmed
that
there
have
been
tenders
that
they
don't
want
to
support
csi
migration
and
they
I
don't.
M
They
don't
think,
there's
like
active
entry
users,
so
we
can
deprecate
those
okay,
yeah
and
and,
in
addition
to
this,
there's
also
another
a
scale
I
o
this
driver
has
been
deprecated
in
1.16
and
in
this
release,
we're
remove.
We
already
already
removed
this
plugin
from
our
code
base,
so
sky
io
is
not
supported
anymore.
A
A
Okay,
next
one
says
migration
vsphere,
so
I
checked
with
deviant
he
about
the
nfs,
so
he
said
I
thought
I
added
it:
okay
yeah!
So
basically
he
said
that
fc
does
not
support
nfs
before
data
store.
We
do
have
a
plan
to
fix
this,
but
right
now
we
don't
have
a
timeline.
Yet
so
that's
that's
about
the
nfs
part.
G
I
think
it's
still
going
to
remain
in
beta,
okay,
I'm
not
sure
if
there's
any
if
they
plan
to
turn
it
on
by
default.
Jawway.
Do
you.
M
Know
I
need
to
check
check
the
document.
We
have
a
csm
migration
meeting
tomorrow,
I'll
go
through
the
the
timeline
there
again.
I-
and
I
also
need
to
reach
out
to
andy
again,
to
see
if
there's
any
any
planning
changes.
G
And
gce,
I
think,
azure
file
you
can
also
uncross
out.
I
think
azure.
A
A
G
N
Yeah,
this
is
continuing.
We
actually
found
some
interesting
performance
regressions
around
how
the
csi
sidecars.
N
E
N
As
mentioned
last
time,
we're
going
to
keep
it
as
beta,
because
so
people
have
the
possibility
to
switch
it
off
if
necessary.
A
The
next
one
is
aws
ws
matt,
I
don't
know
matt
is
here.
Does
anyone
know
the
status
for
this
sad
michelle.
G
F
A
G
A
K
A
A
I
think
leila
has
been
working
on
this
for
other
drivers
right.
So
I
think.
A
Lily
has
been
working
on
this
for
other
drivers,
so
I
just
checked
that
joey
was
checking
with
me
the
other
day
I
asked
tv
and
even
says
he's
going
to
submit
a
pr
for
this
yeah.
A
Okay.
Next
one
is
always
owner,
reclaim
policy,
so
this
one
didn't
make
it.
The
cap
didn't
got
merged,
so
I
so
deepak
is
still
looking
at
this
and
trying
to
address.
There
are
some
comments
from
jan
so
he's
just
trying
to
address
this,
so
this
is
a
move
to
your
1.23,
so
we're
doing
design
the
next
one
is
a
control,
volume,
mode
conversion
between
source
and
target
pvc.
A
So
I
need
to
sync
up
this
junction
and
come
up
with
some
design
on
this.
So
right
now
we
don't
have
anything
yet
and
next
one
is
a
secret
production.
E
I
was
originally
thinking
that
it
is
only
for
secret,
but
there
might
be
a
similar
requirement
for
conflict
maps
or
other
resources,
and
also
we
we
might
need
to
think
of
as
a
generic
way
to
protect
some
resource
from
duration.
A
Okay,
thank
you
so
this
one
we
so
probably
okay.
So
it's
going
to
move
to
23,
then
right.
I
think
it's
need
some
time
more
time.
E
F
A
Oh,
but
then,
but
this
one
we
will
need
to
request
for
exception
right.
So
yeah.
E
A
Are
you
planning
to
talk
to
a
ap
machinery
because
that
needs
to?
If
you
want
to
so
you
want
to
try
1.2,
then
you
need
to
have
this
discussion
soon
get
us
resolved
because
otherwise
I'll
be
late
for
the
exception.
This
is
already.
E
A
A
A
M
So
there
is
a
crap
for
this,
but
I
think
humong
has
some
comments
and
concerns
and
ambassador,
I
think
maybe
he
might
be
busy
and
haven't
replied
yet
think
I'll
sync
with
him
on
slack
for
this,
I
don't
think
this
is
going
to
make
make
it
to
the
1.2
though,
but
the
design
might
be
able
to
merge.
A
A
And
okay,
so
next
one
is
now
grease
for
no
shutdown.
So
we
talked
about
this
one
last
time
that
we're
going
to
do
our
prototyping
we're
trying
to
get
the
cab
merge
as
provisional.
So
I
have
updated
the
cap
michelle
if
you
have
a
time
if
I
can
take
a
look,
but
I'm
not
sure
I
need
to
check
with
the
secret
list
and
see
if
they
still
allow
us
to
get
a
cup
merged
as
provisional,
because
they
have
all
these
new
requirements.
A
You
have
to
have
to
specify
a
stage
as
alpha
beta
or
jia.
You
can't
specify
anything
else
or
leave
it
blank.
So
so
I
actually
suspected
that
the
ci
will
not.
Let
me
pass
if
I,
if
I
don't
like
finish
the
all
the
other
things
so
so
I
need
to
check
with
them
about
the
next
one
is
to
enable
user
namespace
in
cubelet.
A
Oh
okay,
so
I
think
this
is
the
one
that
they
are
requesting
an
exception,
but
I
think
you
are
looking
at
this
and
you
have
some
comments
on
this
right.
Let's
do
some
concerns
here.
B
Yeah,
I
think
the
the
address
the
concern,
so
oh,
okay,
director
lgtm,
then
approved
it.
I
don't
know
if,
like
yeah,
if
you
want
to
go
ahead,
we
can
go
ahead
and
give
the
exception
thing.
It's
from
story's.
A
F
F
A
B
A
N
A
G
A
And
the
next
one:
okay
warning
expansion
for
staple
set
yeah,
so
my
co-worker
celini
is
looking
into
this.
So
she
said
she's
working
on
a
cap.
So,
let's
see
if
we
can
give
a
update
next
time.
A
And
next
one
is
content,
notifier,
so
yeah,
so
team
actually
has
approved
us
from
the
api
reviewer
side.
We
are
waiting
for
signaled
to
review
this,
so
we
didn't
make
it
into
the
we're
not
trying
to
cut
much
deadline.
So
we
are
so.
This
is
still
design,
but
we're
trying
to
get
cap
merged
early
for
1.23.
A
The
next
one
is
kubernetes
utos
monk
split
into
a
new
review.
A
D
There
is
a
notice
pr
that
we
put
it
out
on
the
old
repo
that
is
merged,
but
there
is
another
pr
on
the
case
that
requires
approval.
I
already
got
an
lgtm
once
it
is
done.
I
think
I
am
pretty
sure
that
it's
it's
the
last
pr,
so
I'm
just
bringing
the
reviewers
together
approval.
That's
all.
A
Next
one
is,
this:
is
a
prioritization
and
voting
capacity?
Are
we
doing
anything
for
the
so
michelle
in
this
release?
G
A
G
Being
targeted
for
ga
and
the
cap
has
been
approved.
A
All
right,
thank
you.
Okay,
that's
all
we
have
in
this
spreadsheet
yeah,
so
we
also
have
this
small
dock
here.
Just
this
is
a
this
just
other
enhancements.
We
are
targeting
and
we're
not
22
release.
A
A
A
Thank
you,
okay,
so
I
think
that's
all
we
have.
We
don't
have
other
issues.
Does
anyone
have
anything
else
you
want
to
discuss
here.