►
From YouTube: Kubernetes KubeBuilder Meeting 20210211
Description
KubeBuilder Meeting for 2021/02/11. See https://sigs.k8s.io/kubebuilder for more details.
A
As
a
reminder,
this
is
being
recorded,
so
don't
say
anything
you
don't
want
uploaded
to
youtube
and
saved
for
all
posterity
all
right.
I
think
we
have
two
items
on
the
agenda.
Let
me
double
check
and
pull
that
up
again:
yeah
two
items
on
the
agenda,
so
the
first
looks
like
a
check-in
on
cue
builder,
v3
and
the
blockers.
So
does
someone
to
take
that.
B
B
C
B
B
C
B
B
B
B
And
basically,
basically,
we
well
eric
submitted
a
pull
request
that
allows
us
to
create
the
some
of
the
required
binaries
for
tests
for
different
architectures,
not
only
for
the
hard-coded
ones,
and
it
listed
two
other
ones
in
the
in
the
documentation.
But
I
think
that
we
need
to
also
update
the
list
of
of
the
supported
architectures
in
in
google
cloud.
I
don't
know
who
can
do
that.
B
B
Maybe
today,
even
today,
because
the
documentation
we
can
always
update
it
afterwards,
as
it's
linked
to
the
to
a
different
branch
to
the
book
versus
three
branch,
so
we
actually
could
improve
the
documentation
afterwards.
So
I
think
that,
after
all,
the
issues
of
all
the
reviews
have
been
addressed,
and
I
think
that
camilla
already
did
that
we
should
be.
We
should
be
able
to
to
merge
this
one.
C
C
I
know
that
it's
boring
dude
she's
kind
of
behavior,
but
if
someone
has
time
to
you
know
be
so
free
to
make
all
suggestions
and
give
you
all
feedbacks
and
you
help
toward
him
better
as
well.
If
you
see
that
it's
possible
india
you'll
be
happy
as
soon
as
possible,
address
your
comments,
saying
yeah
and
then
he
I
in
my
humble
opinion,
don't
need
to
be
perfect,
but
if
he
it's
18
percent,
8
percent
90
is
good
enough
to
be
married.
I
think
we
can
address
any
other
concern
after
as
well.
I
agree
yeah.
D
C
B
And
after
we
merge
that,
there's
also
some
maintenance
work
to
do
about
creating
the
well
the
the
branches
created
the
person,
three
branch,
the
book
version-
three,
we
probably
have
to
move
it
to
to
the
same
as
the
release
and
we
have
to
link
the
domains
properly.
I
don't
know
who
has
access
to
that.
A
A
C
A
Yeah
so
there's
like
there's
a
thing
you
have
to
do
in
netlify,
basically,
and
so
it
just
depends
on
who
has
access
to
netlify
and
if
other
people
don't
have
access
to
netlify,
we
need
to
get
everybody
on.
That
list
is
supposed
to
be
trusted
and
with
with
stuff
like
with
stuff
like
netlify,
so
we
should.
We
should
get
you
all
access.
If
you
don't
have
it.
B
There
are
a
lot
of
maintenance
tasks,
I'm
sorry,
sorry
and
those
will
be
the
only
three
things
that
are
listed
as
in
the
milestone
for
version
3.0.0,
and
there
are
a
lot
of
issues
open
and
a
couple
pull
requests,
but
they
pull
requests.
I've
been
reviewing
them
and
they
don't
need
to
be
addressed
right
now,
and
I
don't
know
about
the
issues
I
don't
know
if
there
is
any
issue
that
should
be
addressed
before
version
3.0.0
or
if
any
of
you
guys
knows
of
anything
that
we
should
address
before
releasing.
D
D
D
B
C
A
D
A
D
This
this
justin
santa
barbara
guy-
I
don't
know
if
he's
on
the
call
or
not
but
he's
been
kind
of
hard
to
get
a
hold
of-
and
I
think
the
other
reviewer
on
here
has
I've.
I've
pinged
them
on
slack
and
I
think
they
responded
positively.
But
I
don't
know
if
they've
reviewed
it
or
approved
it.
Yet
obviously
they
haven't
approved
it,
but.
A
C
A
I
think
it's
I
think
it
may
actually
be
supposed
to
be
the
the
set
of
like
there's
a
thing
in
owner's
aliases.
That
says
cue
builder
admins,
that
is
just
the
very
old
copy
of
cue
builder
admins,
so
it
may
actually
supposed
to
be
overlap
with
cube
builder
admins,
in
which
case
I
I
I
my
plan
was
just
basically
to
ping
justin
and
be
like.
Do
you
mind
if
we
do
whatever
we
want,
because
I
I
think
I
can
give
approval
on
that
one
I
just.
A
B
The
thing
is
that
we
well
eric
asked
and-
and
we
agreed
to
not
merge
0.8.0
for
version
three
of
q
builder,
so
it
right
now
it
it's
not
super
super
super
high
priority.
It's
high
priority,
but
not
super
super
super
high
priority,
so
maybe
we
can
give
a
justin
a
day
or
something
or
or
well.
I
think
it
has
been
already.
C
D
C
If
you
be
able,
you
know
for
the
next
ones,
if
you
be
possible,
if
it
is
be
helpful
in
today,
we
ng.
Could
you
put
yours
like
to
approval
just
to
approach
this
kind
of
city
thing
just
see
the
bunk
stop?
Would
you
be
nice
as
well
before,
don't
be
boring?
If
you
didn't,
you
know
just
just
so,
which
is
kind
of
small.
C
B
Okay,
the
the
I
could
say
that
we
should
set
a
date
for
the
I
don't
know
when,
but
when
will
we
merge
the
documentation?
Maybe
I
don't
know
if
it's
today
in
a
week
or
what?
But
we
should
set
a
date
so
that
we
so
that
anyone
that
wants
to
make
suggestions
can
do
it
until
then,
and
then
we
merge
that
one
and
after
that,
everything
we
need
to
do
to
release
three
3.0
is
like
actually
submitting
the
level
and
things
like
that.
So.
B
C
C
Many
rounds
did
it
already
have
we
have
a
lot
but
to
change
a
lot
of
things
as
well,
because
he
before
we
thought
he
make
a
documentation
where
we
we
put.
She
like
the
plugins
into
the
project
version
and
others
tutoring,
so
she's
changed
the
structure
and
he
changed
the
information
as
well.
So
because
of
this,
the
approach,
how
we
will
explain
the
steps?
Change
it
a
lot.
So
I
think
in
more
one
hound,
would
you
be
nice.
B
And
camilla
has
been
also
being
in
in
slack
and
people
who
already
contributed
like
for
at
least
a
week.
So
I
think
that
everyone
has
had
a
chance
to
submit,
and
the
other
thing
that
I
want
to
make
clear
is
that,
even
if
we
want
to
modify
something
of
this
documentation
and
we
do
it
in
a
further
port
request,
we
can
just
change
the
book
version.
3
branch
to
that
comment
and
the
documentation
will
be
updated.
So
I
think
we
don't
need
to
block
the
release
on
on
this.
A
B
A
B
B
It
actually
has
only
has
only
received
a
small
review.
I
don't
know
if
you
guys
could
give
it
a
review.
It
basically
will
allow
plugins
to
be
changed
together
in
so
that
we
can
do
things
like
the
declarative
pattern,
move
it
to
a
plugin
or
the
things
that
we
are
doing.
The
operator
sdk
is
doing
instead
of
wrapping
and
the
whole
base
plugin
and
doing
things
over
it.
It
would
be
just
an
addition.
After
we
have
been,
we
have
scaffolded
with
the
base
plugins.
B
It
defines
the
different
methods
that
that
will
be
supported
for
the
by
the
plugins
and
which
order
will
they
be
and
for
which
commands
will
they
be
executed
and
there's
also
an
implementation
pull
request.
That
already
does
this.
The
implementation
pull
request
has
received
zero
reviews
and
it's
a
pretty
big
one.
B
It
already
does
everything
that
is
listed
in
the
enhancement
proposal,
so
if
you
have,
if
you
guys
have
some
time
to
review
both
the
proposal
and
the
and
the
pull
request
and
the
implementation,
it
could
be
nice
because
I
think
that
if
we
get
this,
this
won't
get
merged
for
version
3.
But
if
we
merge
it
for
version
3.1,
it
will
simplify
the
development
of
plugins
from
from
now
on.
D
A
C
C
So
before
we
viewed
the
road
map-
and
you
know
what
it
should
be
addressed
before
1.0
today,
she
watches
a
breaking
change
in
the
backlog
before
we
started
to
identify
that,
I
think
it
is
would
be
the
the
link
with
all
issues
that
we
need
to
check.
Analyze
being
say,
gave
you
the
idea
of
we
try
to
do
cheese.
You
know
each
person
tries
to
do
cheese
in
the
spare
time
shaky.
I
don't
know
a
few
weeks
a
few
issues
per
day.
C
Do
you
know
until
we
are
able
to
shackle,
but
she
for
we
remove
it
from
cheese
link
we
need
to
some
kind
of,
or
we
need
you
putting
a
milestone.
We,
which
I
think
that
should
be
not
nice
if
she's
proposed,
but
she
I
thought
like
if
you
create
a
milestone
in
action
or
something
like
that
or
another
label,
just
checking
something
like
that.
A
C
Yes,
have
it
not
been
preached
in,
we
don't
know
if
he
has
a
break
change
or
not,
because
it's
nothing
a
milestone
or
doesn't
she
have
the
the
label
break
change
but
okay,
for
example.
If
I
go
there
and
just
listen
check
the
first
three
ones,
how
I
remove
it
from
this
leash,
you
know
I'm
trying
to
find
a
way
to
filter
what
was
checked
and
subreddit.
C
Because
they
probably
don't
need
to
do
to
synchronize
everybody,
each
person
can
like
take
a
a
few
times
to
to
try
to
to
check,
because
I
I
I
believe
that
today
is
not
to
decide
when
should
be
done.
It
was
like
interesting
to
filter.
The
watch
is
a
breaking
change
or
not,
so
I
just
intellectual
way
to
remove
it
from
this
list.
Watch
someone
our
energy,
give
you
a
look
angie,
consider
that
it's
not
a
break
change
at
all.
A
A
Yeah,
I
think
the
only
I
think
just
for
what
it's
worth
like.
That's
fine
with
me
for
what
it's
worth.
I
think
the
main
difference
is
that
more
people
can
assign
a
label
than
to
assign
a
milestone.
I
don't
I
don't
know
if
that's
a
good
thing
or
a
bad
thing
in
this
case,
but
yeah
we
could,
we
could
just
create
a
milestone
for
like
post
1.0.