►
Description
Kubernetes Storage Special-Interest-Group (SIG) Volume Populator Design Meeting - 15 December 2020
Meeting Notes/Agenda: -
Find out more about the Storage SIG here: https://github.com/kubernetes/community/tree/master/sig-storage
B
Okay,
hey
guys
welcome
to
the
kubernetes
sig
storage
volume.
Populators
meeting
looks
like
we
have
a
small
crowd
today.
B
I
just
wanted
to
follow
up
on
two
two
items
from
last
week
that
we
were
not
able
to
resolve
and
talk
about
talk
about
the
holidays
and
when
we're
gonna
get
back
together
and
we
can
discuss
progress
as
well.
The
first
the
first
issue
was
one
of
naming.
So,
as
we
discussed
last
week,
there's
I
found
five
different
places
where
this
new
controller
will
introduce
the
user
visible
names
into
the
system.
B
There's
the
name
of
the
crd
itself,
the
the
name
of
the
controller
that
will
run
in
the
system.
All
of
the
rbac
objects
are
named
after
the
controller,
but
they
they
all
have
names.
There
is
the
the
source
of
the
events
that
the
controller
will
be
generating
and
then
there's
the
event
reason,
and
before
I
get
too
far
down
the
path
here,
I
wanted
to
get
all
the
names
right.
So
what
I
have
been
calling
these
things
volume
populator.
B
You
know
we
started
off
with
generic
data
populator,
but
I
think
that
that
was
sort
of
confusing.
First
of
all,
generic
doesn't
doesn't
really
help
ordinary
users
understand.
What's
going
on,
it
was
more
helpful
to
us
as
a
sig
to
distinguish
it
from
you
know
things
like
cloning
volumes
and
snapshots,
and
then
I
think,
adding
the
word
volume
what
was
helpful
to
describe
what
is
being
populated,
but
the
controller
name.
B
So
last
week
the
proposal
came
up,
maybe
call
it
data
source
controller
or
maybe
even
to
change
the
word
controller
to
something
else
like
validator
verifier.
Something
because
controller
implies
that
it's
going
to
be
you
know
enforcing
some
mechanic,
and
all
we're
really
doing
here
is
just
watching
them
and
generating
events.
So
to
call
it
a
controller
is
a
little
bit
grandiose.
B
So
I
I
I'm
still
sort
of
mixed
between
sticking
with
the
name
populator,
because
that's
what
it's
looking
at
and
we're
calling
it
this
data
source,
something
because
again
it's
it's
responsible
for
basically
validating
data
sources
of
pvcs.
Sod
you
weren't
here
last
week.
Do
you
have
any
feelings
about
this.
C
I,
like
the
volume
populator
name
for
the
crd
for
the
crd
and
then
so.
Is
there
any
kind
of
push
back
to
including
volume
populator
in
the
controller
name.
B
Those
are
the
volume
populators
in
my
mind
like
if,
if
we
were
to
write
a
a
controller
that
allowed
you
to
you
know
one
of
our
canonical
examples
pointed
at
a
github
repo,
so
some
crd
that
represents
a
github
repo.
Then
you
create
a
pvc
that
points
to
that.
Cr
that
refers
to
a
github
repo,
then
there's
a
populator
controller
that
would
populate
that
specific
pvc.
But
that's
not
what
we're
talking
about
we're
talking
about
the
one
that
that
tells
you
when,
when
you
have
an
invalid
data
source.
C
B
C
B
A
So
you
see
this
one
in
the
future
to
have
like,
expand
it
or
to
do
something
else.
More
than
validation,.
B
Well,
my
vision
of
populators
is
that
you
know
each
each
kind
that
you
can
populate
from
will
have
its
own
controller.
B
That's
not
tied
to
csi
that
just
you
know
takes
a
crd
and
populates
from
it
like
and
we're
hoping
that
you
know
the
the
backups
are
one
of
those
things
down
the
road.
You
know
the
whole
motivation
for
this
is
to
enable
restoring
from
backup-
and
that
needs
to
be
something
that
can
stand
alone
as
a
backup,
populator
backup,
restore
controller
whatever
you
want
to
call
that
thing.
C
A
B
The
the
possibility
of
wanting
to
do
some
level
of
validation
on
the
volume
populator
crds
themselves,
for
example,
maybe
to
detect
collisions
between
two
two
volume,
populators
that
refer
to
the
same
group
kind
like
that
warrants
like
a
warning
of
some
kind,
but
like
the
way
to
handle
that
would
be
some
sort
of
a
validating
web
hook,
not
not
a
controller.
B
So
so
this
thing
really
has
a
very
limited
responsibility,
and
it's
limited
to
just
you
know
when
we,
when
we
flip
the
the
feature
gate
on
and
people
start
creating
pvcs
with
other
data
sources,
we
just
want
them
to
know
hey.
You
know
this.
This
pvc
isn't
going
to
get
bound.
Okay,.
C
B
Yeah,
I
don't
know
I
mean
I
don't
want
to
go
too
nuts
about
the
name,
but
I
I
just
wanted
to
get
it,
something
that
wasn't
just
me
making
things
up
data
source
validator
I
do
like
because
it's
very
specific,
but
that's
what
it
is
doing,
is
looking
at
the
data
source
and
it's
checking.
If
it's.
If
it's.
B
I
guess
so
I
mean
this
comes
back
to
the
you
know.
How
does
how
does
the
kubernetes
community
push
distros
to
include
things
that
are
not
in
the
tree
you
know,
and
if
assuming
we
can
convince
them
to
include
this,
the
crd
and
this
controller
and
his
our
back
objects
in
all
of
the
distros
starting
when
121
or
122
or
whenever
we
declare
this
beta,
then
like,
if
we
rename
it
after
that,
how
much
of
a
hassle
is
that
going
to
cause
for
all
those
distros.
B
A
B
A
B
If
we
can
live
with
data
source
validator
as
a
controller
name,
I'm
cool
with
that
and
then
the
rbac
objects
could
be
similarly
named.
How
about
the
the
event
source
could?
Would
that
also
just
be
the
controller
name.
B
B
B
A
B
Down
these
notes
after
the
meeting
to
save
time
so
shane
this,
I
I
saw
some
updates
from
you
on
the
external
provisioner
bug:
five,
five,
three
or
five
three
three,
but
the
wrong
number.
A
A
It
was
using
a
canonical,
I
mean
canary
canary
images,
yeah.
C
A
B
Yeah,
I
just
wanted
to
make
sure
that
was
not
going
to
have
problems,
okay,
so
that
that
was
an
easy
one.
As
for
so
so
progress
on
on
the
various
changes,
I
have
not
been
making
a
ton
of
of
changes.
I
haven't
pushed
another
commit
to
to
the
hello
populators
repo,
yet
for
the
hello
populator
repo
yet,
but
I'm
still
working
on
the
sort
of
splitting
apart.
The
I
mean
there
is.
B
There
is
a
new
commit
that
sort
of
refactors
everything
to
show
the
the
latest
way
that
that
I'm
doing
populating,
and
it's
actually
simpler
than
the
example
that
I
showed
a
couple
weeks
ago,
because
it
doesn't
clone
the
pv
it
just
rebinds
the
pv,
and
that
allowed
me
to
remove
a
couple
dozen
lines
of
code
but
yeah,
I'm
still
trying
to
find
the
line
between
the
the
reusable
library
piece
and
then
the
the
hello
populator
piece,
which
will
just
be
a
sample
that
sits
on
top
of
the
library
and
so
hopefully
I'll
have
more
on
that.
B
B
If
not,
if
no
one's
been
looking
at
the
code,
that's
fine
I'll
be
making
updates
later
this
week
and
then
the
only
other
order
of
business
is
when
to
meet
again.
So
we
have
holidays
next
week
and
the
week
after
and
so
logically,
I
would
want
to
cancel
both
of
those
meetings
and
have
our
next
meeting
be
january
5th,
and
hopefully
there
will
be
substantial
progress
by
then
hopefully
yeah.
That
sounds
good
to
me
all
right,
so
we
had
a
problem
over
thanksgiving.
C
I
can
go
ahead
and
delete
it,
and
I
think
that
should
send
out
the
calendar
updates
and
in
the
agenda
just
go
ahead
and
mark
it
as
cancelled
for
each
of
those
dates
to
make
it
clear.
B
Yeah
yeah
I'll
update
the
agenda,
so
if
you
could
cancel
both
the
22nd
and
the
29th,
then
we'll
meet
up
again
on
the
fifth
and
we'll
have
more
to
talk
about
by
then
okay
done
thanks
son,
anything.