►
From YouTube: Kubernetes SIG Storage - Bi-Weekly Meeting 2022-01-27
Description
Kubernetes Storage Special-Interest-Group (SIG) Bi-Weekly Meeting - 27 January 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
Hello,
everyone
today
is
january,
27
2022.
This
is
the
kubernetes
storage
sig
meeting
today
we
are
going
to
go
through
the
1.24
planning
spreadsheet
today
is
the
prr
soft
freeze.
So
if
you
are
working
on
a
feature,
your
cap
needs
to
have
the
production
revenue
section
filled
out
and
assigned
that
to
a
pr
reviewer.
B
Yes,
I'm
updating
the
prr,
I
updated
the
prl
for
recovery
case
and
I'm
updating
the
prr
for
expansion.
I
based
such
an
old
cap
and
I
have
it's
like.
Basically,
there
are
three
feature
gates
inside
it.
Actually,
like
the
expansion,
expand,
persistent
volume,
expand
in
use,
processing
volume
for
online
and
expand
csi
volume,
so
all
of
them
are
beta
and
I
don't
want
to
write
three
prrs,
so
I'm
hoping
that
that
they
will
accept,
like
the
other.
B
A
Okay,
they
yeah.
Let
me
have
questions,
I
remember
they
had
some
questions
during
the
review
for
the
csm
migration.
There
are
several
feature
gates.
A
At
least,
but
you
probably
need
to
mention
that
in
the
cap,
otherwise
they
may
have
questions
for
that,
but
I
think
it's
probably
it's
probably
okay
for
now
right,
you,
you
just
need
to
just
one
second.
C
No,
it
is
the
feature
gate
field
in
the
cap.
Template
is
array.
B
Yeah,
it
is
array,
so
I
I
I
saw
that
in
cab.com
and
like
in
other
places
in
the
markdown,
it's
not
early,
but
I'm
making
sure
it
should
be.
Okay
in
the
readme.
A
So
I
think
if
you
just
fill
out
the
pr
section
today,
then
you
are
fine
for
today's
deadline
list,
because
the
tab,
if
you
know
once
they
start
reviewing
it,
then
you
can
add
more.
A
So
yeah
today
I
think
then
you
submit
that
and
yeah,
probably
the
focus
focus
on
just
just
to
complete
the
pr
section
and
then
once
you
submit
the
cap,
you
can
always
update
it
right
still.
I
have
until
the
third
together
merged.
D
A
B
And
the
first
second
item:
I
already
have
updated
the
prr,
the
recovery
from
research
failure
and
I
have
assigned
it
to
david
eats
I
pinged
him
also.
He
has
not
actually
responded
back.
I
don't
know.
Hopefully,
you'll
have
time
to
let
particularly.
A
A
E
Yes,
so
the
main
update
is
related
to
the
checking
amount
point
with
a
faster
approach
without
depending
on
the
proc
mount
information.
E
That
was
the
first
step
need
to
be
added
in
the
mobi
sys
repo.
E
The
original
pr
was
kind
of
reviewed,
but
the
the
I
think
the
main
reviewer
is
that
he
he
said
he
opened
a
new
pr
to
replace
that
one.
E
E
A
C
E
Yes,
yes,
so
we
can
use,
still
use
two
different
tracking.
So
I
think
for
the
other
issue
I
mentioned:
there's
not
much
progress
yet.
C
D
A
A
Thanks
next
one
warning
group:
api
yeah
not
got
time
to
work
on
this
one
yet
update,
and
next
one
you
see
is
the
auto
trim.
Iscsi
driver
fit
and
finish
humble,
give
me
an
update.
He
said
just
got
the
first
release
out
michelle.
Do
we
still
need
to
track
this?
If
this
is
already
moved
and
the
first
release
out,
we
still
need
to
track
this.
C
A
C
A
In
the
meeting
today,
so
I
pinned
him,
I
asked
him
if
he
is
interested
in
helping
mustafa.
He
said
he
is,
but
after
that
I
have
not
heard
anything
so
yeah,
okay,.
A
I
got
it
right,
we
got
his
name
right
and
the
next
one
is
wedding
house
additional
matrix.
So
this
one
we
do
have
a
so
we
do
have
this
pr,
so
khaman
has
already
reviewed
it
and
he's
good
with
it,
and
then
all
we
also
got
to
look
to
me
from
someone
from
the
instrumentation
side.
I
think
we
should
right
now
just
need
to
find
the
find
people
to
approve
it.
Just
so.
A
Next
one
c,
seven
house,
pragmatic
response-
I
think
I
think
nikki's
we're
now
probably
busy
with
the
chinese
new
year,
so
I'll
ping
him
after
that.
C
A
So
I
know
michelle
you
reviewed
it.
I
I
have
not
checked
for
the
last
few
days.
So
do
you
know
what's
the
status
still
waiting
for
them
to
update
the
cap,
or
you
know
I
unfortunately
haven't
kept
up
so
we'll
find
out
in
the
meeting
which
is
coming
after
this
meeting.
So
I
believe
in
the
last
meeting
we
talked
about
how
to
address
the
comments
and
I'm
not
sure
if,
if
sit
has
updated
yet.
A
Next
one
is
change
block
tracking,
so
I
just
asked
fun.
I
think
he
says
he
will
get
back
to
work
on
this
design,
but
he
has
because
he,
I
think,
he's
busy
right
now,
so
he
has
not
a
chance
to
work
on
this
yet,
but
he
will.
G
Yeah
working
on
the
cap
for
this
in
preparation
for
the
arch
and
the
node
reviews,
so
this
will
continue
to
be
in
design
for
this.
For
this
release,.
G
This
basically
in
progress,
pretty
much
main
updates
there
is.
There
are
a
few
folks
from
red
hat
who
has
joined
the
meetings
and
may
have
cycles
to
contribute
towards
the
optimizations
that
that
I
think
you
brought
up
shing.
A
Next
one
node
expansion
secret
so
humble
says
this:
he
got
a
look
to
me
from
michelle
and
then
just
reading
for
a
pr
review.
So
this
one
is
on
track.
A
H
I
don't
have
any
update.
Did
you
have
any
update
michelle?
I
mean
I,
I
did
add
an
item
just
to
make
sure
it
was
well
known
that
for
the
gcepd
we're
going
to
delay
ga
till
125,
and
so
that's
going
to
have
knock
on.
H
I
assume
on
the
core
as
well,
because
I
I
thought
the
plan
was
was
that
we
were
going
to
wait
until
we
ga
you
know
some
a
couple
of
the
specific
providers
before
we
jade
the
the
the
core
stuff.
But
I
may
be
wrong
on
that.
Does
anyone
else
here
have
any
feedback,
opinions.
H
Yeah,
so
it's
like.
Are
we
going
to
wait
to
ga
the
core
until
we
ga
some
of
the
like,
until
we
ga
a
specific
one
or
like
gcepd,
in
particular,.
I
A
Oh
oh
1024,
oh
okay,.
A
Okay,
so
matt-
and
there
is
this
issue,
can
you
add
some
comments
there,
just
so
that
the
release
team
know
that
we
are
not
tracking
this
for
1.24
now.
H
Yes,
it's
been
done.
A
Oh
okay,
thank
you
all
right,
let's
see
the
what's
the
next
one
core
I'll
say
we,
we
sphere.
I
think
I
think
michelle
you
have
already.
You
look
good
to
me
right.
This
one
is
all
done.
Is
it
still
pending
something
pr
or
something.
C
I
think
for
the
actual
prs
that
were
flipping
the
future
gate.
I
think
it
was
just
waiting
on
all
the
caps
and
stuff
to
be
approved,
so
I
think
it's
I
believe
most
of
the
cups
have
been
approved
like
as
of
yesterday
or
something
so.
I
think
we
can
go
back
now
and
look
at
these
pr's.
A
A
So
probably
the
same,
I
would
just
would
okay,
I
can
go
double
check
each
one
of
them
after
the
after
the
routine
yeah.
I
did
see
a
lot
of
look
to
miss
so
all
of
those
right.
What
about
the
this
aws
has
this?
So
I
remember
there
was
a
hold
on
aws.
What's
the
plan
for
aws
ebs.
A
A
A
And
so,
okay,
and
then
for
the
for
sev
rbd,
humble
says
this
is
also
updated.
I
think
michelle
already
given
look
good
to
me
on
this
one.
A
I
forgot
the
pr
status,
but
it's
probably
but
at
least
the
sections
filled
and
then
ceph
self-fs.
Actually
we
were
missing
a
cab
earlier,
so
humble
just
submitted
one.
Yes
I'll,
add
a
link
here
michelle.
If
you
want
to
take
a
look.
Basically,
it's
the
well,
it's
just
a
copy
from
this
other
cabinet.
So
change
this
one
to
alpha.
A
C
I
believe
there's
a
cup
out.
I
haven't
had
a
chance
to
take
a
look
at
it.
J
Yan
gave
me
initial
set
of
comments.
I
resolved
them,
I'm
just
waiting
for
any
follow-up,
I'll,
probably
bring
them
again
today.
Okay,
thank
you.
A
A
So
so
I
also
pinned
the
jordan
to
see
if
he
has
other
comments.
I
think
right
now
the
cap
is
written
based
on
his
feedback
and
then
also
waiting
for
pr
review,
but
that's
at
least
that's.
The
next
section
is
filled
out
so.
A
And
then,
and
then
we
have
this
two
items:
secret
production
and
the
in-use
protection.
I
think
those
are
all
from
osaki.
B
No
update
yet,
I
think,
just
yeah.
It
needs
a
new
design.
A
A
A
A
A
So
can
you
update
the
the
cap?
I
mean
other
capital
issue
so
that
yes.
A
Next
one
is
a
rolling
expansion
for
stifle
set,
so
I
think
khomar
has
reviewed
it
and
added
comments,
but
I
think
shalini
has
not
updated
the
cap,
yet
I
I
need
to
pink
her
because
I
I
just
realized
that
yesterday
that
she
actually
didn't
well.
Actually
it's
so
purifying.
She
has
the
section
the
pr
section
filled
out
it's
just.
There
were
a
few
things
that
she
need
to
add
a
pr
review,
or
maybe
that's
not
too
bad,
so
pinker
again.
A
And
next
one
is
a
exclusion
hook
container
notifier,
so
we
really
have
not
got
a
chance
to
make
any
progress
on
this
one.
So.
A
A
Okay,
so,
basically,
if
folks
are
have
some
experience
with
this,
this
secret
linux,
and
if
you
please
review
it
right.
A
That's
all
we
have
on
this
spreadsheet
and
so
moving
back
here.
So
after
today's
deadline,
the
next
deadline
is
thursday
is
the
february
3rd.
I
actually
got
the
date
run
earlier.
I
just
realized
it's
actually
february
3rd.
If
we
are
talking
about
pacific
time,
six
o'clock,
six
pm,
that's
the
enhancement
freeze
next
next
week,
next
thursday.
A
And
we
have
one
issue
here.
I
think
we
already
talked
about
this
one
right.
So
matt
you
added
this
one.
Basically,
we
are
delayed
the
ga
for
gcpd
csm
migration
2.
Why
not
25.
H
A
Okay
sounds
good.
Do
we
have
anything
else
that
we
want
to
discuss
in
today's
meeting.