►
From YouTube: Kubernetes SIG Storage - Bi-Weekly Meeting 2021-12-16
Description
Kubernetes Storage Special-Interest-Group (SIG) Bi-Weekly Meeting - 16 December 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
A
B
Generally,
we
need
a
gap
between
beta
and
g
right.
We
just
now
really
move
this
to
beta,
I'm
not
sure
if
we
can
moved
it
to
ga
in.
B
A
A
Weird,
I
don't
think
that's
possible,
maybe
from
beta
to
ga
otherwise
I've
had
this
one
from
beta
to
ga.
Can
we
do
that
in
my
list?
I
I
thought
we
have
done
that
before
for
something,
but
I
couldn't
remember
which
one
okay.
So
this
is
a
question
mark
then
maybe
we'll
check
or
otherwise
it
will
just
keep
it
better
but
continue
working
towards
it.
A
A
Let's
see,
if
there's
any
documented
policy
on
this
also,
maybe
that's
something
we
could
yeah
anyway,
we'll
check
on
this
one.
A
Okay,
so
next
one
this
one,
this
is
crossout.
Do
we
need
this
one
command,
this
csi
online
apply
resizing.
This
is
the
okay.
So
this
is
a
copy
that
allowed
what
extension.
B
I
want
to
move
this
volume
yeah
expansion
in
general
to
ga
in
124.
Actually,
now
that
we
have
knocked
out
the
item
that
is
below
recovery
from
besides
failure,
I
think
we
can
move
the
entire
expansion
feature
here.
We
have
one
issue
painting
which
was
that.
D
B
Write
many
but
yeah.
A
Many
this
is
about
this.
This
is
oh,
no,
I
don't
know
the
issue.
Is
this
allowed
voting
extension
thing?
This
is
no
longer
issue.
B
A
B
Yeah
so
the
read
write
many
has
an
issue
and
I
actually
had
a
pr
for
it,
but
didn't
get
merged
like
a
couple
of
religious.
Basically,
when
you
expand
volume
on
on
one
note,
the
other
note
don't
get
node
expand
called.
I
think
ben
reported
it
long
back
and
I
had
appeared
but
didn't
get
merged
because
of
some
code
organization.
Stuff
is.
A
This,
like
in
general,
does
not
work.
Was
it
just
like
happened
occasionally,
this
is
what
would
it
have
to
do
this
before
or.
B
A
A
Okay,
this
one
okay,
now
this
is
the
question:
can
we
go
for
our
debater?
This
is
justification,
yeah,
good
question.
B
I
would
like
to
make
this
to
alpha
to
beta
that's
right.
A
A
A
Right
and
then
next
one
is
reissues
related
to
assuming
volumes
are
month
points.
So
this
is
the
back
picks.
Okay,
so
I
don't
know,
are
we
doing
anything?
Is
this
is
jing
on?
The
call
not
sure
looks
like
this.
One
doesn't
have
an
update
for
quite
some
time,
not
sure
what
this
does
is.
A
A
Okay,
this
one
also
probably
the
same
no
update,
so
it's
like
this
just
will
track
it
differently,
but
it's
kind
of
related
to
the
previous
one.
Okay,
do
we
want
to
do
anything
with?
This
is
patrick
on
the
call
story,
capacity
tracking.
A
A
F
A
A
And
then
the
next
one
is,
the
c
is
out
of
three
more
I
scuzzy
driver.
So
I
think
humble
is
humble
on
the
call,
so
he
said
he
might
not
be
able
to
so
looks
like
this.
Is
the
ongoing
work
it's
pr
out.
So,
let's
just
say
I'll,
go
in.
A
A
G
A
A
I
think
they
are
here
so
yeah,
I'm
not
sure
I
pinned
the
stuff
about
it
didn't
get
answered.
So
maybe
you
just
need
to
check.
A
And
then,
since
I
want
to
house
additional
metrics,
so
this
one
we
missed
it,
you
might
not
23,
so
we
will
try
to
get
it
in.
This
is
really
the
code.
It's
already
there.
Just
need
to
get
that
merged
so
so
run
is
already
organized
addressing
the
comments,
so
I
think
come
on.
So
I
think
he
addressed
your
comments.
A
Thanks
the
next
one,
since
I
wanna
have
pragmatic
response,
so
I
think
we
probably
what
you
design.
I
I
need
to
check
with
nick
and
see
if
he
wants
to
do
some
prototyping.
A
H
C
Yeah,
you
can
hear
me
yes
yeah.
This
one
was
meant
to
go
beta
in
123
and
I
didn't
get
it
done.
So
we're
just
gonna
push
that
to
124.
C
Right,
the
outer
tree
work
needs
to
get
done
and
then
the
entry
work
is
going
to
be
very
small.
Just
you
know
moving
it
changing
the
feature.
Gate
really.
H
A
Okay
thanks
next
one
is
cozy.
Okay,
I
didn't
check
it,
I'm
not
sure
if
I
think
I
think
we
had
some
good
discussions
last
time
and
then
see
this
is
going
to
update
it.
I
think
michelle
is
going
to
review
this
one.
I
don't
know
if
michelle's
on
the
call,
but
I
think
we
will
try
to
do
us.
Your
offer.
A
A
All
right,
the
next
one
is
change.
Block
tracking
is
fun
on
the
call
by
any
chance.
I
think
he
said
he
is
he's
a
little
busy,
but
he
will
get
back
to
this
one.
So
we'll
just
still
try
to
do
the
design.
D
Yeah
we'll
continue
to
iterate
on
it
during
1.24.
D
F
A
Now
the
next
one
is
c
as
a
proxy
for
windows,
translation
to
pre-legit
containers.
What
is
the
status
for
this?
One.
D
So
this
is
still
in
in
design
as
of
last
week,
yeah
there's
some
prototypes.
We
have
a
path
forward
that
we
agreed
on
like
mauricio
I
enjoy
and
yeah
we'll
get
to
work
on
it
through
1.24.
A
Thanks
so
this
next
one,
this
is
a
humble
actually
because
the
t
initially
thinking
it's
just
a
code
change
and
there's
no
cap
needed
but
turns
out.
We
need
a
capitalist,
node
extension
secret
thing.
So
it's
going
to
add
a
tab.
A
I
A
We
can
maybe
leave
it
a
little
bit
and
because
so
this
is
a
send
out
and
then
and
then
we
don't
really
have
plan
to
remove
the
code,
the
entry
code,
so,
okay,
we
can
leave
it
here
for
a
while.
Maybe.
A
Okay,
so
the
next
few
items
are
csi
migration
related
the
first
one
is
migration,
officially
duplicate
copyright
plugins.
So
this
is
marked
down.
Okay,
do
we?
I
don't
know
if
we
need
to
well.
I
thought
we
still
need
to
track
this
right,
because
we
we
still
need
to
move
to
ga
and
is
it's
joey
on
call
joey,
matt
or
michelle?
Maybe
who
knows
more
about
this?
One.
I
A
Now
I
think
the
next
next
one
is
the
same,
so
I
think
in
general
all
of
this
we
need
to.
We
need
to
create
a
cap
for
most
of
this,
because
initially
we
have
this
one
big
cap
right
use
that
to
track
all
of
this,
but
then
the
release
team
getting
very
confused.
They.
I
I
think
that
makes
sense.
Maybe
we
can
put
it
in
a
comment
somewhere
just
to
make
sure
it
gets
captured.
A
A
Leave
this
here
I
can
pin
charlie
and
michelle
see
what
they
want
to
do.
It's
basically
a
very
short
cap
for
each
one,
and
then
this
will
have
a
reference
to
the
the
big,
the
main
cab.
A
So
okay,
so
then
we
cut
we
just
look
at
each
one
of
those.
We
sphere.
I
think
we
probably
still
want
to
because
we
didn't
really
go
turn
around
by
d4.
So
we
may
want
to
try
that,
but
I
need
to
check
with
them,
because
there
are
some
concerns
on
especially
the
nfs
4
thing,
but
we're
still
not
sure
so,
just
a
new
check.
A
And
as
you
disk,
so
as
your
disk
is
already
on
by
default,
we're
trying
to
move
that
to
ga,
I
guess
do
we
have
anyone
here,
because
we
don't
have
and
d
michel
looks
like
right.
A
We
need
to
check,
I
guess,
all
of
those
already,
because
we
don't
looks
like
they're
not
here.
The
next
one
is
the
azure
file.
I
think
I
think
this
one
still
needs
to
yeah,
so
this
is
still
the
same
thing
here
beta
but
default.
I
think
this
is
correct
and
then
the
next
one
ga
on
by
d4,
is
mad
going
to
work
on
this.
I
We
can
put
matt's
name
on
that
one
and
he
can
finalize
in
a
future
meeting
if
he's
gonna
work
on
it
or
not,.
A
Okay,
so
his
name
is
there
and
next
one
aws
ga,
okay,
I
think
this
is
a
yeah
one's
names
there.
I
guess
probably
would
just
leave
his
name
there,
then.
A
So
I
added
so
I
I
see.
I
don't
know
why
this
one
is
not
not
in
the
previous
spreadsheet,
so
dims
actually
submitted
a
a
pr
to
move
this
to
ga
so
put
his
name
here,
and
this
one
would
also
need
a
cap.
A
So
young
see
you
already
reviewing
that
pr,
oh
yep,
okay,
and
then
I
think
this
one
yeah
this
one
basically
tried
to
go
to
beta
this
one's
this
one's
fine
beta
and
this
one.
Next
one
is
target
alpha.
A
A
J
Yeah
so
everything's
checked,
then
so
I'm
think
I'm
gonna
explore
what
additional
things
are
necessary
to
move
it
into
beta.
A
A
A
Okay,
next
one
control
volume,
conversion
between
source
and
target
pvc.
Are
you
running
here.
K
Yeah
hi,
I
think
we
can
target
alpha
for
this
for
124,
I'm
not
sure
if
we
need
cap
or
not
yet,
but
probably
no
soon,.
A
A
A
That's
the
yeah,
that's
the
one
with
the
ckpi
machinery,
the
eu's
production,
so
check
for
pm,
and
then
next
one
is
a
user
id
ownership
of
config
max
and
secrets.
A
D
But
you
can
look
at
the
latest
step
as
well.
I
think
yeah
for
phase
like
they've
broken
up
the
feature
into
three
phases:
phase,
one
and
in
the
first
phase,
they're
just
targeting
the
entry
ephemeral
volumes
like
basically
pods
that
do
not
have
persistent
volumes
at
all,
so
only
config
maps
and
secrets,
and
basically
attach
username
spaces
to
only
parts
that
do
not
have
you
know
any
pvcs
or
any
other
kind
of
fml
volumes.
A
This
this,
this
is
the
same
issue
that
you
guys
are
talking
about:
user
id.
Only
google
maps
and
secrets.
D
A
A
D
And
the
first
phase
is
just
starting
like
config
maps
and
secrets:
okay,
and
attaching
like
unique
user
namespace
spaces
to
pods,
with
only
ephemeral
volumes.
Okay,.
D
So
basically,
the
like
that
would
come
in
sort
of
like
phase
two
like
in
phase
two.
The
idea
is
they
want
to
do
like
a
a
cluster-wide
user
id
for
for
everything
that
has
anything
other
than
for
any
pods.
That
has
anything
other
than
config
maps
and
secrets
and.
D
Support
like,
inter
pod
uniqueness
and
then
phase
three
is
kind
of
like
the
real
thing
that
you
were
discussing,
which
is
around
having
like
the
mapped,
ids
right.
C
Right
so
so,
but
just
so,
I
understand
in
in
the
short
term
we're
going
to
change
the
behavior
of
pods
with
no
volumes
or
only
ephemeral
volumes
and
leave
the
ones
with
volumes
with
the
existing
behavior
and
then
later
we'll
address
the
ones
that
have
volumes.
Try
to
make
those
better.
Is
that
accurate,
okay,
cool.
A
A
A
Okay,
okay,
next
one
is
okay.
Pvc
created
by
staple
set
will
not
be
auto
removed,
so
this
is
alpha
minor
23
so
where
this
go
to
beta
is
matte
here.
A
Okay,
so
that
is.
This
is
okay,
just
targeting
beta
right.
I
A
Thanks
and
next
one
is
the
one
expansion
for
staple
said
so
talk
to
you,
shalini
she'd
like
to
try
to
target
alpha,
so
I
need
to
review
this
again.
B
B
A
A
C
A
Okay,
so
this
one,
the
next
one,
the
song
we're
doing
the
sig
node
planting
the
notifier.
We
probably
still
have
to
keep
this
to
design
because
I
just
talked
with
shan
chen,
but
maybe
we'll
see
we'll
see,
maybe
in
another
week
or
so
or
see.
If
we
want
to
change
it
so
right
now
we
keep
it
in
design
with
it's
just
the
holidays
and
all
that
it's
getting
just
too
short
for
this
one.
A
A
E
A
Do
we
is
there?
I
thought
there
was
one
young
jonathan
brought
up
some
something
to
do
with
adding
a
finalizer.
I
thought
he
has
some
cap.
Do
you
want
to
do
that
in
1.24,
or
I
thought
he
talked
about
that
some
some
time
ago?
I
know
that
cap,
but
I
don't
know,
what's
the
plan
for
that.
A
I
don't
remember
the
details.
I
think
it
has
to
do
with
like
certain
cases,
there
are
some
leaking
volumes
or
something
still
there's
a
he's,
trying
to
add
a
something
some
finalizers.
I
think
he
has
a
cap
actually,
but
I
don't
know
like
the
plan.
Okay,.
A
A
Oh
people
can,
they
can
add
yeah.
That's
because
sometimes
I
think
in
previous
previously
somehow
it
a
lot
of
things
got
disappeared
by
accident.
That's
right!
No,
so
what
you
can
do
is
people
can
add,
or
you
can
also
add
here
right.
You
can
add
in
here
then
maybe
one
of
the
lead
one
of
the
64gb
can
add
to
the
spreadsheet
or
you
can
also
ping
us
on
the
slack.
If
you
want
to
add
anything
so
this
one,
you
can
actually
add
a
comment.
It's
just.
I
found
the
comment.
A
A
So
yeah
but
feel
free
to
you
know
just
add
it
to
this
agenda
doc.
If
you
want
to
add
and
say,
I
want
to
add
something
to
the
spreadsheet
or
pin
someone
on
slack
okay,
so
that's
all
we
have
on
the
planet
spreadsheet
all
right.
A
I
think
our
is
that
our
next
meeting
is
that,
like
end
of
the
end
of
year,
we
probably
will
cancel
that
one
and
then
yeah,
if
it's,
if
it's
like
and
the
last
week
of
december
sad.
A
A
Okay,
now
going
back
to
this
one,
so
we
have
a
menu,
is
menu
on
the
call
you
do
you
want
to
talk
about
this.
No.
G
G
Oh
yeah,
the
introducing
like
the
open
at
two
mount
calls
to
identify
to
improve.
Oh.
G
A
A
A
Just
what
is
the
name,
so
this
is
the
name.
What
is
this
is
the
name
of
the
of
this
thing.
E
Okay,
I'm
not
sure
like
the
fix,
is
being
proposed
against
moby.
Oh,
and
are
we
tracking
fixes
against
moby
here.
G
Yeah
once
like
so
I
jing
and
when
I
was
talking
about
the
pr
kalishkan
I
can
update
on
that,
was
pushing
hard
against
like
introducing
the
introducing
this
into
moby,
the
reason
being
that,
right
now
in
kubernetes
code
base,
we
unit
tests
are
not
run
as
root,
so
it's
very
hard
to
test
all
the
cases.
G
A
G
Yeah
and
I
opened
up
like
an
alternate
pr,
because
kubernetes
already
realized
kubernetes
today
already
relies
on
more
pieces.
So
what
we
can
do
is
once
this
pr
is
merged.
We
can
update
the
dependency
and
then
what
is.
G
So
initially
the
way
I
started
it
was
by
introducing
the
change
into
kubernetes
by
looking
at
mobisis,
which
had
the
openness
to
call
and
then
when
the
pr
was
being
reviewed
there,
the
to
make
sure
like
the
support
was
at
one
place
common
to
both
kubernetes
and
docker.
A
G
That
approach
so
and
also,
I
think,
yan,
had
a
look
at
it.
Last
night.
A
G
A
If
you
know
we
do
have,
I
think
we
have
a
couple
of
bugs
that
trap
here.
I
think
we
can
yeah,
maybe
just
make
an
exception
for
this
one
just
to
it's,
probably
just
a
quick
update,
but
what's
the
no
I'm
not
sure,
what's
the
name
or
for
this
one,
it's
you
say
it's
not
well,
it's
is.
Is
this
still
this
one
or
not
this
name?
How
do
we
say?
What's
the
name
of
this
determine
so
determining.
G
Yeah,
I
think
the
name
is
it's.
Okay!
It's
fine
for
yeah!
This
is
fine.
I'll,
add,
like
probably
like
latest
one
kernels,
five
dot
six
plus
happen,
something
like
on
kernel,
5.6,
plus.
A
All
right,
okay,
I
think
there
is
a
oh,
yes,
we'll
have
something.
A
A
If
you
you
know,
if
you
need
anyone
from
search
side,
your
help
is
the
review
looks
like
it's
already
reviewed.
So
basically,
then,
whenever
you
update
the
dependencies,
then
when
that's
merged,
then
we're
done
right.
G
And
then
I
will
have
to
make
some
code
changes
to
mount
utils.
F
A
A
Much
thank
you
for
working
on
this
okay
looks
like
that's
all.
We
have
anything
else.
H
C
A
A
C
A
Okay,
so,
but
okay,
that's
good
actually!
Well!
Well,
that's
good!
It's
you
know,
even
though
they
it's
not
final,
then
I
think
this
is
a
good
sign
that
will
have
more
time
much
better
than
previously
thought.
Okay,
all
right,
then,.
A
A
Okay,
if
we
don't
have
anything
else,.
I
Shin,
can
you
add
a
note
at
the
bottom
over
here
saying
next
meeting
is
cancelled
and
then
oh
yes
I'll
see
if
I
can
go
ahead
and
cancel
that.