►
From YouTube: Kubernetes KubeBuilder 20191009
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right,
this
is
the
cube
builder
sub
project
meeting
for
October,
ninth
2019.
As
a
reminder,
this
meeting
is
being
recorded
so
don't
say
anything
that
you
don't
have
recorded
for
all
posterity
all
right.
So
we've
got
three
items
on
the
agenda
for
today,
plus
if
anyone
wants
to
enemy,
but
apparently
three
so
I
think
we'll
jump
right
into
them.
A
A
B
A
A
C
A
A
A
D
Can
add
to
that
hi
I'm
Phil,
we
rock
there
is
some
guidance
I
think
across
the
community
around
progression
on
kind
of
the
ladder
for
maintainer
ship.
It
is
pretty
out
of
date,
I
think
it
was
a
straw
man
put
into
place
years
ago,
but
it's
there
in
at
least
shows
the
president's
that
there
should
be
like
kind
of
a
standard
way
of
evaluating,
and
one
reason
it's
important
to
have.
A
E
A
Will
create
an
issue
again
on
the
cube
builder,
repo
and
I
will
link
it
and
we
can
come
up
with
some
formal
set
of
criteria
and
we
can
integrate.
Perhaps
the
strongman
or
the
initial
feedback
from
that.
And
if
you
have
thoughts,
please
do
come
and
comment
and
if
you
are
interested
in
being
a
reviewer
to
and/or
proofer,
you
know,
obviously,
as
we
figure
those
out,
please
do
submit
yourself.
A
All
right
so
one
more
quick
note
for
me
and
then
I
think
we
have
an
additional
item
from
Phil.
So
the
last
quick
note
for
me
is
that,
after
much
until
late
on
my
part,
unfortunately,
we
finally
have
a
youtube
channel
for
Q
Builder
recordings
as
part
of
the
or
a
YouTube
playlist
as
part
of
the
kubernetes
organization,
just
like
siggy
machinery,
etc.
A
D
I'm
just
tack
something
on
here
at
the
end
and
I
think
this
relates
to
met
a
controller
and
COO
builder,
but
and
I
just
came
out
of
the
60
Li
meeting,
where
I
actually
brought
up
the
same
topic.
But
customized
has
this
notion
of
plugins,
where
customize
will
ingest
some
set
up
resources
and
transform
them
using
some
configuration
defining
the
difference
of
the
function
and
then
spit
out
a
new
set
of
resources
right.
So
you
can
imagine
like
put
everything
in
this
namespace
as
a
transformer
where
it
takes
bunch.
D
Resources
then
sets
it
puts
everything
in
a
namespace.
That's
names
based
and
then
spits
them
out,
and
this
is
actually
pretty
similar
to
the
meta
controller
approach
for
declarative
in
declared
about
transformations
on
on
resources
for
controllers
and
cout
builder.
Also,
a
controller
does
could
use
this
pattern
as
well,
and
what
I'd
like
to
do
is
as
if
we
are
converging
on
this
sort
of
generalized
functional
pattern
for
manipulating
resources
across
regardless
environment,
whether
it's
client
side
or
server
side.
D
B
D
Well,
yes,
the
idea
is
to
when
we
write
something
when
we
writing
something
like
medic
controller,
like
the
pattern
for
meta
controller
right
is
to
accept
a
request
of
resources,
do
some
transformations
and
then
kind
of
return.
A
result
in
society
is
the
format
of
that
request
is
standardized
across
meta
controller
or
customized
plugins
or
whatever
else
you're
doing,
and
so
then
we
can
build
kind
of
shared
tooling.
That,
like
you,
could
imagine
like
here's.
Your
starter
project
that
just
fills
in
the
function.
D
B
It
okay
I
just
wanted
to.
It
was
that's
an
interesting
idea.
I
agree
with
it.
I
just
wanted
to
distinguish
that
from
some
of
the
other
discussions
that
we've
had
with
Q
builder
in
terms
of
having
a
plug-in
architecture
that
supports
like
different
scaffolding,
techniques-
and
it
sounds
like
this-
is
a
separate
idea.
I.
D
Yes,
although
I
am
always
surprised
at
how
much
every
single
problem
seems
to
actually
boil
down
to
this,
one
I
mean
like
most
of
the
problems,
I
look
at
because
it's
a
declarative
interface
for
kubernetes
right
every
effectively.
Every
request
is
a
resource
request,
and
so
you
can
actually
represent
most
of
the
things
you
want
to
do
this
way.
So
from
a
scaffolding
perspective,
I'd
imagine
like
for
scaffolding
configuration
for
running
kuu
builder.
This
might
actually
fit
with
that
as
well,
because
it
would
just
be
another
instance
of
generating
resources
for
scaffolding
go
code.
B
D
A
A
B
B
B
A
B
A
B
Thinking
about
that,
but
so
some
of
your
suggestions
that
we
were
talking
about
last
week
in
terms
of
like,
if
we
have,
if
we
have
a
type
in
a
function,
signature
in
controller
runtime,
that
has
a
breaking
change
and
that
type
is
in
an
external
repo
there's
a
little
bit
of
weirdness
and
it
doesn't
quite
work.
How
we
would
expect
I
think
that
thing
that
I
have
written
appears
for
so
I'd
like
to
do
is
probably
spend
a
little
more
time.
Cleaning
that
up
such
that
it
like
can.
B
A
That
makes
sense,
I
don't
know
if
it
will
be
useful
at
all,
but
there's
a
PR
hanging
around
where
I
attempted
from
like
I
are
like
eight
months
ago,
or
something
like
that.
Maybe
even
a
year
ago,
where
I
attempted
to
do
something
similar
to
what
you
did.
The
state
of
the
code
is
really
really
hacky,
but
it
did
have
the
logic
for
like
traversing,
through
the
API
and
figuring
out
like
what
things
from
external
packages
were
actually
part
of
our
public
API,
so
that
you
might
have
some
inspiration
from
that.
A
F
I
mean
I'm
not
sure
if
this
page
anywhere
in
the
process
of
trying
to
get
things
working
with
control
of
runtime
on
Kudo.
There
is
a
challenges:
I
guess,
with
academic
dependency
with
client
go
so
it
it
might
be
a
need
to
provide
some
guidance
for
people
using
controller
runtime
as
to
what
versions
should
be
used.
A
A
We
are
finally
getting
progress
on
having
a
standalone
library
from
kubernetes
that
includes
the
generic
parts
of
Clank.
Oh
the
generic
and
the
generic
parts
of
API
machinery,
supposedly
we'll
be
getting
a
cap
from
that
from
sig
API
Machinery
soonish
this
releases.
Hopefully
so,
if
we
get
that,
we
will
draft
up
a
plan
to
switch
to
that,
and
that
will
make
all
of
this
a
lot
easier,
but
in
in
the
meantime,
yeah
generally
try
to
stick
to
the
versions
listed
in
Godot
mod.
How.
C
Would
you
feel
related
to
that
quite
like
a
lot
of
the
kubernetes
dependencies,
given
some
of
go
mods
issues
with
cember
and
high
version
numbers?
What
would
be
your
thoughts
about
tagging,
the
releases
of
controller
runtime
and
maybe
even
controller
to
tools
to
the
kubernetes
version
just
to
match
the
the.
C
Paradigm,
I
guess
the
client
API
and
a
bunch
of
these
other
libraries
are
using
just
so
then
then
you
know
when
you
install
you,
do
a
go:
get
control
of
runtime
SIG's
like
it's
a
no
such
controller,
one
time
at
kubernetes,
1.60,
not
one
I,
think
it's
how
that
all
is
panning
out
now.
What
do
you
think
about
matching
that
for
this
upcoming
controller
runtime,
one
of
15
and
1.16
releases
and
and
in
the
future,
so
we've.
A
I
I
mean
I've,
henceforth
been
hesitant
to
do
that,
just
because
it
like
it
makes
it
impossible
to
know
if
something's
gonna
break
when
you
upgrade
your
code
from
the
controller
runtime
perspective
right
like
if
you're
pinning
to
kubernetes
versions
right
like
they're,
you
don't
have
any
idea.
If
this
is
like
control
or
runtime,
has
a
breaking
change.
Kubernetes
got
upgraded
stuff
like
that
sure
that
that
has
been
our
hesitation
thus
far
on
doing
that.
C
What's
in
our
code
up
ma,
what's
in
a
a
specific
version
of
a
controller
runtime
or
ladies,
we
can
plan
it
out
a
little
bit
a
little
bit
more
clearly
versus
having
it
go
through
each
point,
release
and
keeping
that
up-to-date,
because
we
we,
for
example,
may
elect
that
we
want
to
stay
on
the
kubernetes
1.14
set
of
client
language.
That's
not
the
case,
we're
good.
We
want
to
move
to
116
for
the
CR
dp1,
but
going
forward
I.
C
My
I
guess
my
worry
is:
is
keeping
I
get
I,
get
where
you're
going?
This
is
a
hard
problem,
because
I
don't
want
to
get
behind
on
controller
runtime
releases,
but
I
don't
want
to
suddenly
introduce
a
breaking
client
change
and
the
rest
of
our
code
base
because
controller,
runtime
updates
and
I
guess
I
guess
we'll
just
have
to
keep
it's
we'll
have
to
talk
internally
on
our
side
on
how
we'll
deal
with
that
yeah.
A
A
A
A
Yeah
I
think
that
I
think
that
maybe
I
think
we've
had
a
couple
others
that
I
can
try
to
link
I.
Think
that's
the
most
recent
when
I
was
thinking
of
but
I
think
there's
like
I
think
those
others
that
have
occurred
over
time,
I'll
see
if
I
can
find
them
yeah.
This
is
not
the
first
time
this
question
has
been
brought
up.