►
From YouTube: Kubernetes SIG Storage - Bi-Weekly Meeting 2022-05-12
Description
Kubernetes Storage Special-Interest-Group (SIG) Bi-Weekly Meeting - 12 May 2022
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
A
A
Okay!
So
let's
go
through
this,
so
I
just
copied
the
this
spreadsheet
from
1.24
to
1.25,
and
if
there
is
anything
else
you
want
to
add.
Please
add
it
here
as
well.
A
So
I'll
just
go
through
this
now
the
the
first
one
delegate
efforts
group
two
css
driver
instead
of
cubelet,
I
believe,
last
time
yeah.
So
we
did
not.
We
did
not
go
j
last
time,
but
we
do.
We
want
to
bow
this
to
ga
you
might
not
25,
who
is
see
who
is
working
on
this
child
was
working
on
this
before
is
chang
here
today.
A
Michelle
sad
come
on.
You
know
anything
about
this.
B
Yeah,
I
know
this
feature
was
beta
and
we
should
plan
to
move
it
to
ga.
By
the
same
time
like
we
have
been
talking
about
this
other
issue
that
I
opened
in
github
on
last
week.
I
think
let
me
link
it
in
the
chat.
Okay,
so
there's,
like
complication
associated
with,
I
guess
it's
orthogonal,
to
part
of
this
issue,
but
there's
another
item
that
I
would
like
to
add
is
like
the
upper
driver.
C
A
Obviously
you
are
saying
this
is
the
generous
thing
we
have
seen
this
one
a
lot
for
other
features
as
well.
Like
I
remember
at
least
the
volumes
is
one
thing
like
right,
depending
on
the
type
you
your
driver
may
or
may
not
support
it.
Something
like
that
right
is
that
the?
What
do
you
mean
so,
basically
it
could
be.
One
driver
could
be
supporting
different
capabilities
right.
Is
that
okay?
So
this
is
a
similar
issue?
Okay,
so
we
probably
okay.
So
we
probably
want
to
take
a
look
of
this
and
see.
A
B
Yeah,
so
I
don't
want
to
deviate
this
meeting
so,
okay,
I
want
to
keep.
We
should
try
and
get
the
fs2
thing
ga,
but
but
like
it
could
be
a
little
bit
tentative
at
this
point
in
time,
because
we
don't
want
to
if
you're
going
to
redo
the
whole
thing,
then
they
might
have
to.
D
A
D
E
You
can
mount
with
a
particular
fs
group
and
when
we
designed
that
feature
we
we
said
like
this
is
this
is
not
to
replace
the
stuff.
That's
in
cuba.
This
is
just
to
unbreak
samba
on
linux,
because
there's
no
way
to
get
it
to
work
other
than
this
right.
That
was
the
point
of
that
feature
yeah
and
then,
when
we
take
a
step
back
and
say
well,
we
have
a
bigger
problem
with
how
you
know
security
context
are
applied
to
individual
pods
with
regard
to
fs
groups,.
E
E
And
what
about
all
of
the
other
things
that
aren't
fs
groups
like
I
like
the
idea
of
of
starting
over
with
the
csi
driver,
object
and
maybe
saying
you
can
have
more
than
one
of
them
and
the
driver
will
tell
you
which
one
to
use
on
a
per
volume
basis,
maybe
or
or
you
know
something
some
new
idea
along
those
lines.
We
have
to
go
through
a
design
and
implementation
to
get
it
to
work.
B
Yeah
part
of
me
yeah,
I
that's
why
I
was
saying
it
could
be
considered
orthogonal.
So
let's
just
do
this
ga,
hopefully,
but
in
the
in
this
this
other
problem.
We
should,
if,
if
there
are
cases
where
it
would
prevent
like
it,
doesn't
it's
in
conflict
with,
like
the
new
design
that
we
can
come
come
to
solve?
This
issue
is
in
conflict
with
this
fs
group
to
csr
driver
somehow
that
we
should
probably
not
do
it,
but
but
I
don't
think
that
would
be
the
case.
I
think
these
two
can
go.
E
B
C
In
terms
of
assignees,
I
think
chang
will
not
be
able
to
take
this
forward,
so
we'll
need
a
new
person
so.
E
A
A
A
Okay,
so
let's
see
or
say,
design.
A
A
Okay,
now
this
one
we
can,
we
can
delete
this
one
now
right
online
offline
resizing.
Do
we
still
need
to
keep
this
for
some
time?
No,
I
think
we
can
mark
it
all
right,
great,
okay,
I'll,
just
delete
this
delete
recover
from
resize
failure,
so
this
one
we
will
bring
this
try
to
bring
this
one
to
beta.
A
And
what
just
started
yet,
let's
see
so
this
is
target
target.
A
A
And
issues
related
to
assuming
volumes
among
points.
This
is
a
bug
fix.
Okay,
so
we're
saying
movie
that
moves
to
1.25
is
g
in
here.
Yes,
okay,
so.
A
G
It's
kind
of
already
really
to
one
point.
A
A
All
right
delete
this
row,
all
right,
storage,
quite
checking,
so
I
think
we're
done
with
this
right.
It's
patrick
here.
This
is
ga,
so
I
think
we'll
probably
should
did
we
update
the
product?
A
A
Your
new
checklist,
I
know,
there's
a
one
pr
and
the
main
pr
got
a
merge.
I
believe
there's
another
one.
I
don't
know
I
need
to
check
and
and
okay
c
ephraim
jonathan,
so
we're
bringing
this
to
jay
right.
A
What
jonathan
is
not
here,
but
I
think
he
was
yesterday.
He
said
that
he's
going
to
bring
this
gta.
G
A
C
G
Right
so
the
target.
A
G
A
A
G
A
And
who
should
who
should
be
the
reviewer
for
this?
A
And
owning
group,
so
I'm
thinking
for
one
group,
I'm
thinking,
maybe
we
can
try
to
get
the
cap
merged
as
a
provisioner.
I
don't
know
if
they
still
allow
this
michelle
do
you
know,
can
we
still
have
a
cab
merge
as
provisional?
I
don't
know
if
they
made
any
changes
to
disallow.
That
does
it
have
to
be
something
I'm
not
sure.
Okay,
I'll
check,
let's
see
if.
A
A
So
and
see
it's
out
of
three
more
eyes
as
a
driver
right.
So
this
one.
A
C
I
saw
some
work
in
this
area.
I
think
it's,
it
might
be.
A
H
Yes,
I
think
we,
if
we
agree
to
just
user
across
namespace
snapshot
provision,
saying
we
can
remove
the
transfer
feature
but
yeah,
okay
yeah.
We.
E
A
But
that
will
be
different
right.
It's
a
this
is
we're
talking
about
snapshot
now,
you're
talking
about,
I
mean.
A
A
Is
done
so
this
one
this
one
we
won't
stay
in
design
or
you
wanna
try
alpha
or.
A
A
Okay,
thank
you
and
okay.
Next
one
sees
everyone
in
house
additional
matrix.
So
yes,
it's
alpha,
so
we
could
try.
We
could
try
beta
this
time,
we'll
see
not
started
yet.
Try.
A
Oh
this
one,
okay,
this
is
weird
look
at
this
special
field.
All
right,
we'll
try,
try
beta.
A
And
and
this
next
one,
the
wooden
house,
programmatic
response
nick
says
he
actually
does
not
have
time
to
work
on
this,
so
I
actually
is
gonna
check
with
run,
which
I
have
not
got
a
response
yet
so
right
now,
I'm
not
sure
so
still
need
to
go
check.
A
Rewarding
populator
so
ben
talked
about
this
one
yesterday,
so
you
think
this
is
a
little.
A
Yeah
probably
makes
sense
for
yeah
one
more
release
all
right
and
yeah
cozy.
I
don't
know
that
this
one
will
try
to
bring
you
off.
I
think
it's
getting
close.
So,
let's
cut
soothing.
A
A
So
hopefully
we
can
get
it
in
this
release.
Finally,
and
then
next
change
block
tracking,
so
I
actually
need
to
check
with
the
phone
and
other
folks
to
see
if
they
want
to
try
to
do
alpha
or
still
remain
in
design,
because
they
actually
made
some
very
good
progress.
They
did
the
they
did
the
poc.
A
They
are
going
to
do
a
demo
with
that,
so
we'll
actually
be
starting
to
update
the
cap.
So
I
will,
let
me
check
with
them
and
see
what
they
think
so.
D
Deep,
do
yes,
so
for
this
one
we
want
to
kind
of
shoot
for
an
alpha
in
125,
so.
I
A
Thank
you
and
okay,
no
expense
secret
yeah.
This
one,
I'm
pretty
sure
we're
going
to
try
alpha
again
because
we
just
last
time
we
basically
just
missed
the
deadline
but
everything's
there
so
continue.
A
D
So,
if
that's
the
case-
and
there
has
been
no
updates-
we
probably
need
to
find
another
person.
A
Oh
okay,
so,
okay,
do
we
have
anyone
else
here
who
are
interested
in
thinking
on
this
csr
proxy
for
windows,
transition
to
polish
containers?
Yeah
probably
should
someone
who
has
worked
on
windows
for
a
while
right.
So
all
right
looks
like
we
need
either
we
wait
for
mauricio
to
free
up
and
get
back
to
this
or
if
someone
someone
else,
wants
you
yeah,
okay,
okay,
either.
A
A
A
Do
we
have
anything
here,
officially
duplicate
cloud
provider
plugins?
Do
we
this
one
says
done
so?
Do
we
need
to
do
anything
with
this
row?
We
shall.
G
A
Oh
sorry,
I
think
I
feel
mute,
so
I
think
that
this
one
sees
the
migration
call
boxing
issues
we
just
leave
it
like
this.
C
So
I
think
we
we
might
have
missed
so
last
release
a
couple.
Drivers.
Migration
features
went
ga,
but
actually
the
core
csi
migration
feature
itself
is
still
beta.
C
Oh
okay,
we
might
need
a
another
item
here
to
track
the
core
migration
to
go
to
ga.
Oh.
A
C
I
think
the
core
should
go
first,
I
mean
it's
not.
C
C
It,
which
means
that
it's
still
possible
to
disable
csi
migration
so
that
that
kind
of
screws
up
some
of
the
code
removal
timelines
for
the
cloud
providers.
I
think.
A
J
All
right,
I
got
a
quick
question
on
that,
so,
if
we
I,
I
guess,
don't
if
we
still
have
a
way
to
be
able
to
disable
the
core
migration
feature
but
enable
individual
plug-ins
for
csi
migration.
C
A
Right
next
one,
this
video,
I
think
it's
I'll,
try
to
move
it
to
beta
and
on
by
default
right.
So
that's
the
target,
I
think
that's
the
same.
A
F
A
Yeah
and
then,
and
what
was
the
other
one
that
is
also,
is
that.
A
Okay,
oh
it's
a
file
so
file.
It
is
beta
on
by
default.
So
do
we
want
to
go
ga?
Do
we
know
what
is
this?
What
yeah
we
can
target.
C
A
B
C
That
too,
I
don't
know
if
matt's
on
the
line
here.
A
I
think
last
time
we
got
delayed,
I
believe
in
1.25
release.
So
this
one
did
not.
We
didn't
do
it.
So
that's
why
we
crossed
out.
So
let
me
see
there
are
some
notes
here.
It
was
yeah
delay,
21.25,
so
basically
we're
targeting
ga
right.
So
it's
already
on
by
default,
we're
talking
ga
but
then
delayed.
A
I
don't
know
why
this
one
yeah.
We
didn't
change
this
one.
This
one
actually
should
be.
Maybe
we
changed
it
back
so
so
maybe
we
can
say,
should
we
say,
try
to
ga
kojina
yeah.
We
can
sync
up
with
matt
long,
okay,
see.
A
A
Okay,
thank
you
and
yeah,
so
rpt
this
way,
I'm
pretty
sure
that
we
want
to
go
beta
off
by
default,
because
last
time
was
just
you
know
some
confusion
regarding
test
e3
test
requirements,
this
one
okay,
so
alpha
yeah,
this
one
was
also
delayed.
So
probably
we'll
go.
You
can
check
with
the
oh
check.
A
And
this
one
yeah,
I
think,
t
for
portworx,
I
think
tara.
Also
there
was
some.
You
know
misunderstanding
on
the
eq
test
requirement,
so
I
think,
which
should
be
still
trying
to
go
beta
and
always
on
the
reclaim
policy.
Okay,
so
do
we
want
to
go
because
last
time
we
actually
didn't
go
beta
because
the
ep
test
did
not
get
in
and
then
you
know
found
something
something
that
we
need
to
address
so
should
we
try
yeah?
What
do
you
think
you
should?
We
can
probably
try.
A
H
A
Converting
mode
convert,
control
volume,
conversion
right,
so
it's
alpha,
I
was
thinking
we
might
need
a
little
bit
time
on
the
sun,
because
when
we
do
re
when
we
were
doing
the
production
readiness
review,
there
are
a
lot
of
questions,
the
basically
they're
saying:
okay,
if
it's
going
beta,
you
need
to
think
more
about
this.
So,
but
let
me
let
me
double
check
I'll
check
with
ronald
and
see
what
he
thinks.
A
Okay
sounds
good,
thank
you,
thank
you
and,
and
then
this
next
one
we
cross
this
out
user
id
ownership,
incoming
maps
and
secrets.
So
do
we,
I
think,
command.
You
have
some
contacts
on
this.
Are
we
going
to
do
anything
or
just
what?
What
are
we
going
to?
What
are
we
going
to
do
with
this
one
just
to
leave
it
like
this
yeah?
I'm
not.
J
A
Something
so,
okay,
all
right!
Oh
just
leave
it
now
out
for
now
yeah
thanks
next
one
numbers
for
no
shutdown
yeah,
so
we
went
alpha
so
we'll
try
we'll
try
to
go
beta
in
next
release.
A
D
So
I
think
this
was
like
a
signaled
thing
that
they
were
working
on
and
the
reason
I
think
we
crossed
it
was
because
the
initial
phases
were
not
going
to
involve
actual
personal
volumes.
Oh
okay,.
D
So
basically
they
broke
it
down
into
three
phases
and
I
think,
like
they're,
working
on
phase
one
right
now
and
phase
three
was
when
they
actually
get
to
look
at
uids
for
percent
volumes.
So
phase
one
was
mainly
just
like,
I
think,
ephemeral
volumes
like
config
maps
and
stuff
that
does
not
get
shared.
E
D
I
believe
the
cap
in
signo
does
involve
changes
to
the
cri
to
basically
guess
like
to
come
up
with
a
uid
and
then
send
that
over
to
the
runtime,
and
they
did
require
changes
in
the
actual
runtimes
to
support
it
too.
E
Well,
the
way
that
the
linux
system
call
works,
you
you
just
give
it
a
name
space,
and
so,
if,
if
they
can
take
the
name
space
that
that
the
cri
was
going
to
use
for
the
pod
itself
and
also
use
that
for
the
mounts,
it
solves
all
kinds
of
problems.
I
I
want
to
go
read
that
that
kept.
So
it's
already
it's
already
merged.
C
E
B
B
E
I
think
kubernetes
has
some
expectations
based
on
just
the
long-standing
limitations
of
linux,
but
like
this
is
an
opportunity
to
break
from
the
the
very
ugly
past
and
get
it
right
for
once
the
backwards
compatibility
may
be
a
problem,
but
I
think
if
we
can
offer
like
a
path
where,
like
you
just
run
your
pod
as
the
uid,
you
want
to
run
as,
and
you
have
access
to
all
your
files,
no
matter
where
they
are
and
and
the
uid
and
gid
just
doesn't
matter
like
that.
That's
super
compelling.
A
Okay
thanks
next
one
is
oh,
this
one
pvc
created
by
silverset
will
not
be
auto
removed.
So
this
this
is
the
project
we
called
with
seagaps
and
is
matt
going
to
work
on
this.
Michelle.
Do
you
know,
what's
that
you
know,
but
this
this
was
offer.
A
And
okay:
next
one
is
warning
expansion
for
stay
for
sets.
I
have
not
checked
russellini.
Is
she
on
the
call
or
come
on?
Have
you
talked
to
her
recently.
B
A
Talk
to
her
recently
don't
know
suddenly
sounds
like
it's
not
that
it's
not
that
it's
just
you're
a
lot
of
unaddressed
issues.
B
Yeah
yeah
and
the
design
is
like,
like
we
have
updated
in
last
last
meeting
like,
for
example,
we
identified
me
and
jan
and
like
internet
that
I
hadn't
talked
how
this
will
work
and
we
identify
a
lot
of
corner
cases
that
are
very
hard
to
solve.
Like,
for
example,
you
have
four
replica
stateful
set
and
you
expanded
the
state
full
set.
Then
two
pvcs
got
expanded.
Third,
one
failed
because
you're
out
of
capacity,
then
how
will
recovery
work
from
that
scenario?
B
Then
we
identified
cases
about
what
happens
if
it
is
not
supported
in
the
driver,
then
we
there
is
like
subtleties
associated
with
online
and
offline
expansion
like
how
this
general
flow
will
work.
For
example,
certain
drivers
require
volume
to
be
offline,
then
later
on,
it
can
be
expanded.
So,
like
will
stateful
set
controller,
delete
the
part
and
then
create
it,
and
what
happens
if,
like
there
are
drivers
out
there?
That
say,
volume
has
to
be
online
and
so
basically
like.
A
A
lot
of
too
many
different
okay,
so
would
that
be
possible
for
us
to
say
we
only
support
online
expansion
for
this
case
or
something
just
to,
I
mean
sure,
not
supporting
all,
because
otherwise,
maybe
because
it
probably
will
still
be
helpful
because
right
now,
what
you,
the
user,
have
to
do,
they
have
to
manually.
Do
this
yeah
yeah.
B
B
B
A
B
And
I
think
I,
the
college
challenge
itself:
we
identify
a
lot
of
issues
and
we
she
said
she's
gonna
follow,
but
I
haven't
heard
from
her.
So
it's
just
it
requires.
A
A
Okay,
I
see
all
right,
so
I
guess
this
one
will
stay
in
design.
Then,
if
that's
the
case,
yeah.
B
Yeah,
and
also
please,
if
you
can
talk
if
you
managed
to
talk
with
her
yeah,
see
if
she's
actively
working
on
it
what's
the
status,
I
don't
know.
Okay.
A
A
Yeah,
I
actually
don't
know
how
much
time
she
has.
If
this
is
a
you
know,.
A
All
right
now,
next
one
the
content
notifier,
I
yeah,
I
think
I
still.
I
think
this
one
is
still
in
the
it's
still
the
the
cap.
Basically,
it's
still
trying
to
get
that
reviewed,
but
there's
not
much
progress
here.
I'll
check
with
sean
chan
see
what
he
wants
to
do
with
this.
A
And
next
one
is
a
prioritization
and
volume
capacity,
so
something
we
do
is
six
scheduling.
Do
we
michelle
do
you
know?
Are
we
going
to
do
anything
about
this?
Is
this?
Oh,
this
one
is
very,
this
is
strange,
is
I
thought
the
starting
as
beta
and
then
final
become
alpha?
What
is
the
status
of
this?
Is
it
alpha
or
what
this
is
probably
alpha
right.
C
C
D
C
C
Yeah,
I
need
to
check
back
on
the
chat
history,
but
I
think
for
now
maybe
we
can
just
under
the
owner
put
down
like
needs
new
owner
or
something
okay.
A
Okay,
so
I
will
just
cross
it
off
for
now,
since
we
don't
really
have
not
found
anyone
yet
all
right.
So
the
next
item-
this
is
someone
added
this
one
letter.
G
F
Change:
the
default
storage
class:
you
must
basically
delete
the
old
one
and
create
new
one,
because
we
don't.
D
D
F
Unfortunately,
this
pr
didn't
get
merged.
So
I
wrote
some
thoughts
about
this.
You
could
like
fix
it.
As
a
bug
fix,
we
will
change
kubernetes
behavior.
F
I
think
it's
a
change
for
better,
so
I
would
even
fix
it
as
bug
fix,
but
we
could
also
fix
it
as
a
feature
and
go
through
alpha
beta
ga
and
have
a
new
annotation
for
the
default
storage
class
and
so
on.
I
got
couple
of
ideas
in
this
document
so
and
I
could
get
a
person
who
could
implement
it
also
in
this
release,
either
as
a
bug
fix
or
as
alpha
feature.
A
A
So
the
propose
is
option
one
option,
two
right,
the
main
main
feature
I
mean
those
are
those
which
one
is
which
one
is
the
feature
which
one
is
his
back
face.
Well,.
A
First,
one
is
like
swings:
bug
fix,
okay,
wow,
just
okay,
okay,
so
please
read
this
and
then
we
can.
We
can
come
back
and
take
a
take.
Take
another
look
and
decide
next
time.
A
A
E
A
A
So
yeah
so
I'll,
just
I'll
just
add
it
here.
You
know
before
we
don't
really
have
any
issues
added
here.
Oh
actually,
I
think
the
initial
probably
should
copy
this
one
to
to
here.
Otherwise
I
will
lose
track
all
right.
Okay,
so
I
think
that's
all
we
have,
but
if
you,
if
anyone
you
have
anything
else,
you
want
to
add
yeah,
please
add
to
the
spreadsheet.
We
can
talk
about
it
next
meeting
going
back.