►
From YouTube: Kubernetes SIG Storage - Bi-Weekly Meeting 2023-05-04
Description
Kubernetes Storage Special-Interest-Group (SIG) Bi-Weekly Meeting - 04 May 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
Okay,
so
I
just
copied
the
spreadsheet
for
1.27
to
1.28.
If
there
are
any
other
items
you
want
to
Target
for
1.28,
please
add
it
to
this
spreadsheet.
So
I'll
just
go
over
this.
The
first
one
is
recover
from
resize
failure
command.
Are
we
going
to
Target
this
to
Beta
or.
B
We
still
still
stay
in
Alpha
and
because
we
couldn't
get
the
aphs
merged
so
but
most
of
the
API
changes
were
are
like
written
down
so
I
just,
but
it
still
remain.
Alpha.
B
B
Yeah,
but
we
had
this
API
changes
proposed
in
127
which
moves
around
the
existing
fields,
so
we
cannot
move
it
to
Beta
in
128
without
getting
those
API
changes
merged.
First,
oh.
A
A
All
right
all
right
so
basically
I
guess
the
focus
would
be
to
get
the
API
margin
I'm
going
to
turn
a
then,
and
we
can
change
this.
One
saying
get.
A
B
I
think
so
it's
it's
the
New
York,
so
I'm
gonna
call,
but.
A
Yeah,
okay,
let
me
show
or
sunny
okay.
Okay,
if
you
are
still.
C
A
Change
this
a
little
bit
all
right,
so
next
one
issues
related
to
Austin
Williams
among
points.
This
is
a
this
is
a
bug
fix
three
hatching
here.
B
A
A
Okay,
thank
you
for
the
update
next
one
is
foreign
group
snapshot
so
yeah,
so
this
one
is
Alpha.
We
are
still
wrapping
up
the
implementation
in
the
some
snapshotter
repo.
So
it's
going
to
be
staying
in
Alpha.
C
D
Hey
hello
now
is
no
no
updates.
Today,
oh.
A
Okay,
do
you
I,
guess
I
I
believe
there
are
some
painting
work
in
the
volume
popular
people
to.
A
D
A
To
just
say,
working,
proper
calculator
or
just
use
this
to
track
this.
C
A
And
next
one
is
a
boarding
house
additional
metrics,
so
this
one
I'm
not
sure
if
we
can
Target
the
beta
yet
because
we
still
have
this
e
to
E
test.
So
maybe
I
will
add
a
note
for
myself
to
follow
up
on
this
one.
A
And
next
one
is
the
change
block
tracking,
okay,
I,
don't
see
E1
or
Prasad,
okay,
so
I
think
we
would
like
to
move
this
one
to
other,
but
I
like
to
check
with
me.
First,
we
still
haven't
designed
discussions
in
the
data
Protection
One
group,
so
I'm
going
to
say
wow
to
this
one.
A
Next,
one
is
the
newly
write
on
the
access
mode,
the
red
one's
access
mode.
So
this
one
okay,
I,
don't
know
if
we
are
planning
for
Gan
I
mean
we
need
to
wait
for
a
release.
C
A
A
Xy
is
the
runtime
of
system
mounting
I,
do
not
know
if
deep
is
planning
for
anything.
A
A
Of
okay,
is
this
a
I.
A
C
G
So
I
think
I
I
need
to
sync
up
with
Mauricio
again,
but
Mauricio
doesn't
really
have
time
to
work
on
this
anymore.
Okay,
so
if
you
know
anyone
else
is
interested
in
this
and
also
wants
to
potentially
take
this
forward,
I
think
that.
D
Hi
Michelle:
this
is
Manu
from
AWS,
so
we
we
may
be
interested
in
evaluating
the
work
that
is
required
to
implement
this.
Can
you
or
Mauricio
provide
us
some
context
in
terms
of
what
is
the
current
status
of
this
effort
and
also
What
what
the
scope
of
the
work
is,
and
we
can
make
a
call
at
that
point
in
terms
of
whether
we
can
contribute
something
to
this
or
not?
Okay,.
G
C
G
Sounds
good
I'll,
I'll,
poke,
Mauricio
and
maybe
I
think
there
is
a
time
slot
set
up
for
like
a
weekly
windows.
D
There
wasn't
enough
participation,
is
my
understanding,
so
I
think
that
meeting
got
canceled,
but
we
are
happy
to
sync
with
you
and
and
see
you
know.
Like
I
said
you
know,
we
may
be
interested
in
collaborating
on
this
I.
Just
don't
know
what
the
scope
of
the
work
is
and
and
we'd
like
to
understand
that
before
we
can
commit
to
anything
sure.
G
D
A
Okay.
Next
one
is
a
new
experience,
Secret,
okay,
so
it's
a
I
think
humble
is
here
right!
Oh
no
home
is
not
here,
okay,
but
this
one
just
moved
to
beta.
So
we
probably
need
to
wait
for
One
release.
Then.
F
And
now
it's
being
disabled
because
it's
broken
anyway
I
will
see
if
what
the
status
is
and
anyway
I
will
not
move
it
to
GA,
because
I
need
to
wait
for
One
release
anyway,
so
it
was
in
beta.
Okay,.
C
C
A
So
should
change
this
one
sheets:
okay,
yeah,
it
is
beta,
but
then
okay,
we
just
started
again
right,
started,
started.
A
Okay,
so
maybe
beta
D4
or
something
like.
A
A
G
I
think
it's
planned,
there's
actually
a
PR
there's
a
PR,
that's
disabling
the
the
future
Gates,
but
we're
asking
the
author
to
also
just
remove
the
whole
plug-in
so
I
think
it's
planned!
Yeah,
okay,.
F
Do
you
also
plan
to
remove
the
whole
cloud
provider?
That's.
G
I
think
we
at
least
so
far,
at
least
in
this
PR
we're
scoping
it
to
just
the
volume
plug-in
I
think
for
the
entire
cloud
provider.
That's
a
discussion.
We
need
to
have
with
Walter
on
that.
A
So
I
believe
they
actually
started
that
discussion.
I
heard
they
talk
about
that
one
at
kubecon
they
may
have
some
meetings
for
Club
providers,
yeah.
A
A
A
A
A
Humble
was
saying
that
there
isn't
really
any
customers
using
the
entry
stuff
already
plug-in.
So
no
I
was
just
wondering.
If
that's
the
case,
should
we
actually
look
at
this
one?
Do
we
really
need
to
go
go
to
GA?
Is
that
even
necessary,
or
should
we
just
remove
it
duplicate
it,
and
if
that's
easier,
that
that's
something
maybe
let's
see
if
he
has
any
update
on
this
one
say
that
working
on
it
yeah
but
I
mean
there
are
no
customers,
I
mean
I,
don't
know.
A
A
F
A
C
A
A
Yeah,
that's
that's
exactly
what
I'm
asking
why
I
just
feel
bad.
Let
me
just
move
this
one
too,
to
beta
on
by
default.
A
C
A
And
okay,
so
seven
of
us
yeah,
we
I
think
humble,
send
out
that
email,
I,
don't
remember.
Seeing
any
response.
Did
you
guys
see
any
response
for
that.
A
F
A
And
next
one
is
the
port
portworx
entry
driver,
so
right
now
it
is
off.
By
default.
I
came
to
Grant
to
see
if
they
are
interested
in
Windows
2
on
by
default.
He
said
not
in
1.28.
Maybe
in
1.29
I
also
asked
him
if
there
are
actually
any
customers
using
it,
he
said
he
has
to
actually
have
customers,
but
they
need
to
do
thorough
testing.
Let's
have
this
node
here.
A
Okay,
so
next
one
is
this:
always
honor,
reclining
policy
I
need
check
and
check
with
dependency
for
yes
time
to
add
E3
test.
Basically,
that's
what
is
left
there.
A
Next,
one
is
a
comparable
mode
conversion,
so
controllable
conversion.
So
this
one
is
beta
in
1.27,
so
I
believe
we
need
to
wait
at
least
one
release,
or
maybe
even
two
before
we
move
this
one
to
ga.
A
F
A
A
A
G
Yeah
we're
still
in
design
discussions
right
now,
but
yeah.
We
want
to
try
to
Target
this
if
possible.
Okay,.
G
C
A
Okay
and
this
okay,
do
we
Okay
this
one
that
looks
like
I
think
Jonathan
have
some.
F
A
All
right,
thank
you
and
okay.
Next
one
is.
We
already
talked
about
this
okay,
so
PV
last
phase
transition
time.
Okay,
this
this
is
the
one
that
we
actually
got
the
cap
merged
by,
but
didn't
have
time
to
do.
Is
that
right
so
so
trying
to
Target
Alpha,
but
then
we
removed
it
because
we
don't
think
Roman
didn't
got
time
to
right.
Okay,
I
think
that's
the
status.
A
A
Oh
this,
this
is
the
this
is
Arthur.
A
So
should
we
on
okay
remove
this,
you
need
to
double
check.
C
A
A
B
I
think
we
are
still
trying
to
do
the
design
we
are
I
spoke
with,
like
we
have
been
making
progress,
obviously,
but
we
still
have
some
roadblocks
to
solve
and
yeah
I
think
the
person
who
was
assigned
to
it
rlr.
He
said
he
just
disappointed
that
he's
busy
too
end
of
this
month,
but
I
will
try
to
describe
something.
Let's
see,
okay,.
A
Thank
you
and
okay.
The
next
one
is
I
need
to
check
with
Oshkosh
just
to
see
if
he
has
time
to
work
on
the
eating
test.
Voucher.
A
So
the
next
two
I
I
think
we
okay,
so
those
are
all
signaled
items
broncoupled
without
root.
A
Those
have
your
names
on.
Do
you
know?
Are
there
any?
Are
they
targeting
anything
for
this?
Two?
The
next
two
features
are
all
no
signaled.
A
A
So
look
at
the
timeline
the
so
the
release
cycle
begins:
May
15th,
the
prr
for
that
we
need
to
get
the
prr
ready,
June,
8th
and
then
the
enhancement
phrases
June
15th.
But
then
one
month
after
that,
it's
code
free.
So
this
between
this-
and
this
is
just
one
per
month,
all
right.
A
E
There,
yes,
yes,
it's
real
hello,
hey
thanks
for
having
me
I'm
Marianne
I'm
from
the
II
team
in
New
Zealand
and
we've
been
working
on
conformance
testing
of
the
API
for
kubernetes
for
at
least
from
2019..
E
When
we
started,
we
were
sitting
at
25
percent
and
what
happened
at
that
stage.
Is
the
Performance
Group
looked
at
the
test
requirements
there,
so
I
believe
there
for
the
test
requirements
and
they
said
I
can
let
storage
aside
for
a
while,
because
we're
not
100
sure
if
it
conforms
to
all
the
requirements
of
conformance
testing
and
we
reached
100
of
all
the
other
endpoints
in
March
this
year
and
now
we're
swinging
around
to
all
the
other
ineligible
endpoints.
E
E
So
what
we
would
depreciate
from
this
group,
if
we
could
have
a
review
of
the
endpoints
by
the
group
and
the
Specialists
we
saw
all
around
here
in
the
group-
can
tell
us
whether
we
are
correct
to
assume
that
these
endpoints
do
conform
to
the
requirements,
because
they
they
can't
be
vendor
specific.
They
can't
be
calling
specific
operating
system
goals,
they
have
to
be
not
using
Cube,
cuddle
and
so
on
and
so
forth.
If
you
go
to
you'll,
see,
there's
a
lot
of
requirements
there.
E
So
if
we
can
get
some
agreement
from
this
group
that
there
is
none
of
these
that
should
not
be
tested,
we
will
go
ahead
and
write
tests
for
those.
So
we
do
the
test
writing.
But
if
there's
anybody
that
willing
to
help
here
with
writing
tests
everybody's
busy,
but
if
there's
somebody
passionate
about
test,
writing
or
you've
got
an
intern
that
wants
to
help
with
that.
So
the
process
for
conformance
for
those
that
do
not
know
is.
You
first
have
to
write
an
EQ
test,
get
that
approved
by
the
city
architecture
group.
E
There
was
a
sub
project
for
conformance
running,
but
at
the
moment
we
merged
the
meeting
with
sick
architecture,
where
there
is
input
about
the
test,
whether
the
test
is
actually
properly
exercising
the
end
point
in
a
way
that
reflect
the
operation
of
the
endpoint
and
then,
when
this
agreement,
the
test
is
doing
what
it
should
be
doing.
We
merged
it
into
into
the
code
base.
Then
we
track
it
on
the
test
grid
for
two
weeks.
It
is
not
allowed
to
flick
at
all
for
two
bits.
E
If
it
does
flag,
we
need
to
figure
out.
Why
fix
the
flake
put
it
back
in
and
as
soon
as
we
have
two
weeks
flag,
free
proven,
we
could
go
ahead
and
promote
the
endpoints
4.4s,
which
would
basically
mean
it
will
then
be
included
in
the
the
con
performance
test.
Suite
run
by
solo
boy
for
anybody
that
wants
to
put
a
debonairs
performance
badge
on
their
box.
E
I
will
also
send
out
this
information
through
your
mailing
list.
If
it's,
okay
and
we'll,
then
the
other
big
ask
is,
we
will
come
back
with
the
tests
to
this
group
for
approval,
because
we
are
definitely
not
experts
on
storage.
E
So
please
feel
free
to
help
us
in
the
right
direction
and
we
hope
that
it
would
be
a
bit
of
a
cumulative
curve
as
soon
as
we
start
knocking
out
the
first
few
and
figure
out
the
correct
patterns
for
testing
storage,
that
it
will
go
faster
and
we
hope
to
have
these
done
properly
by
the
end
of
the
year.
D
We
we
would
be
happy
to
collaborate
on
this
I
I,
don't
know
what
the
scope
of
the
work
is
at
this
point,
but
this
sounds
like
something
that
given
the
fact
that
you're
looking
for
some
somebody
to
help
out
I
think
we
should
be
able
to
at
least
contribute
some
bandwidth
towards
these
tests
and
and
helping
you
in
this
work.
So
so,
if
you,
if
you
can
reach
out
either
over
slack
or
email
or
whatever
we
can,
we
can
figure
out
what
the
next
step
should.
E
Be
accordingly,
that
would
be
really
really
helpful
if
you
just
drop
your
slack
name
in
in
the
agenda
or
the
in
every
chart.
Yeah.
G
Cool,
maybe
I
can
also
provide
some
context
on
this
I
think
in
the
past
we
have
considered
conformance
tests
for
storage,
and
one
of
the
challenges
of
say,
like
an
end
to
one
conformance
workflow
is
that
it
does
require.
You
know
the
sum
operating
system
and
potentially
storage
system
requirements,
because
it
needs
to
mount
and
and
do
operations
like
that,
and
so,
like
I,
think,
there's
a
thread
there.
G
There
has
been
a
thread,
an
old
thread
about
like
having
some
optional
conformance
Suite
for
for
for
storage
or
for
stateful
workloads
that
has
these
kind
of
additional
requirements,
but
I
think
what
you're
talking
about
here
is
a
little
bit
different.
G
G
So
then,
this
is
a
little
different.
This
is
actually
these
tests.
The
purpose
of
these
tests
is
to
test
that
the
kubernetes
cluster
is
able
to
serve
these
apis
and
to
serve
the
endpoints,
but
it
doesn't
necessarily
need
to
test
the
whole
end-to-end
functionality
of
the
system.
E
C
G
Yeah
so
I
think
in
terms
of
like
previous
efforts
here,
I
know
for
some
of
our
recent
features.
In
the
last
couple
of
reasons,
we
did
create
some
conformance
tests
for
the
CSI
driver,
endpoint
I,
don't
remember
if
we
actually
promoted
those
to
conformance
or
not,
but
I
think
those
tests
might
be
a
good
place
to
start
as
sort
of
like
a
sample
and
then
extend
it
to
the
rest
of
the
storage.
Api
endpoints.
D
Yeah
I
think
I
think
it
would
be
a
good
idea
to
have
a
more
comprehensive
set
of
storage
conformance
tests,
as
Michelle
was
pointing
out
and
I.
We've
thought
about
doing
some
work
in
that
space.
But
we
haven't
really
had
time
to
prioritize
that
so
far.
So
I
think
if
there
is
interest
here
in
enhancing
the
capabilities
as
part
of
those
tests.
B
D
We
can
certainly
look
into
doing
that.
G
Yeah,
let
me
also
in
the
agenda,
notes
I'll
link
to
the
old
discussion.
We
had
about
functional
conformance
tests
and
we
can
try
to
continue
the
discussion
there,
but
yeah
I
guess
in
the
interim.
The
closest
thing
we
have
is
we
have
the
the
storage
end-to-end
test,
Suite
that
can
be
plugged
into
a
number
of
providers.
E
G
E
C
G
Is
the
API
conformance
test,
which
is
what
your
is
primarily
looking
at,
and
then
there
is
this
like
functional
conformance
test,
which
is
another
sort
of
aspect
of
it
all
right.
E
Right,
thank
you
very
much,
I'll
appreciate
that
we
will
go
and
have
a
look
at
that
CSI
driver,
endpoints
and
I
believe
like
we
found
we've.
We,
the
apps,
was
totally
open
last
year
with
just
right
now
this
and
once
we
started
on
that
and
they
discovered
the
patterns
for
their
specific
resources,
and
it
actually
rolls
quite
quickly
once
you've
got
a
pep
and
established.
E
So
if
people
can
help
us
establish
that
pattern,
we're
more
than
welcome
to
more
than
happy
to
do
the
work
and
a
little
bit
forward
and
we'll
also
do
all
the
the
administration
and
chasing
up
the
the
test
grid
and
making
sure
that
the
thing
is
passed
and
monitor
that
and
do
the
promotion.
So
we
try
to
do
as
much
of
the
work
as
possible.
If
we,
you
can
just
share
all
the
knowledge
that
we
need.
A
All
right,
thank
you.
Thanks.
A
Okay,
so
the
next
one
I
just
want
to
give
a
quick
update,
yeah
and
I
were
at
kubecon,
so
we
have
a
six
story
session
there
actually
yeah,
it
was
pretty
good
I
had
some
great
questions
from
the
audience.
There
was
also
a
DP
working
group
session.
One
is
virtue.
A
We
also
had
a
a
Meetup
at
the
contributor
Summit,
it's
a
small
number
of
people,
and
then
we
also
had
a
meter
grid
for
new
contributors,
so
yeah.
So
that's
that
was
good.
D
I
had
one
question
we
had:
we
were
working
with
Matt
and
sunny
on
the
Qs
related
provisioned
IO
cap,
and
we
had
left
some
feedback
on
that
cap
and
we
didn't
really
see
any
updates
on
on
that
cap
recently.
So
I
was
wondering
if
you
know
what
what
the
next
steps
there
should
be
about.
That.
G
Yeah,
let
me
sync
up
with
them.
They
are
still
actively
working
on
it.
They
just
recently
got
pulled
into
some
things
in
the
last
few
weeks,.
D
Got
it
yeah,
I
think
last
we
heard
from
on
on
that
subject.
They
had
said
that
they
were
going
to
try
and
address
the
feedback,
so
I
just
wanted
to
kind
of
make
sure
that
that
was
still
the
plan
or
not.
Yes,.
A
So
remember,
there
was
a
dog
that
they
are
capturing
some
requirements.
I
don't
know
if
this
is
the
right
one
or
it's
a
different.
Is
there
another
dog?
Maybe
this
looks
like
the
old
one
I
believe
there
was
another
dog
at
the
end.
They
actually
captured
some
requirements
or
from
different
storage
systems,
looks
like
that's
not
linked
here.
A
But
this
was
but
there
was
also
a
talk.
There
was
a
but
I,
don't.
C
G
Going
on
yeah
I
think
in
the
CSI
spec
PR
there
might
be
a
link
to
a
different
dog.
G
A
I
think,
let's
see,
is
that
this
one
right:
okay,
let's
see
this
is
the
this-
is
the
there's
a
Google
doc
somewhere
yeah
I.
A
G
C
D
A
A
Yeah
so
I
know
that
she
so
I
added
something
from
vsphere
point
of
view
and
I
believe
she's
also
trying
to
collect
something
for
for
Seth
I'm,
not
sure.
If
that's
that's
there
yet
or
maybe,
or
maybe
from
Pure
Afghan
reserved.
We
mentioned
a
few
vendors
that
she
said
she
will
collect
some
feedback,
yeah,
so
I
believe
it's
a
it's
ongoing
and
it's
just
maybe
not
everything
is
showing
here
in
this
issue.
D
Yeah,
that's
fine,
as
long
as
folks
are
working
on
that
I
think
that's
great
to
hear
so.