►
From YouTube: SIG Cluster Lifecycle - Cluster Addons 20200121
B
A
Know
Lee's
in
the
plane
somewhere
yeah.
Just
just
let
me
know,
I'll
send
me
the
file
and
all
I
did
to
the
to
the
YouTube
cool
I
had
another
small
thing:
it
wasn't,
but
the
repository
name.
It's
not
a
huge,
hugely
urgent
thing
to
me.
I
just
realized
that
we
went
from
Anton
operators
to
a
broader
definition
of
things
we're
looking
at
and
it
might
be
easier
to
find
if
we
have
cluster
add-ons
consistently
across
slack
and
all
the
other
place.
But
I
also
don't
know
what
it
involves.
C
B
A
D
B
D
B
D
Some
of
the
questions
that
I
ever
like
what
and
I
can
mark
them
on
the
terrible
PR
as
well.
One
was
about
technical
about
the
integrating
with
controller
runtime
and
links.
Removing
API
is
from
a
watch
list
system
dynamically.
Some
other
ones
were
generally.
What
injector
are
we
using
for
these
things?
There
seems
to
be
some
difference
between
the
ones
that
are
currently
you
know.
Operators.
F
E
F
B
E
D
Of
tangent,
where,
when
we
have
to
beat
the
eyes
within
the
same
API
group,
but
possibly
our
different
controllers,
we
typically
want
them
to
live
in
the
same
package
and
go
since
we're
generating
these
things.
Together
with
you
builder
easily,
so
installer,
let's
say
claims
one
group
and
I
want
to
belong
to
the
same
group,
but
I.
Don't
necessarily
want
the
code
to
be
part
of
installer
so
like
how
does
this
all
all
shake
out
there?
D
G
G
G
We
have
needed
sort
of
a
you
know
a
kubernetes
installer
as
just
like
part
of
our
product
for
a
long
time,
and
so
we've
kind
of
have
had
one
and
we
open
sourced
the
latest
iteration
of
that,
and
we
call
it
curl
with
the
case
okay,
URL,
and
the
idea
is
that
you
can
create
these
different
add-ons.
We
made
those
add-ons
customized
based.
G
We
have
a
handful
of
add-ons
that
we
support
today
that
we've,
like
kind
of
built
ourselves
from
different
upstream
projects.
It's
all
based
on
cubm
and
it's
it's
just
like
I
think
it
has
really
interesting
like
parallels
and
integration
points
with
the
cluster
add-ons
cig
and
the
idea
that,
like
we
might
be
able
to
make
curl
compatible
with
the
add-ons
that
you
know,
are
the
spec
that
we're
creating
here.
We
can
potentially
also
use
some
of
the
existing
curl
add-ons
as
sort
of
a
foundation
to
create
cluster
add-ons,
because
we
have
like
really
ten.
G
But
you
know
the
the
highlights
are
basically
like
we
built
this
because
we
needed
it.
We
would
love
to
contribute
anything
we
can
from
it
we'd
love
to
integrate
any
way
we
can
from
it.
There's
no
like.
We
don't
need
anything
proprietary
in
this,
and
so
whatever
we
can
do
to
sort
of
help.
You
know
align
and
further
the
simplification
of
sort
of
like
a
raw
readies
installed
that
has
some
of
these
necessary
or
common
components,
sort
of
baked
in
we'd
love
to
collaborate
on
that
we
have
a
full
foe.
B
I
guess
a
question
is
a
so
this
today
does
not
use
operators
or
is
this
kind
of
client,
side
or
server
side,
and
how
does
that
we've
been
described
by
we've
been
doing
operators
to
date
that
they
were
not
tied
to
doing
operators,
but
we've
been
doing
a
purse
today.
But
if
we
can't
understand
like
is
this
client
site?
Is
this
server
side
to
thing
yeah.
H
It's
a
good
question,
so
today
we
built
this
as
its
client
side,
so
you
run
the
Installer
and
it
installs
kubernetes
and
basically
all
of
the
add-ons
are
ultimately
each
add-on
is,
is
a
customization
yamo
which
defines
everything
that's
going
to
be
deployed
and
a
bash
script,
because
sometimes
the
best
the
bash
script
doesn't
have
to
really
include
anything.
But
often
it
does
things
like
sequencing,
CR,
DS
and
custom
resource
installation
or
generating
you
know
certs
or
something
like
this.
That
doesn't
currently
happen
inside
operators
or
inside
plain
kubernetes
DMO.
H
Well,
I
guess
grant
mentioned
like
we're
like
this.
Is
you
know
a
very
you
know,
we've
been
we've
had
something
like
this.
This
is
like
an
open-source
version
of
something
that
we've
had
internally
for
quite
a
while
now
and
it's
not
it's
not
necessarily
a
spec
that
were
that
we
we
feel
like
you
know
we
want
to
either
own
or
that
like.
This
is
exactly
the
right
format
for
it.
F
F
H
So
we
do
everything
is
packaged
as
a
single
batch
script
today,
because
we
support
air-gap,
installs
of
kubernetes
and
all
the
readers
and
so
we'll
create
a
tar
gzip.
That
includes
all
the
images
and
all
the
manifests
and
everything
necessary
for
that
specific
package.
The
curl
spec
defines
a
list
of
here's
all
the
add-ons
that
I
want
inside
here,
so
that
curl
spec
will
create
a
tar
gzip.
That
includes
the
images
and
everything
so
to
install
an
update.
H
H
B
Think
there's
a
bunch
of
like
reassuring
things
here.
There's
them
there's
the
mechanics
of
like
getting
a
customized
based,
I,
don't
I
guess
into
the
cluster
and
there's
the
work
you've
done
to
package
some
add-ons
as
customers.
Full
add-ons
I
think
may
be
a
great
place
to
start
might
be
like
trying
to
pick
one
of
those
add-ons
and
get
it
into
the
like
the
operator
framework
and
compare
the
two
I
compare
the
operator
approach
to
what
you've
been
doing
on
the
client
side.
B
When
I
was
looking
at
like
the
lists
or
the
six
while
I
didn't,
it
seems
as
far
as
I
know,
we
don't
have
anyone
working
on
the
registry,
so
maybe
that
might
be
a
good
one
to
to
focus
on
if
that
was
a
good.
That
was
an
interesting
one.
I
don't
know
if
team
ref
I
was
gonna
say.
Actually
we
have
a
perfectly
good
operator
for
registry.
I,
know
I'm,
just
not
familiar
with
that.
E
E
H
Have
some
operat
some
add-ons
that
aren't
listed
on
that
homepage?
If
you
go
into
the
repo
and
look
in
the
add-ons
directory,
but
we
have
things
like
you
know:
they're
a
little
newer
for
us
fluent
Dee
and
calico
and
Valero
from
from
VMware.
So.
B
E
G
H
Yeah,
so
we
you
know,
one
thing
that
that
curl
is
doing
that's
kind
of
I,
suspect
out
of
scope
of
cluster
add-ons
directly
is
like
bringing
the
cluster
along
and
installing
in
provisioning
the
kubernetes
cluster
for
you.
So
we
do
some
things
around
some
pre
flights
and
ensuring
that
the
machines
are
going
to
be
capable
of
successfully
running
kubernetes.
With
the
add-ons
that
you
have
selected.
H
B
H
It's
fine
definitely
can
dive
into
a
little
more.
We
don't
like
our
curl
project,
like
the
primary
use
case
of
the
curl
project.
Isn't
somebody
saying
I
have
a
kubernetes
cluster
up
and
running
and
I
want
to
install
this
add-on
into
it,
but
it's
more
I
have
some
CentOS
or
some
real
machines
or
Bunty
I
have
some
Linux
servers
and
I
want
to
turn
this
into
a
kubernetes
cluster
with
all
these
add-ons
already
installed
it.
H
So
there
are
two
different
tasks
you
know
of
provisioning
kubernetes
with
like
the
container
runtime,
which
is
you
know,
generally
dr.
right
now
for
us
and
and
all
of
that
and
then
the
add-ons
around
the
CNI
and
storage
and
in
you
know,
registry
and
everything
like
this.
Those
are
two
different
things
that
curl
does
and
so
I
think
the
question
really
is
like
is
the
the
first
part
of
that
which
is
taking
Linux
machines
and
getting
kubernetes
up
and
running
out
of
scope
of
the
cluster
of
the
sync
or
add-ons
I'm.
B
There
is
something
I
think
interesting,
which
is,
for
example,
as
the
version
of
kubernetes
changes.
How
do
we
match
that
to
the
compatible,
add
ons
and
manage
the
upgrades
in
sequence,
those
things
but
I
that
would
be
I,
think
where
it
is
vague
in
scope,
but
not
driving.
The
installation
of
kubernetes
itself
figure
that
Jessica.
E
H
In
Jessica
and
Jason
like
then,
the
operator
methodology
for
deploying
add-ons
today
do
you
have
have
you
done
anything
around
hooking
that
into
like
reacting
to
upgrades
to
the
underlying
kubernetes
framework
and
then
being
able
to
like
have
a
life
cycle
hook
that
does
trigger
something
inside
the
add-on.
I.
B
E
Yeah,
as
Justin
alluded
to,
we
have
some
stuff
as
part
of
our
distribution,
where
we
do
lifecycle
a
lot
of
the
add-ons
that
are
part
of
our
platform,
as
we
lifecycle
cube,
so
that
is
kind
of
there
today
and
some
of
our
stuff
and
a
lot
of
we
know
what
we
talk
about
in
this
add-ons
group.
We're
trying
to
take
from
what
we've
learned
doing
that
ourselves
and
expand
that
out
to
everybody.
E
Yeah
and
we're
looking
at
some
of
that
stuff,
so
in
the
operator
framework
group
and
the
lifecycle
manager,
that's
one
of
things
that
we're
thinking
about
is
yeah
like
just
digestant.
If
something
we
upgrade
your
cluster,
but
you
have
this
particular
add-on
installed.
What's
that
going
to
do,
and
how
do
we
manage
that
and
do
we
block
upgrades
or
not
and
those
kinds
of
questions
all
that
stuff
is
coming
up,
so
definitely
things
that
I
think
are
in
scope
for
these
discussions.
E
E
A
H
No
I
think
I
don't
have
any
specific
questions.
I
think
it's
like
as
we're
continuing
to
build
out
add-ons
in
like
enhancing
curl,
and
you
know
releasing
stuff
around
up.
You
know
updating,
kubernetes
and
managing
all.
That
would
like
continue
to
join
the
calls
and
see
how
we
can
like
share
and
like
make
sure
that
we're
not
building
something
that's
completely
disconnected
from
the
community.
F
H
D
Like
yeah
I
wanted
to
follow
up,
there
I
think
that's
a
pretty
good
place
for
us
to
collaborate
on,
because
every
solution
that
we're
looking
at
and
have
talked
about
has
the
same
problem
of
like
how
do
I
just
talk
about
a
set
of
manifests
that
I
want
to
represent
an
add
on
and
apply
to
the
cluster.
Everyone
is
like
slightly
different
variants
on
this
one
thing:
I'm
so
if
we
could
make
some
headway
on
a
green
on
that
that
might
help
us
build
a
big
tooling
around
it
cool.
H
Yeah
we
have
am
a
doc
on
how
to
put
a
package
and
add-on
which,
like
is
I'll,
put
it
into
the
slack
under
the
chat
on
the
zoom.
This
is
definitely
a
little
bit
more
like
I'm,
an
add-on
author
and
I
want
to
package
it,
but
what
you
know
internally,
we
create
the
add-on
archives
as
air-gap
packages
in
a
really
similar,
like
format,
so
I
think
that
that
link
there
we'll
walk
it
through,
but
I
think
that's
a
good
good
feedback
to
is.
We
should
be
a
little
bit.
D
G
Yeah
I
was
I
could
be
explained
last
time
that
we
we
didn't
intentionally
set
off
to
build
something
like
just
different
than
what
was
happening
here.
We
actually
just
didn't
know
that
this
existed
and
so
I
was
like
just
searching
around
or
something
solidus
like
I,
don't
know
a
month
ago
and
I
was
like
oh
crap
like
we
should
probably
try
to
align
better.
So
there's
not
like
a
you
know,
I
there's
no
intention
of
like
splitting
this
off.
It
was
just
like,
oh
well.
We
were
building
this
thing
that
we
needed.
G
B
I
thought
we
talked
about
previously
about
like
the
idea
of
doing
like
something
like
show.
Intel's
I
think
here
is,
if
I'm
not
getting
confused,
but
the
I
think
we
have
the
pieces
going
into
cops
for
at
least
an
implementation.
That
I
think
is
a
little
different
from
the
widely
used
than
it
for
like
how
we
can
put
add-ons
into
the
cop.