►
From YouTube: Kubernetes SIG Storage Meeting 2022-08-25
Description
Kubernetes Storage Special-Interest-Group (SIG) Meeting - 25 August 2022
Meeting Notes/Agenda: https://docs.google.com/document/d/1-8KEG8AjAgKznS9NFm3qWqkGyCHmvU6HVl0sk5hwoAE/edit#heading=h.lvbozfwix3l0
Find out more about the Storage SIG here: https://github.com/kubernetes/community/tree/master/sig-storage
Moderator: Saad Ali (Google)
A
Okay,
today
is
august
25
2022.
This
is
a
meeting
of
the
kubernetes
storage
special
interest
group.
As
a
reminder,
this
meeting
is
public
recorded
and
posted
on
youtube,
so
we
just
wrapped
up
the
125
release,
big
congratulations
to
the
sig
and
everyone
who
worked
hard
on
features
that
got
delivered
as
part
of
125..
A
Today
we
will
spend
some
time
reviewing
those
features
and
seeing
what
landed,
what
didn't
land
moving
items
that
didn't
land
into
126
and
adding
any
new
items
to
126
that
you
feel
like
should
be
part
of
126.,
so
I
just
copied
over
the
spreadsheet
125
to
126,
and
we
can
start
going
over
that.
The
exact
timeline
for
126
is
still
tbd,
so
the
release
team
is
being
put
together
for
126
and
the
exact
schedule
will
be
announced.
A
So
I
anticipate
that
this
is
going
to
be
the
last
release
of
the
year.
So
my
guess
is
that
this
release
will
be
sometime
in
december
or
so
before.
I
continue
any
any
questions.
Comments,
concerns.
A
Okay
feel
free
to
add
to
the
agenda
as
we
go.
If
you
have
anything
that
you
want
to
discuss,
we
can
come
back
to
it
after
going
through
the
126
spreadsheet,
okay,
so
switching
back
to
126
here,
there's
going
to
be
two
goals.
One
is
for
the
items
that
are
completed
just
getting
final
status
and
then
figuring
out
if
we
want
to
move
them
to
126
or
not
and
let's
get
started.
So
let
me
add
a
column
here
for
8
25
22.
A
Okay,
so
first
item
here
is
delegate
fs
group
to
csi
drivers
instead
of
cubelet.
This
was
moving
to
beta
last
status.
Update
was
csi,
spec
pr,
updated
anything
new
on
this
one.
B
No
no
update
still,
I
need
to
validate
if
moving
alpha
to
g8
breaks.
Anything
and
the
csi
spec
needs
to
merge.
First.
A
B
B
No,
so
I
think
we're
not
sure
right
now
we
still
have
like
some
issue.
We
still.
I
need
to
just
double
check
whether
we
because
another
another
two
related
amount
points,
pr
already
merged,
which
is
speed
up
like
the
amount
and
how
to
check
mount
point.
B
There's
one
issue
left
thing
that
I
filed
on
github
recently
is
that
we
are
not
doing
volume
reconstruction
properly,
because
we
expect
the
slash
mount
node,
publish
part
to
be
a
mount
point
and
so
that,
basically
any
csi
volume
is
not
reconstructed
properly.
If
the
node
is
rebooted
as
a
result,
we
are
leaving
files
on
the
node.
B
C
A
A
And
same
thing
for
storage
capacity,
tracking
for
pod
scheduling,
I
believe
this
was
successfully
moved
to
ga
any
objection
to
removing.
A
Okay:
next
item
is
csi
ephemeral
volumes,
existing
api,
moving
that
to
ga
docs
were
merged
blog
completed
any
anything
new
here
and
or
anything
remaining.
B
No
well
so
there
is
one
pr.
I
have
that's.
A
Got
it
and
what
was
the
pr
that's
remaining,
you
said
to
promote.
B
A
Got
it
so,
let's
do
this,
we
will
switch
over
to
125
for
the
sake
of
tracking
call.
This
done.
A
And
on
the
126
side,
we'll
change
this
to
wrap
up
test
work,
switch.
B
A
Okay,
next
up
is
spreading
over
failure.
Domains,
we
dropped
this
last
cycle.
Do
we
want
to
pick
it
up
again?
This
cycle.
C
I
think
I
we
need
to
finish
the
the
next
one.
The
wording
group
first
got.
A
It
so
I'll
go
ahead
and
remove
this,
and
then
we
can
reintroduce
it
when
appropriate
and
then
for
volume
group.
Do
you
still
plan
to
work
on
this
shane.
C
Yes,
so
I
have
got
some
information
from
other
vendors
who
has
implemented
this,
or
I
documented
that
I'd
like
to
bring
this
to
you
alpha,
I
mean
26..
Oh.
A
Okay,
so
we'll
move
that
from
design
to
alpha-
and
we
will
change
this
to
enhancement
needed
so
feel
free
to
throw
in
the
enhancement
issue.
When
you
get
a
chance.
C
A
All
right
next
item
are
the
csi
out
of
tree
drivers.
Moving
iscsi
driver,
fit
and
finish
anything
new
on
this
one.
A
I
think
this
was
complete,
I'm
assuming
there's
no
outstanding
work.
If
anybody
disagrees
feel
free
to
speak
up.
B
A
A
Okay,
if
not,
we
will
go
ahead
and
drop
it
provision
volumes
from
cross
namespace
snapshot.
Pvc.
Anyone
interested
in
picking
that
one
up.
C
Right
so
I
think
his
name
is
masaki.
I
think
should
be
here
somewhere
yeah.
We
should
check
with
him.
He
might
still
be
interested.
C
A
B
C
C
Beta
yeah
right
now,
it's
still
alpha
because
we
don't
have
e
to
e
test.
Yet
so
if
we
can
get
that
in
before
the
cap
merge,
then
we
can
go
to
beta.
C
Oh,
it's
actually,
the
the
phone's,
the
yeah,
the
second.
B
C
A
And
then
we
have
programmatic
response
for
csi
volume
health.
Anyone
interested
in
carrying
that.
C
Yeah,
so
there
is
one
person
I
yeah,
it's
actually
nick
runs
a
co-worker
who
might
be
interested.
I
just
need
to
confirm.
A
Okay
sounds
good,
so
we'll
keep
this
I'll,
keep
it
for
now.
Next
up
we
have
volume
populator
data
source,
which
was
also
dropped
last
cycle.
Anyone
interested
in
picking
that
one
up.
C
This
one,
I
think
so
it's
already
beta
all
right
so
before
we.
A
C
So
I
don't
know
if
we
are
ready
yet
so
maybe
that's
something
we
need
to
take
a
look.
Okay,.
A
So,
do
you
want
to
keep
it
around
and
should
look
into
that
or
just
drop
it
for
now.
A
So
I
think,
is
the
target
beta
or
keep
it
an
alpha,
this
cycle
and
fix
bugs.
A
A
C
Because
we
need
to
have
if
you
test
before
the
cap,
merge
that
line
right.
So
I
think
that
one.
I
don't
think
we
have
that
yet
yeah,
okay,
I'll
talk
to
him,
because.
C
This
test,
probably
what
we'll
need
to
have
that
apple
tree
so
probably
we'll
have
those
in
those
cozy
ripples.
A
A
B
Hey
yeah,
I
should
be
able
to
work
on
that
and
get
the
cap
in
a
better
shape.
A
Sounds
good
I'll
go
ahead
and
mark
this,
and
then
do
you
want
to
target
alpha
for
the
cycle.
A
A
Mauricio
didn't
have
time
last
cycle
to
work
on
it,
any
change
to
that
and
or
anyone
else
interested
in
picking
this
up.
A
Okay,
so
we'll
keep
that
around
for
now
jing
and
once
we
know
for
sure
we
can
add
or
remove
it
for
this
cycle.
A
Next
up
is
node
expansion.
Secret
was
this
able
to
land.
C
Yes,
so
this
is
ava.
C
Humble,
but
this
already
has
the
et
test
so
yeah
you
may
want
to
try
to
go
later
asking
it
has
a
to
it
test.
I
thought
so
I
oh,
we
can
double
check.
Okay,
well,
we'll
double
check
with
him.
I
mean
sounds.
B
B
C
A
Usage,
we're
gonna
start
seeing
bugs
okay,
so
let's
keep
it
opportunistically!
Okay,
if
there's
nothing
we'll
just
remove
it
and
for
the
move
to
chords.
Ga
mark
that,
as
done.
A
A
B
Zinc,
one
of
the
things
that
I
asked
in
the
chat
and
I'm
still
a
little
bit
confused
is
like.
Are
we
going
to
support
like
older
version,
we
said
that
okay,
entry
drive
volume
doesn't
support
older
version
than
7.0
youtube,
but
are
we
going
to
like?
But
if
you're.
C
Using
like,
I
think,
the
I
forgot
I
don't
know,
I
asked
this
one.
I
think
it's
when
the
older
version
go
out
of
support.
It's
like
being
you
know,
it's
like
the
wml
announcement
right.
Then
then
the
caesar
driver
cannot
support
that
anymore.
Something
like
that,
but
I
forgot
we
need
to
update
the
document
for
the
csr
driver
as
well.
C
We
have
not
well,
we
haven't,
we
still
need
to
qualify
with
1.5.25
right.
We
normally
qualify
that
after
the
the
release
right.
So
it's
it's
going
to
be
about
the
same
time
like
september
october.
That
time,
then
we
will
have
to
finish
qualifying
and
then
we'll
say
we
drop
that
because
it's
out
of
end
of
life
out
of
support
or
something.
B
C
C
So
so
that
off
offline
I
thought
I
really
would
have
replied
to
you.
C
But
I
think
my
understanding
is,
we
will
qualify
with
1.25
and
then
after
that,
we'll
update
the
the
document
saying
you
know
the
older
versions
end
of
support
yeah
at
the
time.
That's
around
the
same
time
in
october,
when
you
know
it's
officially
end
of
support,
because
right
now
we
can't
say
on
the
end
of
support
yet
because
it's
still
it's
still
there,
which
means
correct.
If
you
use
it
now,
you
can
still
use
it
now,
but
we
did
we
didn't
say
we
can
support
1.25
yet
right
because
we
have
not
finished
qualifying.
C
A
All
right
cool,
thank
you,
then.
Moving
on
azure
ga
was
dropped.
Last
cycle
actually
was
code
complete
and.
B
A
B
A
C
A
A
A
I
think
that
makes
sense,
so,
let's
give
it
one
more
release
then
hold
on
any
objections.
B
A
B
Need
to
keep
the
entry
driver
for
two
releases,
because
the
gtex
controller
must
be
able
to
detach
volumes
from
cubelets
old,
cubelets
and
cubots
can
be
two
versions
older.
A
Okay,
so
I
assume
this
is
going
to
be
picked
up
by
andy,
remove
entry,
azure
disk
driver
and
then
I'll
leave
azure
file
to
move
to
ga
and
then
aws
windows
support
to
ga
anything
new
here
was
this
able
to
land?
I
looks
like
it
was.
C
C
A
Okay,
so
then,
finally,
we
have
cluster
fs
entry.
Deprecation
is
deprecated
in
125.
So
I
think
the
next
step
here
is
to
remove
cluster
fs
for
126.
C
Yeah,
unfortunately,
we
don't
have
e2
tests
yet,
but
I
think
we'll
try
between
between
now
and
the
cap.
I'm
not
sure
when
will
be
the
camera
data
line,
but
we'll
try
and
see
if
we
can
get
if
you
test
there,
if
we
can
get
in,
then
we
could
target
data,
but
otherwise
you'll
just
still
be.
Do
you
test.
C
A
C
Yeah,
so
test
is
a
work
in
progress,
so
yeah
tentatively.
I
want
to
target
target
data.
A
Next
up
is
secret
protection.
Prevent
deletion
while
in
use
depends
on
in-use
protection
kept
below.
A
B
B
This
may
like
be
required
for
the
user
namespace
implementation,
because
that's
I
don't
know
if
they're
they're
planning
to
pick
it
up,
but
it's
they
actually
try
to
do
this
in
username
space
pr,
but
we
ask
them
to
drop
it
because
we
can't
have
like
just
for
user
namespace.
A
Okay
sounds
good:
next
is
non-graceful
node
shutdown.
A
Then
we
have
enable
user
name
spaces
in
cubelet,
so
uids
get
shifted
rootless
mode.
Anyone
interested
in
picking
that
up
again.
A
B
A
version
of
this
pr
was
merged
in
n125,
actually
like
click
and
the
username
space
implementation
as
alpha
feature,
so
the
gids
are
being
shifted
right
now,
actually
in
kubernetes.
If
you
have
this
feature
in
apple,
it
only
works
for
certain
volume,
tabs,
ephemeral
volume,
type
secret,
amplitude
and
all
it
doesn't
work
for
precision,
volume
types,
but
yeah
and
six
stories
was
asked
to
review
it.
So
I
will,
I
will
link
the
latest
one.
I
think
on
this
one
latest
enhancement
and
pr
there's
a
new
one.
A
A
A
A
Okay
thanks
a
month
next
is
cigaps.
Address
issue
where
pbc's
created
by
stateful
set
will
not
be
auto
deleted.
It
was
not
merged
plan
was
to
move
it
to
126.,
we'll
keep
it
in
126.
matt.
Are
you
still
planning
to
work
on
this.
A
Okay,
cool
so
we'll
keep
this
here.
Next
up
is
volume.
Expansion
for
stateful
set
any
updates
on
this
one.
There
was
a
kept
pr
out
awaiting
review.
I
assume
it'll
stay
and
design
this
cycle.
B
Yeah
there's
like
there's
another
person
who
was
trying
to
drive
it
and
we're
talking
in
slack
it's
it's
mostly
on
us.
Reviewers
like
they
to
to.
These
are
like
what
to
say,
there's
a
proof
of
concept.
Pr
that's
been
open
before
the
enhancement,
and
I
want
to
use
this
time
to
review
it.
I
haven't
had
chance
to
take
a
look
at
it.
B
C
C
C
It's
not
the
same
as
the
chalenes.
I
know
I
know
he
proposed
another
one.
He
proposed
another
cap
based
on
you
know
the
previous
one
yeah.
C
B
A
So
we'll
keep
that
in
design
for
this
cycle.
Next
up
is
execution
hook
for
application
snapshot.
This
was
dropped
last
cycle.
C
Yeah,
you
can
remove
it
for
now,
maybe
because
yeah
we'll
get
to
this
one.
A
Okay,
we'll
go
ahead
and
remove
it
for
now
and
then,
if
someone
wants
to
pick
it
up,
we
can
reintroduce
it.
Then
we
have
better
default.
Storage
class
was
targeting
alpha
last
cycle
code
was
merged,
doc
was
ready
for
review
blog
pending.
Does
anyone
remember
the
final
status
on
that
one?
The
block
is
merged.
B
A
mark
that,
as
done
and
for
126,
we
will
say
beta
and
then
I'll
add
a
comment
that
says
we'll
consider
using
two
data,
this
cycle,
and
if
that
changes,
we
can
go
ahead
and
remove
it.
A
Thank
you
yawn.
Next
we
have
handle
per
volume,
csi
driver
capabilities,
so
this
was
awaiting
volunteers
last
cycle.
Anyone
want
to
pick
this
up.
A
A
Okay,
so
I
think
with
that,
we
can
consider
our
126
planning
complete
if
you
end
up
with
any
additional
items
before
next
time
feel
free
to
reach
out
to
me
or
shing
or
michelle
or
yon,
and
we
can
help
get
them
added
here.