►
Description
Kubernetes Storage Special-Interest-Group (SIG) Volume Populator Design Meeting - 06 April 2021
Meeting Notes/Agenda: -
Find out more about the Storage SIG here: https://github.com/kubernetes/community/tree/master/sig-storage
A
How
do
I
know
whether
it's
recording
or
not?
Oh,
it
is
okay,
so
this
is
the
kubernetes
sig
storage
volume,
populators
weekly
meeting
main
thing
I
have
on
the
agenda
today
is
talking
about
the
the
new
repos
that
were
created.
So
two
weeks
ago
I
sent
out
the
request
for
two
new
repos
and
you
guys
approved
them.
Thank
you.
They
were
created
and
I've
moved
all
of
the
code
from
the
old
prs
into
these
repos,
and
we
can.
We
can
actually
look
at
them.
I
think.
A
A
I
had
to
create
some
new
boilerplate
stuff.
Like
my
own
copy
of
release
tools,
I
had
to
rename
some
things
and
move
some
stuff
around,
but
but
this
this
is
a
fully
working
repo
with
just
a
couple
of
commits
in
it.
This
one
has
unit
tests
or
at
least
a
decent
number
of
unit
tests,
but
we
don't
have
any
kind
of
like
change
control
on
it.
So,
like
I,
don't
know
how
to
make
the
unit
test
run.
A
For
example,
if
someone
pushes
a
pr
so
there's
that
repo
level
stuff
that
needs
to
be
figured
out,
you
know
that
we
have
the
code
here,
but
we
don't
have
any
kind
of
change,
control
or
automated
testing
setup
on
the
repo.
A
A
There's
no
release
tools
in
here,
because
it's
a
library-
and
I
don't
know
how
you
do
releases
of
libraries
to
be
honest,
because
there's
no
artifacts
that
get
produced.
B
A
Yeah
so
so
like
these
are
the
kinds
of
things
I
wanted
to
talk
through
and
figure
out,
because
I
do
want
to
get
this
code
reviewed
and-
and
I
want
to-
and
I
want
to
get
change
control
set
up
so
that
tests
have
to
run
and
people
have
to
press
approve
and
all
of
those
things,
but
but
these
these
two
repos
as
they
stand
like
I
I'm
on
the
the
aqua
list.
I
don't
know
where
the
ac
list
is
maintained.
To
be
honest,
maybe
it's!
This
is
this
owner's
fault
yeah.
B
You
are,
but
still
normally
should
not
be.
Checking
code
like
this
normally
should
be
go
through
like
the
pr.
B
Even
that
I
think,
when
we're
working
on
one
snapshot
in
the
beginning,
it
was
like
a
huge
pr
still
went
through
the
reviews.
Actually,
okay,
but
if
you
already
have
something
maybe
yeah
we
can.
Maybe
if
you
have
any
further
changes,
maybe
we
should
just
yeah
go
through.
A
Why
we
should
review?
What's
here
I
mean
I
don't
want
anything
to
escape
review.
Obviously
so
so
I
mean
we
can
always
go
back
and
look
at
like
the
the
commits.
So
there's
three
commits
in
this
library.
Two
of
them
were
by
the
infra
guys
and
this
one's
for
me.
So
you
can
look
at
the
commit
and
you
can
see
all
the
changes.
It's
a
there's.
I'd
say
the
vast
majority
of
it
is
actually
there's
no
auto
generated
code
in
here
is
there
so
everything
in
here
is.
If
I
look
through
this.
A
Why
are
these
not
showing
up?
Oh
the
go.some
files,
always
a
pile
of
garbage
controller.
This
is
all
the
code.
I
wrote
yeah
everything
in
here,
except
for
go.sum.
I
guess
is
code
that
I
wrote
so
it's
an
1800
line.
Change
should
be
reviewed
and
yeah,
so
I
I
don't
know
how
we
can
do
a
review,
but
if,
if
people
want
to
send
comments
and
say
like
this
is
bad,
we
need
to
change
this.
A
I
can
turn
that
into
a
pr
and
go
go
fix
it
in
in
a
in
a
proper
pr
and
but.
A
A
B
A
I
was
gonna
say
like
because
I
have
push
access.
I
can.
I
can
remove
this,
commit
from
master
and
and
change
it
into
a
pr,
and
we
can
review
it
and
then
merge
it,
but
but
yeah
it's
been
in
here
for
a
while.
So
so
the
the
main
things
I
want
to
do
is
I
want
to
figure
out
how
to
make
it
like
run
the
tests,
because
this
one
does
not
have
unit
tests.
Yet
that's
something
I
need
to
do
it.
Has
you
know
the
example
off
here
in
this
example
directory?
A
This
is
structured
very
much
like
there
was
another
example
that
I
copied
to
to
develop
this,
but
I
can't
remember
which
one
I
was
copying.
Oh,
I
think
I
was
copying
the
the
the
storage
library,
that's
in
kubernetes,
sigs
storage,
the
one
that's
used
heavily
by
the
external
provisioner
repo
there's,
a
gigantic
library
there
that
I
basically
modeled
this.
After
so
you
know
the
the
example.
You
know
that
everything
is
in
populator
machinery
controller.go,
so
you
can.
A
Just
you
know
include
this:
in
whatever
project
you
want
to
have
for
your
populator
and
you'll,
get
the
library
and
then
the
example
is
an
example
of
how
to
do
it,
and
then
there's
not
much
else
here.
You
know
we
just
need
the
the
automated
tests
and
then
machinery
so
that,
when
prs
gets
submitted,
we
can
run
some
sort
of
a
test
job
that
will,
you
know,
make
sure
that
there's
no
regressions.
So
we
got
to
figure
out
how
to
do
that.
A
For
for
this
library
and
then
for
this
one,
we
have
the
artifact
creation
and
with
the
make
file,
it'll
spit
out,
containers
and
and
stuff.
A
But
it
also
doesn't
have
any
kind
of
auto
it.
Has
the
unit
tests
checked
in,
but
no
way
to
run
them
and
again
I
don't
know
how
to
how
to
trigger
that.
So
if
there's
a
an
example
of
of
how
you
set
up
ci
jobs
for
repos,
I
need
to
follow
that
and
I'm
happy
to
do
that,
and
then
we
also
need
to
review
this
one.
So
in
this
one,
I
think
if
we
look
at
the
commits
there's
there's
three
commits
I
one
of
the
commits
was
just
a
automatic
one.
A
That
was
the
importing
of
the
release
tools.
Actually
two
of
them
were
importing
of
release
tools,
so
the
documentation
for
release
tools
said
to
run
a
command
and
I
ran
it
and
it
produced
these
two
commits,
and
then
this
this
top
commit
is
the
one
that
actually
contains
all
the
code.
So
in
here
it's
it's
a
3500
lines,
but
a
lot
of
this
is
auto-generated.
I
believe,
because
it's
yeah
all
the
the
volume
populator
crd
has
a
huge
amount
of
boilerplate
code
that
gets
generated,
and
then
the
controller
itself
is
rather
small.
So.
D
So
for
the
tests,
I
sent
you
a
link
in
the
chat,
basically
there's
ways
to
create
new,
proud
jobs,
and
you
can
go
ahead
and
add
a
new,
proud
job
for
this.
A
A
A
A
A
A
So
then,
the
the
next
order
of
business
after
we
have
ci
working
and
stuff
reviewed
is
doing
an
alpha
release.
B
B
Well,
there
is
a
talk,
actually
there's
a
talk
on
how
to
do
release
it's
under
where
I
can
find
that
I
maybe.
D
D
So,
at
a
very
high
level,
I
think
we
need
to
figure
out
the
versioning
if
we're
going
to
follow
december
and
do
major
minor
patch.
I
think
that
seems
reasonable.
D
A
D
A
A
D
Following
and
so
we
tried
to
do
an
rc
cut
off
of
the
off
of
the
release
branch
get
input
from
folks
for
a
few
days
two
to
three
days.
If
there's
any
anything
that
needs
to
be
fixed,
always
have
the
fixes
go
into
master.
First
cherry
pick
them
to
the
release
branch
and
then,
whenever
you're
ready
go
ahead
and
cut
the
official
final
release.
A
A
D
Cut
your
1.1,
you
would
have
a
release,
stash
1.1
branch.
If
there
was
a
bug
fix
that
needed
to
go
into
both
any
change.
First
goes
to
master
right,
and
then
he
would
cherry
pick
it
to
both
one
one
branch
and
the
one
zero
branch.
D
And
then
you
can
go
ahead
and
cut
a
patch
release
off
of
one
zero.
So
you
get
one
zero
one.
Okay,
then
same.
D
D
The
release
branches
are
minor
version
branches,
and
then
you
can
have
multiple
patch
versions
come
out
of
it
right.
B
D
D
D
C
A
C
C
A
Worked?
Okay.
So
so
I
I
try
to
follow
that
process.
I'll
read
this
this
doc
and
see
see
what
it
says
here,
because
because
yeah
I
was,
I
was
trying
to
do
the
the
right
thing,
but
it
appears
that
there's
just
some
bleeding
edge
stuff
going
on
with
with
that
release
tools,
repo
yeah.
D
Maybe
the
release
tools,
repo
should
have
releases
as
well.
A
A
Directories
in
my
file
system
route,
so
I
was
like
yeah,
I'm
just
going
to
go
back
to
something
that
actually
works
and
yeah.
D
The
the
main
purpose
of
that
release
tools
is
just
to
add
automation
around
the
whole
release
process
so
like
for
one
repo.
It's
not
a
big
deal
to
do
it
manually,
but
I
think
they
have
five
or
six
side
cards
that
they
have
to
release
for
and
it
becomes
a
absolute
hassle
to
manage
all
of
them.
So
they
created
this.
A
Yeah,
okay,
so
I
will
read
both
of
these
and
follow
up
with
you
guys.
If
I
have
any
questions-
and
it
sounds
like
both
of
you
guys
are
signed
up
to
review
these
repos
so
I'll
I'll
wait
for
feedback
on
there
and
when
is
the.
When
is
the
actual
timeline
for
kubernetes
121
to
go
out.
A
A
A
A
Because,
oh
actually,
I
can
just
copy
paste
the
links
you
guys
sent
me
here
into
the
agenda,
so
they'll
be
preserved.
For
anyone
to
come,
find
these
yeah
that'll
be
useful.
Okay,
then
I
I
guess
we're
done.
Those
were
the
ais
that
I
just
covered
for
myself
and
for
you
guys
cool
all
right.
Take
care.
Thank.