►
From YouTube: Kubernetes SIG Storage Meeting 2021-04-08
Description
Kubernetes Storage Special-Interest-Group (SIG) Meeting - 08 April 2021
Meeting Notes/Agenda: https://docs.google.com/document/d/1-8KEG8AjAgKznS9NFm3qWqkGyCHmvU6HVl0sk5hwoAE/edit#heading=h.qtu643prp9st
Find out more about the Storage SIG here: https://github.com/kubernetes/community/tree/master/sig-storage
Moderator: Saad Ali (Google)
A
All
right
today
is
april
8
2021.
This
is
the
meeting
of
the
kubernetes
storage
special
interest
group.
As
a
reminder,
this
meeting
is
recorded
and
published
on
youtube
so
on
the
agenda
today
we're
going
to
go
over
the
items
that
we've
been
working
on
for
the
121
release.
That
release
is
happening
today,
so
we
just
want
to
get
a
status
update
for
what
made
it
into
the
release
and
what
did
not,
and
next
time
we
can
do
planning
for
the
122
cycle.
A
So
if
you
have
any
items
that
you
want
to
start
working
on
in
122
bring
those
to
the
next
meeting
and
we
can
make
sure
that
they're
tracked
by
the
sig
and
appropriately
assigned
for
review
and
everything
in
the
meantime,
if
you
have
anything
else
that
you'd
like
to
discuss,
feel
free
to
add
to
the
agenda
doc.
The
link
to
the
agenda
doc
is
in
the
calendar,
invite.
A
All
right,
let's
go
ahead
and
switch
over
to
our
sig
storage
planning.
Spreadsheet,
make
sure
there
is
a
column
here
for
today.
Today
is
april.
8
21.,
first
item
that
we
have
here
is
delegate
fs
group
to
csi
driver
instead
of
cubelet
a
month.
Are
you
on
the
line.
B
Yeah
I'm
here
I
don't
have
any
new
update,
you're
still
blocked
on
serious
aspect
change.
I'm.
C
A
But
sounds
good
so
we'll
go
ahead
and
get
this
moved
over
to
122
and
mark
the
status
has
started
next
up
is
csi
online
offline
volume
expansion
last
status
update
here
was
made
some
fixes
we'll
have
more
changes
at
122
and
a
cap
for
recovery
for
failure.
Anything
new
here.
A
Perfect,
so
get
that
moved
over
to
122
as
well.
Next
is
recovering
from
resize.
Failures
seems
like
the
same
update
here
as
well.
B
A
A
Is
next
up
is
sc
linux,
recursive
permission
handling.
D
A
Makes
sense:
okay,
no
worries,
let's
we'll
try
to
move
it
to
122
and
see
if
we
could
find
someone
to
pick
this
up
next
item
is
the
csi
entry
read-only
handling
chang?
Are
you
on
the.
A
Line
so
I
don't
think
chenck
has
gotten
a
chance
to
work
on
this,
I'm
not
sure
if
he's
going
to
be
able
to
commit
to
it
moving
forward.
So
let's
move
it
to
122
and
see
if
we
can
find
a
new
owner
for
it,
maybe
chain
can
help
review
it.
A
Last
status
here
was
pr
was
reverted
due
to
a
race
between
pod
deletion
and
volume
management,
no
solution
yet
so
this
sounds
like
a
move
to
122.
Anybody
want
to
add
a
new
status
or
anything
additional
here.
A
A
So
last
status
here
was
review
and
progress
in
external
provisioner
end-to-end
test.
Merge.
Does
anyone
know
if
those
reviews
were
merged
or
the
they're
still
in
progress.
E
A
Okay,
so
two
pr's
open
trying
to
merge
by
end
of
week
and
cut
releases
by
after.
A
Okay.
Next
item
is
pvc
online
ephemeral
volume
work
with
csi
drivers.
This
was
completed,
so
you
can
mark
that
as
done
next
up,
we
have
spreading
over
failure
domains.
This
was
a
design.
It
was
dependent
on
the
next
item.
So
move
that
to
122.
A
A
Sounds
good
next
item
is
csi
out
of
tree
move,
iscsi
driver
fit
and
finish.
This
has.
A
A
michelle
or
karen.
Are
you
on
the.
C
A
Okay,
let's
say
we're:
gonna
move
this
to
122
and
hopefully
get
a
final
status
on
this.
I'm
gonna
go
ahead
and
mark
it
as
started.
A
Next
item
is
pvc
volume
snapshot
namespace
transfer?
This
was
a
design
for
this
quarter.
There's
been
some
meetings
that
been
held
so
far
sounds
like
move
to
122
would
be
the
most
appropriate
here.
Christian,
yes,
perfect.
A
A
Next
item
is
csi
volume,
health
last
status,
update
here
doc.
Pr
is
in
progress
working
on
removing
agent
logic
from
external
health,
monitor
anything
new
here,
shane.
F
This
is
done,
we're
just
wrapping
up
and
planning
to
cut
our
release
of
the
sidecar
next
week.
F
But
I
also
get
some
some
new
requests
making
rolling
house
available
so
that
the
controller
can
do
some
reaction.
So
I
think
I
will
schedule
some
meeting
to
get
more
requirements
on
that.
A
G
Yeah,
the
all
the
code
has
been
moved
into
new
repos,
I'm
getting
the
initial
review.
G
Check-In
completed
someone
already
found
a
bug
and
submitted
a
pr
to
fix
it,
which
is
great,
but
we
haven't
set
up
things
like
the
the
proud
jobs
or
some
of
the
other
stuff.
So
so,
there's
a
lot
of
just
initial
repo
bootstrapping
we're
driving
towards
an
alpha
release
in
the
next
couple
of
weeks,
so
that
we
can
get
to
beta
in
in
122..
A
A
G
Okay,
sorry
go
ahead,
I
was
gonna
say
if
no
one's
here
I
can
just
report
that
there's
a
lot
of
work
going
on
in
the
in
the
design,
meetings
and
updates
are
happening,
but
I
don't
know
if
we've
reached
any
concrete
new
milestones.
G
makes
sense.
Oh,
and
also
I
should
mention
that
every
other
monday,
the
they're,
using
the
meeting
as
like
there's
like
an
introduction
for
new
people
who
just
want
to
come
and
learn
about
it.
I
don't
know
if
it's
last
monday
or
next
monday,
but
they're,
trying
to
encourage
people
to
come
and
ask
questions
and
join.
A
That's
awesome
so
yeah,
if
you're
sitting
on
the
sidelines
and
wondering
how
to
get
involved
with
the
cozy
project.
This
would
be
a
good
opportunity.
They
hold
meetings
twice
a
week
on
mondays
and
on
thursdays
on
thursdays.
It's
right.
After
this
meeting
and
on
mondays,
you
can
look
at
the
sig
storage
calendar
to
find
the
exact
time.
So
it
looks
like
every
other
monday
they're
using
that
meeting
to
introduce
new
people
to
the
project
so
good
way
for
folks
to
get
involved
if
they're
interested.
A
Sounds
good
next
item
is
new,
read,
read,
write
once
access
mode.
E
Chris
yeah,
so
the
cap
for
that
all
the
fields
required
for
alpha
are
filled
out.
I
got
some
preliminary
feedback
and
I'm
addressing
that.
A
Next,
up,
update,
topology
labels
from
beta
to
ga
last
status
here
was
working
on
azure
file.
Pr,
layla
or
jawway
are
either
of
you
on
the
call.
A
A
Sounds
good
seems
like
we've,
made
good
progress
here
and
we'll
continue
that
in
the
next
cycle,
csi
migration-
another
one
with
a
lot
of
good
progress.
Joey,
you
want
to
talk
about
this.
One.
H
Yeah,
so
I
think
from
last
time
I
we
don't
have
much
updates,
but
yeah.
We,
I
do
have
a
lot
of
planning
stuff
to
do
in
1.22,
especially
on
deprecating,
some
of
the
the
plugins
that
will
not
support
csi
migration.
A
Perfect,
and
is
there
any
entry
driver
that
you
haven't
gotten
some
owner
to
pay
attention
to
that
you
need,
if
so,.
H
H
Yeah
most
most
of
the
drivers,
I
I
have
already
like
create
an
issue
in
kubernetes
and
add
their
owners.
C
H
Namely
so
first
is
seth
fest
and
seth
rbd.
So
I
know
I
know
humble
is
working
on
this,
but
I
couldn't
reach
out
to
him
and
he
he
seems
not
replying.
So
this
is
what
the
first
one
and
the
second
one
is
gloucester
fs
and
I
believe
the
owner
is
also
humble,
and
so
I
think
if
he
he
can
reply,
then
we
can
decide.
H
What's
the
next
step
for
that
and
besides
that,
we
also
have
a
core
bait
callback,
combat
driver,
yeah
and
that
one
I
I
pinned
the
qual
by
csi
driver
owner
and
hopefully
they
can
get
some
reply
on
that.
A
H
A
If
anybody
on
the
call
knows
someone
who
is
very
interested
or
owns
the
ceph
entry
driver
code
or
the
gluster
code
or
the
qobike
code,
please
reach
out
to
jaway
he's
trying
to
plan
the
transition
of
the
entry
drivers
to
csi.
A
So
please,
please
reach
out
to
him
he's
holding
meetings
on
friday
for
csi
migration.
It
would
be
good
to
get
those
owners
involved
thanks
joey,
and
so
I
guess
now
we
want
to
get
status
updates
for
each
of
the
drivers.
The
cloud
provider
drivers
we've
got
vsphere
up
first
last
status
here
was
support
for
67u3
will
be
in
release.
2.3,
which
is
work
in
progress,
need
to
follow
up
on
csi
windows,
support.
F
Yeah,
so
that's
still
true
and
also
jaiway
mentioned
that
we
also
need
to
update
the
topology
label.
So
we're
going
to
do
that,
one
as
well
in
1.22,
please,
okay,.
A
So
I'll
say:
move
to
123
update
topology
label
22..
Oh
yes,
thank
you
and
we'll
say
that
started
azure
disk.
We
skipped
for
this
cycle.
Azure
file
move
to
beta
issues
will
be
fixed
later.
I
have
the
issues
been
fixed
here.
H
I
know
last
time
there
is
a.
There
is
a
regression
issue
about
other
file
secrets
and
I
I
see
that
it's
already
been
revert,
but
that
doesn't
impact
csi
migration.
I
guess
I
don't
know
if
michelle
do.
You
know.
C
Basically,
no,
I
think
the
so.
The
revert
of
the
astrophile
regression
is
basically
causing
csi
migration
to
be
broken
for
inline
volumes,
and
so
andy
is
working
on
a
fix
for
that.
A
Okay
looks
like
this
will
be
work
that'll
get
carried
through.
Do
we
have
like
a
partially
working
partially
broken
in
121?
Then.
A
H
Everything
is
going
on
schedule
for
gke,
so
we're
still
we're
still
turning
on
csi
migration
by
defaulting
1.21
for
gke,
and
also
we're
we're
doing
some
more
sesame
migration,
upgrading
testing
in
our
jke
environments
and
for
gce
we're
like
it's.
It's
still
working
as
expected,
like
we're,
we're
still
working
on
the
cube
cup,
cube
up
script
change.
C
C
A
All
right
thanks
a
lot
joey
for
the
update,
looks
like
we'll
mark
that
as
started
and
get
it
moved
over
and
then
finally,
we
have
cinder
last
status.
Here
is
beta.
D
A
D
A
All
right,
the
next
set
of
items
are
co-owned
by
sig
storage
as
well
as
other
cigs.
First
up
here
is
sig
node
co-owned
ungraceful,
node
shutdown.
This
was
a
design
for
this
quarter.
Last
status
update
was
that
we'll
update
the
cap
here
shang
any
updates
on
this.
A
G
C
A
All
right,
thanks
ben
next
item
is
enable
user
namespace
in
cubelet,
so
uids
enable
username
spaces
in
kubelet,
so
uids
get
shifted,
mauricio
or
hamant.
Any
updates.
A
A
Here
all
right
next
up
is
volume
expansion
for
stateful
sets.
We
need
a
new
owner
for
this
one.
A
I
A
Next
up
is
execution
hook.
The
last
status
update
here
was
reviewed.
A
new
api
proposal
need
api
review
again
anything
new
here,
shane.
F
So
yeah,
so
the
cab
is
updated.
We
got
some
comments,
but
we
still
need
to
get
reviews
from
the
api
reviewers
yeah,
so
that's
status
and
moving
to
1.22.
A
Perfect
mark
that
as
started,
get
that
moved
over
next
item.
Is
the
kubernetes
mount
util
library
splitting
that
into
a
new
repo,
adding
end-to-end
tests
doing
a
formal
release
for
that
looks
like
we
haven't
really
gotten
any
updates
recently
for
any
of
that
work
last
status
was
he
was
waiting
on
this
mobi
library
to
be
updated.
Sereni,
I
guess
hasn't,
give
been
on
these
calls
yawn
or
does
anybody
else
have
an
update
on
this.
C
I
think
the
the
thing
that's
remaining
is
cleaning
up
the
old
location
and
like
removing
it
or
deprecating
it
there
and
that
is
blocked
on
moby,
changing
their
dependency
or
something
like
that
or
c
advisor
changing
their
dependency.
C
I'm
sorry
assad
you're,
muted,
if
you're
talking.
A
Oh
thanks
cool
sounds
good,
we'll
go
ahead
and
get
this
moved
to
122.
A
Thanks
michelle.
A
And
next
up,
prioritization
on
volume
capacity
is
done:
user
id
ownership
and
config
maps
and
secrets
co-owned
with
sega
auth
last
status.
Update
here
was
another
contributor
may
work
on
it,
so
it
sounds
like
that's
moved
to
122
and
hopefully
we
can
get
the
other
contributor
identified
and
anything
else
here.
A
A
I
don't
believe
it
was
targeting
ga
this
cycle
right.
This
is
targeting
ga
for
the
next
cycle.
A
Jinger
anyone
working
on
windows
on
this.
D
Here,
yeah
so
yeah,
we
are
we're
going
to
work
on
integrating
the
csi
proxy
version,
one.
We
we
we're
going
to
release
the
one
of
csi
proxy
and
integrate
it
with
gc
and
with
tdcsi
display,
and
hopefully
we
can
win
this
gga.
F
I
thought
it's,
I
thought
gene
said
this
1.21
ga.
I
think
she
just
said
that,
like
a
couple
days
ago,.
C
A
A
C
G
H
A
Perfect,
and
can
you
put
their
github
in
yeah.
A
All
right,
I
think,
with
that
we've
got
a
status
update
for
all
the
items
that
we
worked
on
in
121
and
thank
you
for
everyone.
Who's
worked
hard
on
this
release.
We
also
started
a
document,
capturing
kind
of
the
big
features
that
were
released
as
part
of
this
cycle.
A
The
highlights
here
are
immutable
secrets
and
config
maps
which
went
to
ga
storage
capacity
tracking,
which
went
to
beta
generic
ephemeral
volumes,
which
went
to
beta
azure
file.
Csi
migration
to
beta
csi
service,
account
token
to
beta,
and
then
volume,
health
monitoring
and
prioritizing
nodes
based
on
volume
capacity
to
alpha.
A
So
the
sig
is
accomplished
a
lot
for
this
121
release.
So
thank
you
all
for
your
hard
work
and
moving
forward.
We
are
going
to
do
planning
for
the
122
release
in
the
next
meeting,
which
will
happen
in
two
weeks.
A
The
exact
timeline
for
the
122
release
has
yet
to
be
finalized,
and
as
soon
as
it
does
we'll
surface
it
here,
but
roughly
in
the
past,
we
followed
a
three
month.
Cadence,
so
first
month
is
feature
free
second
month
is
code.
Freeze
and
third
month
is
the
release
we'll
see
if
we
do
a
three
or
four
month
cycle
this
time.
A
A
I
think
that's
all
I
have
for
this
meeting.
Was
there
anything
else
anybody
was
hoping
to
discuss
today.