►
From YouTube: Kubernetes SIG Storage Meeting 2023-07-13
Description
Kubernetes Storage Special-Interest-Group (SIG) Meeting - 13 July 2023
Meeting Notes/Agenda: https://docs.google.com/document/d/1-8KEG8AjAgKznS9NFm3qWqkGyCHmvU6HVl0sk5hwoAE/edit#heading=h.6isw1846ipjr
Find out more about the Storage SIG here: https://github.com/kubernetes/community/tree/master/sig-storage
Moderator: Saad Ali
A
All
right
today
is
July
13
2023.
This
is
the
meeting
of
the
kubernetes
storage
special
interest
group.
As
a
reminder
of
this
meeting,
is
public
recorded
and
posted
on
YouTube
on
the
agenda
today
we're
going
to
go
over
the
128
items.
The
next
upcoming
deadline
here
is
July
18th,
which
is
code
freeze
next
week.
So
that's
coming
up
fast
for
anybody
that
is
working
on
features.
Please
remember
that
date
and
if
you
have
anything
that
you
want
to
add
to
the
agenda,
please
feel
free
to
do
so.
A
B
A
B
I
think
we
can
close
this.
The
one
last
item
that
was
left
was
the
during
Reconstruction.
We
used
to
assume
that
all
of
their
Mount
points
and
that
was
removed
and
after
that
I
think
we
are
good
Michelle
and
if
you
have
but
I,
don't
see
any
other
place
in
the
code
where
we
assume
that
the
yeah
Michelle.
A
C
A
D
C
A
E
D
Yeah,
so
we
don't
have
a
lot
of
progress
on
this
right
now.
I
think
it's
fair
to
say
that
it's
not
going
to
make
it
into
128,
so
we
should
definitely
take
it
out
of
that.
We
probably
need
at
least
another
couple
of
weeks
to
figure
out
what
we
want
to
do
with
this
I've
said
in
the
past.
We
are
definitely
interested
in
doing
this
work.
That's
still
the
case.
We
just
need
to
find
somebody
to
work
on
it.
A
D
A
A
A
A
A
A
D
Sonic
the
question
for
you:
I
think
we
were
targeting
this
for
128
I
doubt
we
are
going
to
be
able
to
make
it
in
128
at
this
point,
I'm
not
sure
what
the
status
of
the
work
is,
but
we
had
kind
of
discuss
the
possibility
that
a
few
folks
need
help.
Then
we
can.
We
can
contribute
some
resources
to
towards
the
Upstream
code.
Implementation
for
this
cap,
so
I
think
you
had
said
you
were
going
to
put
together
a
list
of
work
items
just
wanted
to
see
where
we
were
with
that.
C
G
A
Yeah
I
think
we're
going
to
keep
it
marked
as
128
for
now.
I
think
the
benefit
here
is
that
most
of
the
changes
here
will
likely
be
out
of
tree,
but
at
the
next
meeting,
depending
on
where
things
land,
we
can
slip
this
to
129.
you're
right,
most
likely
it'll
select
129.
But
let's
see,
let's
wait
another
cycle
before
we
update
it.
A
A
F
F
C
A
A
E
C
A
A
A
G
A
F
Yeah
I
just
see
a
lot
of
people
from
AWS
here,
so
I
would
like
to
ask
them
if
they
can
look
at
those
PRS
and
maybe
have
this
review.
All
of
both
of
them
were
open
for
half
a
year,
at
least
and
from
my
point
of
view,
they're.
Okay,
to
merge.
However,
somebody
from
bws
is
asking
for
wants
to
do
a
review
on
AWS
side
actually.