►
From YouTube: Kubernetes SIG Storage - Bi-Weekly Meeting 2023-06-01
Description
Kubernetes Storage Special-Interest-Group (SIG) Bi-Weekly Meeting - 01 June 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
Hello,
everyone.
This
is
June
1st
2023.
This
is
the
kubernetes
story,
stick
meeting.
We
will
be
going
over
1.28
spreadsheet
today,
so
the
next
deadline
is
June
8th.
That's
the
production,
Readiness
freeze,
so
if
you
have
an
enhancement
targeting
1.28,
then
you
need
to
have
the
prr
section
filled
out
ready
for
review
and
then
one
week
after
that,
June
15th.
That's
that's
the
enhancement
phrase.
A
Okay,
thanks
yeah
just
make
sure
you
have
that
prr
ready
by
the
eighth
okay.
A
A
Next
one
voting
group
API,
so
this
one
we
are
still
wrapping
up
the
development
work
and
we
are
staying
Alpha.
We
probably
don't
have
to
track
it
track
this
for
1.28
and
we'll
just
cross
this
out.
A
A
Let's
see
masaki
or
takafumi
are
you
here
today.
Let
me
show.
A
So
the
next
one
is
see
if
they
want
a
house,
so
this
one
we
are
still
waiting
to
add
E2
test.
So
there
is
a
contributor
looking
into
this.
Let's
see
she's
a
still
wrapping
up,
so
we
want
to
Target
beta
in
this
release.
A
So
we
we
discussed
this
in
the
data
Protection
One
group
meeting
yesterday
yeah,
so
we
there
was
a
there
was
a
POC
done,
so
this
is
definitely
making
good
progress.
I.
Think
the
the
team
says
that
I
don't
want
to.
C
A
Well,
so
yeah,
so
so,
basically,
if
we
want
to
follow
the
the
cap
freeze
deadline,
this
is
not
going
to
make
it,
but
because
that's
that's
coming
really
soon,
just
two
weeks,
but
since
this
is
Auto
3,
we
can
still
work
on
it
so
yeah.
So
we
can
check
again
because
I
still
have
not
heard
the
consensus
just
to
see
just
to
say
whether
we
want
to
talk
it
out
or
not
right
so,
but
we
definitely
will
continue
with
the
design.
A
C
The
the
Prototype
and
POC
proceed
well
this
coming
month,
but
we'll
talk
about
that
offline
I'm
sure.
Thank
you.
Yeah.
A
So
I
think
the
let's
see
I
probably
should
update
this.
A
Thank
you,
and
next
to
my
runtime,
assist
in
the
mountain,
so
I
think
that
I
have
not
heard
from
deep
yeah
yeah.
You
heard
anything.
E
A
Next
One
enable
privileged
containers
for
Windows
to
replace
Cesar.
Proxybo
windows
looks
like
we
have
a
new
owner
menu.
D
Yeah,
so
we
we
have
started
reviewing
the
current
cap
that
Mauricio
has
and
we're
trying
to
understand
what
is
the
scope
of
the
work
that
needs
to
be
that
remains
and
that
we
need
to
do.
Our
goal
is
to
probably
set
up
some
kind
of
checkpoint
with
with
Mauricio,
either
over
slack
or
in
person
sometime
next
week
and
and
then
I
think
that
will
inform
our
next
tips.
A
And
next
one
is
see
some
aggressions.
A
Is
this
I
forgot?
What's
the
statuses
there's
a
someone
started
this
one.
A
Okay,
so
those
are
just
for
tracking
and
and
this
oh
I,
don't
know
why
this
one
says
done:
okay,
so
maybe
I'll
just
say
because
I'm
not
sure
what
this
is,
the
the
sap
RBD
send
out
an
email
deprecating.
It
I,
don't
think
there
is
a
PR
out.
A
It's
actually
right
so
I
don't
know
what
it
we
probably
need
to.
Maybe
we
need
to
change
some
of
the
messages
or
something
it's
basically
just
application
first,
and
then
we
have
to
wait
for
a
few
I.
Think
it's
a
three
right
three
releases
before
removing
the
code.
Oh
I,
also
remember
last
time
is
that
in
last
meeting
Gene
mentioned
something.
Is
there
any
potential
user
for
this,
but
but
I
have
not
heard
anything
up
after
that.
I
know:
I'll
chat
with
the
homework.
E
Humble
has
BR
to
emit
the
warnings,
if
you,
if
you
create
a
bot
or
PV,
no
just
a
pot.
That's
not
very
useful.
E
A
A
We
don't
have
YouTube
tasks
for
this
one,
yet
I
think
Deepak
won't
have
time
right
now,
but
maybe
later
so
this
one
we
put
it
put
it
here,
I'll
hold
next
one
is
the
better
default
story.
Class.
E
We
are
finished,
Roma
is
finishing,
the
gap
single
field
there
and
yeah
should
be
already
soon.
Ish.
E
E
A
F
We
met
on
that
earlier
this
week
and
for
continuing
design.
We
aren't
going
to
get
anything
in
128.
A
Okay,
so
you
think
we
just
designed
it.
F
Cool
thanks,
I
appreciate,
yeah
I
think
we
are
setting
up
a
meeting
to
look
at
like
the
current
annotation
based
implementations.
F
That's
something
Sunny
is
getting
sorted
out.
Foreign.
E
I
want
mute,
so
it's
the
same
like
last
week.
E
B
Yeah,
this
is
design
only
we
don't
have
like
we're.
We
had
some
updates,
but
we
still
need
to
answer
the
questions
that
Sig
apps,
posted
and
I
think
some
of
them
were
responded,
but
we
are
trying
to
work
through
the
the
open
items
on
the
the
cat,
so
yeah.
A
Next
one
is
the
inauguration,
so
we
are
trying
to
move
this
to
GA,
and
so
the
cap
is
updated
in
reviewed
and
then
E2
tests
are
in
progress.
B
A
Oh
looks:
let
me
show
it's
not
on
the
call
today
right
so
I'm
not
sure
if
they
are
ready
to
Target
the
alpha.
A
So
there
is
a
there
is
a
cap
out,
but
the
author
didn't
put
on
any
Milestones
didn't
didn't
put
on
when
they're
targeting
Arthur
or
anything
it
could
be
just
his
enough.
Medium
is
the
process,
so
just
pin
pinned
him
I
just
added
a
message
on
case
cap
asking
him
about
that.
A
C
E
Is
your
file
CSM
migration,
sorry
Azure
file,
removal.
A
Yeah
I
remember:
I
asked
Michelle,
so
what
happens
is
that
they
actually
missed
the
lock
the
feature
state
or
something
misses
something
that.
B
E
A
E
A
A
Okay,
we
can
Let's
check
this
out
to
the
meeting.
E
A
Okay,
so
that's
all
we
have
today
and
we
don't
have
any
other
topics
added
here.
Are
there
anything
else
folks
want
to
discuss
here.