►
From YouTube: Kubernetes SIG Storage Meeting 2022-12-01
Description
Kubernetes Storage Special-Interest-Group (SIG) Meeting - 01 December 2022
Meeting Notes/Agenda: https://docs.google.com/document/d/1-8KEG8AjAgKznS9NFm3qWqkGyCHmvU6HVl0sk5hwoAE/edit#heading=h.a4oc0xnjnezo
Find out more about the Storage SIG here: https://github.com/kubernetes/community/tree/master/sig-storage
Moderator: Saad Ali (Google)
A
A
So
we're
gonna
go
through
the
agenda
today.
First
up
we're
gonna,
go
through
the
126
planning
spreadsheet
and
get
a
final
status
update
on
the
items
that
are
going
into
the
126
release.
The
upcoming
deadline
is
the
release
date,
which
is
December
6th
next
week,
so
coming
up
very
quickly,
so
we
just
want
to
get
a
end
of
cycle
update
for
all
the
features
that
folks
have
been
working
on
then
we'll
go
over
PRS
to
discuss.
A
If
you
have
any
PRS
or
designs
that
need
review,
please
feel
free
to
add
them
or,
if
there's
anything
else
that
you
want
to
add,
feel
free
to
add
to
the
agenda
and
we'll
get
to
that
afterwards.
So
with
that
we'll
go
ahead
and
switch
over
to
the
planning,
spreadsheet
and
start
getting
status
updates.
A
B
B
C
B
I
opened
a
PR
that,
like
I'm
working
on
test,
I
open
a
PR
that
refactored
some
of
the
mock
tests
and
then
I
have
a
PR,
not
I
have
I
don't
have
a
period,
but
I'll
have
a
peers
soon
in
order
to
that,
actually,
as
the
the
new
tests
I'm
working
on
them.
So
as
soon
as
the
Master
branch
merge
opens,
we
should
have
this.
These
two
things
done
like
22.,.
D
A
A
B
I
think
there's
still
a
bunch
of
issues
related
to
mount
points.
I
think
I,
I
Michelle
knows
some
and
then
there's
a
issues
during
Reconstruction
when
we
assume
why,
when
we
assume
the
volumes
are
Mount
points
and
we
don't
properly
reconstruct,
sometimes
so
yeah,
we
still
have
to
fix
those
things.
As
far
as
I
know,
I
think.
If
we
look
at
the
last
like
update,
there
will
be
some
updates
on
this.
This
one.
A
E
E
A
F
F
E
C
D
F
A
F
D
A
D
F
A
A
C
A
E
A
D
D
E
C
D
E
A
E
A
E
E
E
A
B
Actually
this
is,
there
are
two
different
stories.
This
is
a
bit
of
confusion.
We
should
track
them
differently,
one
is
to
run
route,
run
cubelet
without
root
and
that
that
is
a
different
cap
and
there's
a
second
cap
is
the
one
that
we
were
talking
in
the
last
meeting,
which
is
like
enable
username
space
inside
Cube
and
yeah.
B
So
the
last
time
we
had
folks
from
signal
presenting
the
enabling
username
space
in
cubelet
and
I
tested
I
tried
to
use
that
feature
and
if
it's
it's
release,
Alpha
in
the
last
release,
but
I
found
that
it
doesn't
actually
work
with
any
configuration.
Any
combination
of
container
runtime
and
analytics
kernel
right
now,
either
there
are
bugs
in
container
runtime
or
bugs
in
Linux
kernel.
B
A
A
C
I
Would
like
to
bring
that
back?
Yes,
if
there's
openness
to
actually
moving
forward
like
I,
can
outline
the
design
in
more
detail.
If
that
would
help
people
understand
it
better.
I
mean
I
still
think
that
the
the
pr
as
is,
is
okay
to
merge
and
it's
what's
what's
missing,
is
sort
of
an
understanding
of
the
rest
of
the
the
rest
of
the
design
so
yeah.
If
people
want
to
see
that
merge,
I'll
work
on
it.
E
E
E
H
D
E
B
E
G
A
B
D
A
A
Cool
thank
you
John
and
with
that
we'll
switch
back
to
our
agenda
and
first
up,
we
have
a
PR
from
deep
I
think
this
is
the
one
that
you
mentioned
p
deep,
around
runtime
assisted
mounts,
so
that
needs
to
be
reviewed.
Please
help.
Take
a
review.
Take
a
look
at
this
anything
else.
You
want
to
add
deep.
A
C
So
far
we
have
been
resisting
because
that
makes
the
PVCs
not
portable,
but
it
doesn't
stop
the
people
from
requiring
death.
So
I
don't
know,
has
anything
changed
in
this
area
or
is
it
still
the
same
I
linked
the
previous
discussion
on
Disco
two
years
ago
and
also
like
five
years
of
old
tip
that
was
almost
merged,
but
then,
in
the
end
nobody
really
wanted
to
implement
it.
E
C
That
what
you
mean
yes,
I,
think
if
I
remember
correctly,
that's
the
last
status
it
introduced.
What
was
the
conflict
map
and
user's
name
space
and
then
a
PVC
would
start
a
route
that
points
to
a
storage
class
and
to
the
conflict
map
so
and
somehow
managing
the
parameters
from
both.
But
that's
it's
complicated
from
Atomic
cluster
admin
perspective,
because
some
storage
class
parameters
could
be
dangerous
and
they
need
to.
The
question
means
they.
C
C
H
D
C
H
Yeah
I
I,
it's
I
mean
it's,
it's
it
it.
We
haven't,
decided
anything.
So
there's
still,
you
know
plenty
of
opportunity
to
change,
but
the
touch
of
the
direction
is
it's
going.
Is
they'll
we'll
be
driver,
specific
parameters
like
number
of
iops,
so
yeah
instead
of
like
classes,
it
should
be
kind
of
General
parameters.
H
F
They
don't
want
to
have
to
have
special
logic
to
deal
with
every
different
platform
or
infrastructure
that
they're
using
I
was
actually
watching
or
not
watching.
I
was
I
was
looking
at
some
slides
of
talk
and
I.
Think
it
was
someone
from
it
was
like
a
maintainer
of
the
kubernetes
Cassandra
operator,
I
believe,
and
they
were
saying
that
you
know
portability
is
key
to
them
and
you
know
they
actually
specifically
called
out
like
PVC
being
portable,
as
kind
of
you
know
really
kind
of
key
to
to
letting
them.
F
H
A
Yeah
and
I'll
I'll
say
big
plus
one
to
Michelle.
I
know
portability
is
hard.
I
know
it
makes
it
difficult
to
not
be
able
to
add
arbitrary
things,
but,
like
Michelle
said
very
eloquently,
you
know
it
is
what
makes
kubernetes
attractive.
You
write
your
application
deployment
once
and
kind
of,
don't
have
to
worry
about
it.
So
let's
try
and
hold
up
that
principle.
If
we
can
okay
sure
with
that,
let's
move
on
to
the
next
item:
copying
PVC
annotations.
C
So
again,
people
come
and
ask
for
a
way
how
to
transfer
the
PVC
labels
or
something
doesn't
need
to
be
usable
into
a
label
in
the
cloud.
So
they
can.
They
can
see
what
is
what
and
in
similar
fashion
transfer
labels
from
BBC
to
PVS.
So
they
can
filter,
PVS,
better
and
again,
I'm,
resisting
because,
like
peace,
labors
and
peace
be
available
as
they
are
different,
they
are,
they
have
different
purposes,
but
I
think
there
should
be
some
way
how
to
transfer
some
labels.
Some
selected
name
labels.
C
C
C
B
B
A
A
C
H
Yeah
so
I
actually
figured
these
previous
two
topics
were
going
to
fill
up
the
time,
so
it
would
be
better
to
make
a
meeting
for
next
week
to
discuss
the
cause.
Stuff
I
mean
I.
Think
as
mentioned,
it's
possible
that
this
is
actually
just
the
general
question.
We've
just
discussed
about
passing
on
my
driver,
specific
parameters
or
around.