►
Description
Kubernetes Storage Special-Interest-Group (SIG) Volume Populator Design Meeting - 02 March 2021
Meeting Notes/Agenda: -
Find out more about the Storage SIG here: https://github.com/kubernetes/community/tree/master/sig-storage
B
Let
me
ask
you
a
lot
of
sources.
Let
me
ask
yeah,
let
me
ask
a
different
question
so
and
I
apologize
because
that
my
memory
for
details
is
terrible.
If
we
leave
the
existing
behavior,
where
we
auto
clear
it
and
we
add
the
populators
we
follow
through
with
that
cap
in
pr,
the
populators
allows
you
to
have
any
source
as
long
as
that
source
is
registered
right.
B
That's
consistent
so
anyway,
the
point
I
was
getting
to
is:
if
we
really
have
to
take
the
slow
path
on
the
bug
fix,
we
could
and
that
doesn't
actually
affect
the
populator's
change
right
correct,
so
it,
for
example,
hey
you're
not
allowed
to
put
core
objects
here,
I'm
going
to
throw
an
annotation
on
your
object
and
then
clear
it
like
we
always
did
before
and
now
we
can
go
through,
say
march
of
2022
go
through
the
fleet
of
gke
and
whoever
else
wants
to
participate
and
say
hey.
Is
anybody
actually
doing
this
right?
B
If
they
are,
then
we
have
different
data
and
if
they're
not,
then
we
are
safe
to
proceed
right.
I
don't
really
want
to
be
talking
about
this
again
in
a
year,
but
that's
the
safer
path.
So,
but
if
we
go
that
avenue,
we're
not
saying
that
all
the
popular
work
has
to
wait
for
another
year,
also,
okay,
correct.
A
A
B
A
A
Because
what
the
feature
gate
does,
is
it
basically
relaxes
the
admission
controller's
behavior
of
zeroing
out
the
field?
What
we're
adding
in
121
is
a
separate
controller
that
is
going
to
watch
your
pvcs
and
warn
you
when
they
have
data
sources,
that
that
don't
match
something,
and
that
controller
only
makes
sense
when
we're
not
zeroing
out
the
field.
So
we
have
to
put
the
emission
controller
into
beta
so
that
we're
not
zeroing
out
the
field
and
then
letting
and
then
this
other
controller
will
start
warning
you
that
hey
nothing's
going
to
bind
this
volume.
B
A
Right,
it
would
be
something
that
we
would
want
kubernetes
distributions
to
install
so
that
you
get
this
warning.
It
wouldn't
be
absolutely
necessary,
but,
like
the
absence
of
it
would
would
cause
bad
behavior.
So
we
would
write
a
blog
entry
saying
like
you
need
to
include
this
controller.
Much
like
what
happened
with
snapshots.
When
we
shipped
snapshots
you
had
to
install
crd,
you
had
to
install
a
controller,
you
know
we
we
encouraged
kubernetes
just
shows
to
do
that
and
it
didn't
happen.
A
A
B
So
it
jumps
to
beta
I'm
trying
to
think
through
what
are
the
risks
right?
What
happens
if
it
goes
sideways?
Well,
the
risk
here,
the
biggest
risk
here
is
you've
got
a
controller
that
starts
spamming.
Events
on
everything-
and
you
know
worst
case
like
makes
your
control
plane
unavailable
right.
It's
pretty
bad
worst
case
right
seems
unrealistic,
but
it's
it's
there
and
we
have
no
real
testing
on
it
except
you
know
whatever
you
all
have
done
by
hand.
A
A
A
So
there
were
a
few
other
feedbacks
that
you
put
on
the
kept
that
I
wanted
to
to
suggest
real
quick.
So
let's
do
it
the
one
about
metrics.
So
so
you
would
ask
about
what
kind
of
metrics
we
can
output
here
and
and
the
the
response
back
was
for
me
was
that
for
actual
populators
they
will
of
course
generate
their
own
metrics,
but
the,
but
the
metrics
that
I
think
are
going
to
be
most
useful
to
an
operator
are
going
to
be
the
one
that
you
suggested
in
particular,
was
like.
A
That
particular
time
elapsed
from
pvc
creation
to
pvc
bound
by
data
source
kind,
and
I
think
that's
also
kind
of
a
separate
effort,
because
that's
a
core
feature
to
enhance
that
metric.
That's
useful
for
all
kinds
of
reasons
not
just
for
the
populators
okay
is
that
is
that
a
reasonable
plan
to
that.
B
A
A
B
A
B
B
A
B
I
forget
what
I
was
getting
to
oh,
I
think
I
think
it
was
simply
like.
Are
there
security
implications
to
being
able
to
like
who
who
can
register
a
data
populator
and
you
you've
answered
you
cut
off
one
big
vector
by
just
saying
we
don't
accept
core
types
right,
but
could
I
find
a
way
to
the
reason
I
ask
for
for
sig
security
is
because
they're
good
at
coming
up
with
answers
to
the
questions
of.
Could
I
find
a
way
to
could
I
trick
your
controller
into
letting
me
register.
B
B
B
A
Yeah,
okay,
okay,
okay,
so
so
that
I
think
that
covers
the
your
feedback
and
and
responses
to
it.
So
if
you're
satisfied
with
all
that,
I
I'll
just
proceed
on
the
pushing
that
other
cap
and
then
so.
How
do
we
get
out
in
front
of
the
right
people
once
once?
We
have
the
other
cap
that
addresses
the
legacy
behavior.
B
We
can
tag
them
and
actually
we
can
bring
it
up
at
cig
arch
like
next
week.
Looking
at
the
calendar,
I
think
it
would
be
next
week.
Oh
shoot
next
week
is
next
week.
Code
free
is
next
week,
but
also
we're
going
through
perf
reviews.
So
I
have
a
conflict
I
can
maybe
make
maybe
make
it
happen,
the
11th
at
cigar.
So
if
you
have
a
cap,
that's
out
and
we
can
even
sort
of
preemptively
merge
the
fix
and
then
bring
it
to
cigarch
and
say
like
hey.
Is
anybody
gonna
scream?
A
Yeah:
okay,
okay-
I
like
that
so
so
I
can
have
the
the
kept
posted,
or
at
least
the
pr
for
the
cat
posted
today,
because
I'm
working
on
it
now
and
and
then
also
have
the
the
two
specific
code
changes
for
the
two
caps
for
the
core
repo
also
pushed
up
very
soon
this
week
and
get
them
reviewed
and
hopefully
merged,
and
then
okay
have
those
other
discussions
and
and
if,
if
someone
says
no,
no,
this
is
a
terrible
idea.
We
will
have
the
opportunity
to
back
it
out.
A
A
A
I
think
it's
already,
I
think,
there's
already
a
pr
against
the
external
provisioner
repo
I'll
have
to
double
check
that,
because
I
wrote
that
code
last
year
and
it's
just
been
sitting
there
so
yeah.
I
may
I
I'll
probably
ask
you
guys
for
some
reviews.
I
guess
that's
what
I'm
saying.
Yep
sounds
good.
Hopefully.