►
From YouTube: Kubernetes SIG Storage - Bi-Weekly Meeting 2023-09-21
Description
Kubernetes Storage Special-Interest-Group (SIG) Bi-Weekly Meeting - 21 September 2023
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
D
Sorry
this
is
The
Crossing.
D
Spoke
with
I,
and
they
said
they
were
interested
in
in
pushing
the
reference.
Grant
cap
I'm,
not
sure
if
they
opened
a
pier.
Yet,
though,.
A
A
A
And
next
one
CSI
wedding
house,
this
is
to
add
ET
test,
so
I
did
talk
to
actually
I
think
she
is
still
is
trying
to
fix
something
in
her
lab
environment.
So
so
it's
still
working
progress.
A
So
we
there's
a
there
is
a
cap
and
then
there's
a
CSS
back
PR.
That's
been
reviewed,
Ben.
E
Yes,
I
expecting
at
least
is
in
good
shape.
The
cap
is,
is
on
my
review.
Queue
and
I
haven't
gotten
to
it.
Yet.
A
A
Well,
this
is
back
to
the
gyms,
did
get
back
for
the
reviews.
E
A
A
Thank
you,
and
next
one
is
this
rewrite
once
access
mode,
the
new,
the
new
one,
the
romance
part?
So
we
are
moving
this
to
GA
it's
Chris
here.
Well,
Michelle.
You
want
to
give
an
update.
D
Yeah
I
think
the
prsr
out
and
so
I
think
it's
just
waiting
for
approval.
A
D
A
C
Yeah
so
I
think
the
last
time
when
we
talked
about
this,
we
were
trying
to
figure
out
what
the
next
steps
should
be.
I
think
it
seems
like
based
on
the
discussion
that
we
had
that
there
may
be
like
a
resets
that
may
be
needed
in
terms
of
trying
to
understand
how
we
want
to
approach.
This
I
think
Ben
in
particular,
had
some
questions
around
what
the
model
should
be
for
security
Etc.
C
So
at
least
for
now,
I
think
we
will
probably
go
back
on
this
and
and
kind
of
start
looking
at
it
from
afresh
and
and
see
what
makes
sense
and
at
some
point
we
will
probably
come
back
with
a
proposal
on
this
one
and
and
circulate
that
with
the
rest
of
the
community.
I
think
it's
unlikely
that
it's
going
to
happen
in
the
129
time
frame,
though
so
so
I
would
say
that
this
is
probably
more
long-term
at
this
point.
So.
E
C
Think
yeah,
yeah,
no
I,
think
I
think
I
think
I'm,
not
blaming
you
for
sabotaging
time.
I
think
the
concerns
that
you
raised
are
valid.
We've
had
some
internal
discussions
around
this
as
well.
In
terms
of
you
know
what
makes
sense
and
it
doesn't
seem
like
there
is
any
clear
consensus
yet
regarding
which
which
to
take
so
probably
worth
doing
some
more
investigation
and
I'm
trying
to
figure
out
what
is
the
right
step
here
so
I.
D
C
And
I
think
I
think
we
want
to
kind
of
hopefully
come
up
with
a
solution
which
is
mostly
agreeable
to
everybody
in
the
short
term
at
least,
and
then,
if
there
is
a
longer
term
solution
in
future
that
we
need
to
work
towards,
we
can
we
can.
We
can
think
about
that.
So.
A
And
then
we
have
a
few
items:
that's
for
future
releases,
the
driver,
removal
and
next
one
always
owner
reclaim
policy.
So
unfortunately,
Deepak
has
some
family
issues.
He
has
to
take
care
of
so
I'm,
not
sure
if
we
can
actually
meet
the
the
deadline,
so
so
I'll
just
say
and
not
be
able
to
do
it.
I
mean
we
may
need
to
move
this
one
until
next
next
quarter,
but
I'll
leave
this
here
for
now.
D
To
make
sure
the
cap
is
updated,
I
believe
we
just
need
to
update
the
milestones.
C
So
I
believe
that
there
were
three
issues
that
were
part
of
the
implementation,
one
of
which
was
being
handled
by
Connor
from
AWS,
so
Conor
I
believe
has
already
sent
out
a
PR
for
his
issue.
C
I
think
I'm
I
believe
we
are
still
targeting
129
if
I'm
not
mistaken.
Although
I
don't
know
the
latest
on
this
one,
so
yeah,
that's.
D
Right
we're
gonna,
Target,
129,
yeah,
so
I.
Think
first
step
is:
we
need
to
make
sure
the
enhancement
is
properly
trapped
by
the
release
team.
That
requires
a
couple
of
updates
to
the
kept
Milestones
and
then
yeah
and
then
for
the
actual
implementation.
D
A
Okay,
yeah,
so
no
no
there's
a
another
API
PR
that
is
out
for
review,
so
corner
is
working
on
which
part
the
controller
change.
Your.
C
I'll
have
to
dig
up
the
exact
year.
Oh.
A
Okay,
it's
good
progress
thanks,
but
so
we
don't
need
any
new
EQ
test
for
this.
Do
we?
But
it's
already
it
is
already
there.
We.
A
All
right,
thanks,
XY
storage
capacity
story,
tested
scoring
Michelle.
Did
you
have
an
update
on
on
this.
A
So
does
the.
A
Does
he
want
to
go
for
Alpha
or
just
do
design?
That's.
A
A
Next
one
is
auto,
delete
PVC,
so
it's
the
Steve
was
set
so
I,
don't
know
if
Matt
is
here,
Michelle
are
we?
Are
we
moving
this
to
jail
or
not?
Do
you
know,
did
you
chat?
Did
you
check
this.
D
D
Because
the
the
way
the
feature
was
implemented
is
it
started,
adding
an
owner
reference
onto
PVC
objects
that.
C
D
Created
by
staple
sets
and
I
think
Matt
was
not
sure
if
that
could
interfere
with
any
operators
that
might
also
be
creep
putting
owner
references
on
pecs.
So
he
was
just
trying
to
look
for
like
anybody.
Try
using
this
feature
successfully
and
I
think
he's
been
having
some
difficulty
with
that.
Okay.
A
D
Can
try
to
make
sure
it's
mentioned
in,
like
any
of
the
coupon
Sig
update
sessions.
A
Yeah,
okay,
we
probably
should
have
yeah.
We
should
probably
add
that
right
normally,
we
we
only
talk
about
things
that
are
targeting
someday,
but
maybe
something
is
already
completed.
We
probably
should
maybe
should
add
something
to
bring
awareness,
yeah,
yeah,
okay,.
A
A
Okay
I'll
leave
this
here
for
now,
I
I,
don't
think
we
have
targeted
this
in
a
cab
you
should
solve
yet.
So,
oh,
what
happened
to
oh?
That's
this
next
one
right:
let's.
A
Market,
all
right,
okay,
so
next
one
this
is
added
by
pen
and
an
option
to
disable
six
minute
Force
detached
timer
is
there
is
the
priority
already
merged.
E
I
don't
know
if
this
one
has
emerged
there.
This
one
actually
turned
into
two
separate
issues:
okay
about
the
six
minute
timer,
which,
as
far
as
I,
can
tell
it's
still
under
discussion,
but
there
was
another
bug
found
which
was
around
temporary
failure
is
becoming
permanent
when
the
CSI
driver
got
unregistered
temporarily
and
that
that
was
fixed
and
that
fix
was
merged.
Okay,.
E
A
A
Okay,
so
the
next
one
cozy
bucket
quota-
I,
don't
like
Blaine-
is
here,
so
he
brought
this
up
in
the
Cozy
standard
meeting.
So
yeah
there
was
a
there's,
an
issue
opened
and
there
is
also
a
cap
submitted
for
this
one.
A
So
this
is
like
getting
a
quota
of
the
number
of
objects
in
a
bucket,
but
the
object
itself
actually
doesn't
really
have
a
kubernetes
API
representation.
A
Next
one
is
the
season
set
car
or
you
want
so
Mauricio
talked
about
the
scene,
the
last
meeting
I,
don't
know.
If
my
ratio
is
here
's
not
here,
are
there
any
more
update?
D
No
I
don't
think
there
has
been
any
new
updates
since
last
week.
Okay,.
A
Oh
here,
let's
see,
let's
see,
proposal
as
well
received
as
a
proposed
Target
here
will
be
completed
uncontinent,
but
we
can
start
tracking
status
updates.
Okay,.
A
Okay,
let's
see.
Okay,
that's
all
we
have
on
this
brush
sheet,
so
coming
back
here.
So
just
a
reminder
of
the
coming
deadlines:
production,
readiness,
that's
that
has
a
September
September
28th,
that
that's
the
that's
the
deadline
and
the
the
cap
freeze
date
is
October
5th.
A
So
if
you
have
a
feature
targeting
in
1.29,
so
here
are
the
dates
that
you
should
pay
attention
to
and
see
this
bag,
as
we
are
still
tentatively
trying
to
cut
a
release
end
of
September
and
trying
to
get
the
CBD
Seaside
stack
PR
in
before
we
do
that.
A
So
I
don't
see
any
other
issues
added
here.
Are
there
anything
else
people
want
to?
Because
in
today's
meeting.