►
From YouTube: Kubebuilder community meeting Aug 10, 2023
Description
Kubebuilder community meeting Aug 10, 2023
A
C
A
It
looks
like
the
agenda
item
is
emptier.
The
announcement
section,
let's
move
on
to
the
next
item,
which
is
professor's
Community
interests,
so
the
first
Point
here
is
discussing
our
priorities.
This
this
mentioned
by
Camilla
in
the
last
community
meeting.
We
went
through
that
quickly.
We
had
a
few
items
assigned
to
folks,
except
for
the
last
one
and
others
have
been
worked
on
so
Camilla.
Do
you
have
any
thoughts
in
this.
D
D
A
D
D
D
D
Yeah
yeah
I,
don't
know,
I
I
was
thinking
about
it.
Maybe
has
two
things
right:
changing
the
hash
history
that
you
are
pushing.
Maybe
we
don't
need
you
use
their
prone
to
do
that,
maybe
that
should
we
could
do
in
the
way
the
church
generates
now
just
to
change
the
the
hashes
by
itself.
Each
might
work
directly.
That's
it
for
the
proxy
image
right,
but
we're
still
using
the
Google
Cloud
platform
for
other
things,
such
as
generate
the
invitation.
Binaries.
D
A
D
A
D
D
A
A
A
D
A
D
No,
unfortunately,
not
that
that
is
a
decided
for
the
long
time,
because
the
first
example
I
want
to
use
the
aapi
I
want
to
create
a
project
can
be
operator,
for
example,
and
I
want
to
using
an
API
that
symbol
is
from
another
project
right,
so
operatory,
for
example,
watching
the
crg,
the
CRS
from
one
crg
from
our
operator
B.
But
you
know
the
tooling
doesn't
allow
your
scalfold
using
standard
apis.
We
discussed
it
touching
the
past
in
cheesy.
Show
has
some
proposal
ideas
how
what
we
need
to
do?
D
Would
it
be
nice?
If
someone
would
you
like,
it
should
take
a
challenge?
A
few
people
has
been
been
giving
me
out
like
he.
What
what
I
can
do
that?
That
is
not
a
easy,
easy
one,
but
it's
not
so
hard
as
well,
but
it's
a
medium
I
think
which
would
be
very
important
to
do,
because
a
lot
of
people
want
to
do
the
same,
and
the
tooling
doesn't
actually
help
the
users
regardless.
This
needs.
A
D
It's
not
a
goaling
definition.
Oh
it's
it's
API,
because
when
we
Define
strg
right,
we
are
creating
a
API,
so
the
holy
goal
is
allow.
We
run
copy,
Builder,
create
API
and
in
stage
of
the
general
HD
applying
the
project
itself
allow
we
will
do
is
call
forward
to
using
API
from
another
project
so,
for
example,
if
I'm
building
the
project
a
but
I'm
watching
what
the
apis
I
want
to
watch
a
custom
resource
definition
that
who
is
the
owner
of
the
custom
resource
is
another
project.
D
E
A
D
It
is
for
a
long
time
a
lot
of
people
would
like
to
have
this
possibility
and
but
we
we
never
implemented.
One
of
the
comments
has
these
steps
more
or
less.
If
you
I
know
that
the
traged
is
big
but
I,
try,
if
you
want
you
can
ping
me
I,
try
to
find
you
the
comments
that
she
has.
Some
ideas,
I
think
she's,
one
that
you're
putting
the
best,
which
is
also,
if
you
see,
let's
see
how
you
put
you
here
in
the
zone
right
here.
E
A
A
B
That
is
like
a
step
from
zero
to
one,
and
then
we
will
write
the
logic
to
go
with
the
reconciliation
and
so
right
now
it
seems
like
there's
already
have
some
definitions
of
the
API
and
then
for
the
users.
What
is
the
use
case
that
they
want
to
use?
They
want
to
import.
The
external
API
not
just
directly
say,
write
the
Logics
of
the
red
conciliations
or
the
The
Operators
to
watch
that
API
I.
D
I
can
I
can
try
to
to
give
you
an
example.
For
example,
I
have
a
project
that
she,
let's
see,
is
the
front
change
right.
I
have
an
operator
that
you
deploy
manage
everything
about
your
front
chain
solution
right.
Anything
I
have
the
backings
in
the
back
end.
For
example,
I
want
to
watch
the
custom
resource
that
you
do
definitions
about
my
phone
change
or
the
operator
that
she
I
can't
change.
This
right.
D
I
have
one
potato
that
install
my
solution
and
I
have
another
operator,
that's
responsible
for
install
post
service
or
my
cycle,
a
database
right,
but
in
my
operator,
I
want
to
watch
the
custom
resource.
That's
installed
the
database
itself
in
the.
According
with
some
definitions,
I
want
you
to
do
some
kind
of
behavior,
or
things
like
that
right.
So,
if
I
want
to,
for
example,
create
a
webi
hook,
I
want
to
sculpture
is
to
have
a
CLG
resource
in
API
to
be
used
in
the
web
hook.
D
D
So
they
we
needed
to
it's
possible
to
do
that,
but
you
needed
to
change
the
scaffolding.
Okay,
okay,
cool
yeah,
I,
don't
know
Michael
you!
You
said
that
she'll
face
that
as
well.
Do
you
want
to
share
the
scenario
that
to
you,
that's
what
you
are
trying
to
do
and
what
you
are
the
child
and
his
face?
Or
did
you
miss
something.
E
It's
very
similar
I
mean
it's
like
you
have
I
mean
part
of
it
is
like
you
have
one
upper
code
base,
then
it
defines
an
API
and
with
another
operator
you
want,
like
you,
want
to
interact
with
the
first
operators
API.
So
like
it's
possible,
if
you
just
like
import
the
first
operator,
but
I
mean
sometimes
like
it's
messy
right
like
maybe
the
first
operator
has
some
replace
statements,
so
just
the
whole
import
process
is
not
something
you
really
want
to
do.
A
Yeah,
that
makes
a
perfect
sense,
so
in
other
use
cases
say:
I
am
a
service
provider
and
I
would
like
to
define
the
apis
and
have
a
validation
Logic
for
the
apis,
which
I'm
providing
to
multiple
other
teams.
So
I
would
not
want
the
specific
teams
to
create
or
for
the
API,
which
I
have
and
add
their
own
spec
values.
Sorry
aspect:
definitions
I
would
like
to
control
the
validation
of
it.
A
So
this
is
one
other
use
case
where
I
would
like
multiple
other
teams
to
use
the
API
which
the
provider
has
defined
and
then
built
an
operator
rather
than
creating
an
API
or
forking.
The
API
like
Michael,
said
so
that's
another
use
case
and
the
one
which
Camilla
said
is
also
like
perfect.
That
also
makes
perfect
sense.
Does
that
answer
your
question?
Tony
yeah.
D
Thing
I
just
used
a
supplement.
One
thing:
I
I,
put
a
request
in
the
search.
Teaspoon
requests
is
a
documentation,
that's
explained,
like
people
watching
poetry,
all
apis
from
one
project
to
another,
and
she
thinks
it's
focused
is
explaining
how
to
do
that.
Energy.
The
caveats
into
the
problems
to
do
too
since
she's
put
in
his
documentation.
D
Also
has
the
parents
like
what
you
need
to
do
manually
to
do
this
helpful
to
work
with
Stern
apis
is
the
pull
request
is
not
emerged
because
it
has
a
few
things
that
you
need
to
be
changed
also.
If
someone
would
like
to
continue
to
work,
would
you
be
wonderful
and
you,
maybe
that
also
can
help
Michael
pursue
the
goal.
E
A
A
Moving
on
to
the
next
one,
I
think
Michael
has
also
mentioned
this.
There
is
an
issue
created
long
ago
and
using
of
a
network
policy
instead
of
the
Q
barback
policy.
Those
got
bummed
up
because
one
of
the
community
members
had
commented
that
GCR
container
Registries
being
deprecated.
The
good
thing
is,
we
have
taken
action
against
this
and
we
have
looking
to
move
this
to
another
registry,
but
the
issue
also
talks
about
replacing
Q
Bar
back
policy
with
network
policy,
which
is
a
code
type
that
kubernetes
routes.
A
E
E
I
kind
of
like
agree
wholeheartedly
was
that
they
seem
they're
just
different
layers
in
the
authorization
or
like
authentication
stack,
so
I
think
they're
different
different
enough,
so
like
we
shouldn't
necessarily
replace
one
for
the
other,
but
you
know
I
was
thinking,
maybe
it's
possible
if
we
like
document
how
to
use
a
network
policy
like
like,
if
you
don't
want
to
use
Q
Bar
proxy,
here's
how
I
could
use
Network
policy
like
this.
These
are
the
differences,
but
it
doesn't
feel
like
it's
something
we
could
just
replace.
A
I
think
document
useful
here.
The
only
question
which
I
had
is:
we
need
an
example
or
probably
Michael.
If
you
are
working
on
this,
it
would
be
super
helpful
to
use
a
network
policy
instead
of
a
Q
Bar
back
policy
and
check
if
the
operator
works
as
expected
before
writing
the
documentation,
so
that
we
can
mention
that
if
you
need
to
get,
if
you
need,
excuse,
Network
policy
and
if
you
need
by
you
can
use
Cube
back
policy,
does
that
make
sense.
A
D
Putting
this
so
that
the
focus
closet
I
think
not
necessarily
with
such
a
close,
because
this
user
is
complaint
like
that
is
to
open
it
hated
in
his
point
of
view
a
would
you
like
it
that
she,
the
one
for
proxy,
would
be
optician?
Why
can
we
have
like,
for
example,
graph
phone,
then
I
started
to
think
if
we
could
do
not
also
externalize,
it
is
one
and
you
have
it
by
the
fool.
D
D
So
maybe
we
could
put
option
out
and
then,
instead
of
generate
the
image
we
use
that
image
directly
and
just
analyze
the
plugin
for
their
Repository,
because
it
the
the
best
thing
about
to
use
the
image
is
because
the
project
is
not
part
of
the
kubernetes
C.
And
just
because
of
that
we
have
been
taking
that
image.
Reviews
for.
D
We
no
longer
needs
to
to
use
the
alpha
proxy
or,
if
that
should
be
a
plugin
that
lives
in
there
repository
we
no
longer
needed
to
build
damage.
Also,
we
don't
need.
We
don't
have
the
first
priority
that
we
discussed
today
about
the
hashestry
thing.
We
reduce
the
default
to
keep
the
things
maintained.
D
Accounts
right:
the
project
is
very
nice
and
I
understand
that
she
has
features
to
protect
the
solution
that
he
using
only
kubernetes
API
is
is
not
the
same.
It's
not
achievable.
However.
We
also
has
she's
born
that
she's
every
time
that
they
generate
image.
We
need
to
go
there.
Okay,
it's
very
simple
with
just
a
bump
engine
damage.
D
The
images
in
the
in
the
kubernetes
has
history,
for
we
ensure
that
she
always
that
she
image
will
be
available
for
our
users.
However,
it's
not
so
much,
but
if,
for
example,
now
they
change?
No,
it's
not
you
know,
but
they
change
the
hedges
we
need
to.
We
need
to
generate
touching
another
way,
I,
don't
know
and
she's
new
process.
If
we
no
longer
use
it.
A
The
future
just
one
question
Camila,
because
I'm
not
aware
of
the
queue
like
how
the
workings
of
the
queue
are
actually
a
project
as
much,
but
we
do
scaffold
the
metrics
endpoints
for
the
Readiness
and
liveness
probe
by
default
in
Cube,
Builder
reconciler.
Does
that
effect
in
any
way,
because
now
we'll
be
making
it
unpredictable.
D
Yeah
we
we
Scout
for,
let's
see
if
you
understood
you
are
saying
like
we
discovered
the
service
account
right
with
the
permissions
to
allow
the
metrics
and
the
point
chip
be
accessible,
and
then
the
person
is
applied
that,
if
I'm
not
wrong
and
the
other
option
is
turning
off
the
proxy
and
today
I
think.
That
is
how
we
documented.
D
Because
he
for
others,
when
I
saw
the
issue
I
started
to
think,
could
you
not
that
should
be
I
stand
up
looking
as
well
and
he's
leaving
the
Kobe
our
RBC
proxy
repository
instead
of
every
scaffolded
by
the
fool
and
today
not
be
operational?
That
is
a
ID
as
well
like
engineering.
We
reduce
the
burn
because
you're
no
longer
wanting,
we
no
longer
needed
to
rebuild
this
image.
D
So
I
I
didn't
reach
out
our
opinion
so
far,
however,
I
don't
know
like
yeah.
Would
you
like
to
see
what
the
others
think
about
you
as
well
like
he
about
the
proxy,
how
much
he
they
think
that
she
has
been
helpful
or
not?
If
we
do
external
plugging
for
cheese,
one
I
don't
know,
I
I
think
we
have
more
than
one
option
or
keep
the
things
as
it
is
today.
A
A
That
makes
sense
we
can
bring
this
up
on
the
slack
to
get
more
inputs
from
the
community
and
I
think
we
can
keep
this
issue
open
to
see.
If
there
are
more
comments
on
this
and
probably
reinserted,
does
that
sound
fine,
Michael
I
know
you
had
you
wanted
to
work
on
this,
but
it'll
be
nice
to
get
some
more
Community
thoughts
and
then
start
on
this?
Is
that
fine
for
you
yeah.
A
D
Yeah
I
posted
this
one
from
the
last
year
meeting
I
I
was
watching
the
last
one,
so
I
don't
know
if
it
was
discussed.
If
not,
my
idea
is
this:
one
is
like
he
now.
If
he
will
check
the
project,
we
have
a
lot
of
deprecations
in
place.
The
only
thing
that
is
missing
to
deprecate
is
I
think
he
we
probably
should
do
as
soon
as
possible
is
the
declarative
plugin,
because
we
have
the
question
to
externalize
that
she's
using
the
external
plugin
stuff
and
everything.
D
So
at
some
point
we
need
to
also
remove
everything
right.
She
go,
V2
go
V3
the
declarative.
One
also
has
the
config
the
OG
config,
that
is
sharing
the
codes.
If
you
will
be
able
to
remove
these
things,
we
will
have
a
huge
cleanup
in
the
code
because
it
has
a
lot
of
conditions
like
if
blah
blah
blah
bang
do
blah
blah
blah
right.
So
we
can
also
clean
up
everything.
The
other
point
is
the
componential
config
that
it's
another
thing
that
we
must
show.
D
Deprecated
that
you're
no
longer
supports
so
the
documentation,
if
you
will
look
now
as
well
as
a
lot
of
deprecations
applications
applications.
So
if
we
do
could
be
builder
for
X,
we
can
like
generate
a
new
documentation,
remove
everything
that
is
deprecated
changing
the
source
code
of
the
project.
We
can
move
all
these
applications
into
all
these
conditions,
so
I
think
that
should
be
making
the
production
easier
to
get
contributions.
For
you
know,
it's
less
code
is
so
yeah
inability.
A
D
I
think
I
think.
The
only
thing
that
we
need
to
do
now
is
try
to
move
it
forward
you
if
he
the
maintainers
from
the
declarative
Department
in
the
channel
again
the
guy
that
she's
working
this
kind
of
plugin-
and
you
see
they
agree,
we
could
deprecated
as
soon
as
possible.
It
could
be
building
because,
after
the
deprecation
right,
we
need
to
have
some
time
before,
go
there
and
remove
the
things.
D
So,
probably
if
you
eat
the
package
now-
and
we
agree
with
the
Forex
plane-
probably
will
only
be
able
to
remove
these
applications
because
it's
better
with
the
all
by
ones
right
or
probably
any
situation,
at
least
in
January
in
the
next
year.
Then
we
remove
everything
because
he'll
give
like
a
six
month.
Fertilization
of
communication.
A
A
E
E
D
Because
if
we
do
that,
for
example,
for
the
next
release,
let's
imagine
that,
should
we
release
it
Forex
now
right
everybody
that
she
is
using.
That's
a
great
chapter.
If
you
go
with
three
you'll,
be
unable
to
use
the
two
Forex
because
they
went
right
to
run
our
commands.
You'll
be
like
that
is
no
longer
supported
right,
so
you're
not
to
work
the
person.
Would
you
be
able
to
still
using
the
old
release
for
sure?
D
Don't
need
to
convince
the
dates
or
in
the
strategy
now
I
I
believe
that
the
first
step
is
like
we're
trying
to
package
the
declarative
ones
right,
because
he
signs.
We
know
that
you're
depreciate
energy,
we
will
externalize,
because
we
agreed
on
Dutch
in
the
past
a
long
time
ago.
If
you,
when
we
remove
everything,
it's
better,
we
remove
it
all
by
once
right
that
we
know
that
you
will
no
longer
wants
in
the
projects.
So
we
we
don't
need
to
define
the
dates
now,
but
I.
D
A
Yes,
I
think
I
agree
with
the
first
action
item
we
should
start
by.
To
conclude,
we
should
start
by
deprecating
declarative
pattern
once
the
declarative
pattern.
Others
are
agreeing
that
we
are
in
a
good
position
to
do
so,
since
we
also
have
an
external
plugin,
then
at
once
after
a
few
other
Cycles,
they
can
also
have
a
discussion
on
cue,
Builder,
GitHub
and
start
on
our
next
turn.
Your
food
or
text
by
removing
V3
V2
and
also
see
if
a
component
config
is
being
removed,
are
being
brought
Again
by
controller
and
time
maintenance.