►
From YouTube: SIG Cluster Lifecycle - Cluster addons 2021-09-28
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
B
Yeah,
I
guess
I've
been
talking
a
lot
about
oci
images
in
flux
for
quite
a
bit.
I
think
commuted
some
of
this
to
the
other
folks
on
the
flux
team.
I
work
at
vmware.
Now
we
have
a
bunch
of
the
carvel
tool
set
over
here.
B
They
have
been
the
carbill
engineering
team
has
been
building
a
poc
of
some
additional
flux,
controller
that
helps
integrate
an
oci
image
and
image
package
source
capability
into
flux,
and
that
we
should
be
looking
to
upstream
that
very
very
soon,
so
you
know
should
expect
an
inbound
pr
into
the
flux
project.
B
You
know
within
probably
within
a
month
and
ideally
earlier.
B
I
need
to
kind
of
chased
on
the
proper
folks
so
that
we
can
prepare
the
contribution
and
like
make
sure
that
all
the
like
legalities
are
crossed
and
dotted,
but
I'm
really
excited
about
that,
because
oci
images
and
red
drops
definitely
make
a
lot
of
sense
for
packaging
and
continuous
delivery.
B
I've
had
the
opportunity
now
to
play
a
lot
with
the
image
package
toolset,
particularly
the
registry
copy
feature,
and
the
bundling
feature
where
you
can
like
it
has
this
this
sort
of
odd
way
to
package
images
from
different
registry
like
different
repositories
like
into
the
same
repo.
A
B
Like
different
shaws,
and
then
you
know,
you
can
just
take
that
one
thing
with
those
five
different
images
baked
into
it
and
like
push
it
different
places
and
it's
just
split
up
via
these
shots
and
tags
and
that's
a
yeah.
It's
a
pretty
good
workflow,
because
you
know
that
when
you're
copying
to
another
registry
you're
not
like
stepping
on
anything
else,
it's
like
this
fully
self-contained
thing.
B
So
if
you
want
to
package
up
some
add-on,
it
keeps
it
all
in
one
one
end
point
essentially,
but
outside
of
the
image
package,
workflows
like
locking
images
and
bundling
things
together,
putting
configuration
into
an
oci
registry
and
being
able
to
read
it
is
a
general
need
as
well.
That
comes
with
some
of
those
shortcom
shortfalls,
and
then
I
think
we've
also
talked
about
some
the
other
ways
to
expand
the
use
case
so
with
evan
and
their
work
inside
of
olm.
B
So
this
is
actually
like
the
beginning
of
the
engineering
part
to
deliver
that
ecosystem
capability,
at
least
into
flux.
For
sure,
when
we
do
this,
we
should
let
other
large,
continuous
delivery
projects
like
argo
and
maybe
rancher
would
be
interested
as
well.
B
It'd
be
healthier
for
the
entire
ecosystem,
to
support
capabilities
like
this
and
to
make
sure
that
they
look
rather
uniform
because
it's
not
a
standard
like
git,
so
this
is
happening
for
flux,
and
we
should
probably
let
our
other
friends
know
so
that
this
is
not
just
some
niche
feature.
It's
a
thing
that
we
can
use
broadly.
B
I
did
not
really
take
notes
on
this.
I
don't
know
if
you've
been
able
to
take
any
notes
as
I've
been
blabbering,
but
I'm
happy
to
qualify
that
out
a
little
bit
kind
of
longer
term.
You
know
I
imagine
that
as
long
as
the
engineering.
C
B
Of
all
of
this
is
looking
square
square
by
the
way
is,
is
a
good
word
for
making
things
yeah
I
was,
I
don't
know
I
just
I've
been
doing
some
woodwork
lately.
I
could
show
you
some
pictures
if
you
want
but
yeah,
if
all
the
software
square
and
the
contribution
process
and
everything
like
I.
B
A
Because
because
they're,
you
know
refactoring
some
of
the
controllers
right
now
or
what
do
you
think
it
wouldn't
be
accepted?.
B
The
spirit
of
the
project,
the
functionality,
maybe
api,
design,
like
though
none
of
those
things
are
concerned
right,
because
we,
I
think,
as
a
team
on
flux
and
as
a
community,
already
know
that
this
feature
set
needs
to
be
a
thing.
So
I'm
excited
about
that
right.
It's
just
about
like
getting
in
touch
with
all
the
folks,
making
sure
that
attribution
and
legalities
are
good
and
that
that
it
all
works
so
just
making
it
happen.
B
A
A
B
Yeah
yeah
yeah.
We
will
shape
shape
that
up.
I
think,
because,
right
now
the
controller
is
built
independently
right,
but
we
want
to
actually
have
the
source
controller's
controller
manager.
Take
ownership
of
it
would
be
ideal
so
that
way
it
has
the
same
deployment
model
and
uses
the
same
apis
and
life
cycle
of
that
controller.
B
So
that
that's
a
little
bit
of
the
hat
trick
and
they
did
build
it
with
coup
builder
right
and
with
some
of
the
design
choices
of
the
flux
libraries
in
mind.
So
it
should.
It
should
just
bolt
right
in.
B
Fun
stuff
there,
that's
that's
the
all
the
update.
I
had
you
know
very
long
term
right
if
we
could
get
all
of
the
projects
using
oci
or
image
package
images
or
then
that
stuff
would
likely
build
an
ecosystem.
B
There
would
be
likely
multiple
repositories
from
different
open
sources
and
potentially
closed
sources
as
well,
and
we
would
want
to
list
those
things
in
artifact
hub,
so
that
would
be
a
fun
conversation
which
I
I
think,
steve
lasker
and
a
couple
other
microsoft,
folks
and
stuff
would
be
really
interested
in
that
so
yeah,
that's
all
I
don't
know.
Did
you
guys
have
any
updates,
I'm
feeling
very
casual
this
morning.
D
I'm
looking
through
the
I'm
looking
through
the
the
how
it
was
packaged,
it
looks
very,
very
sane
and
sort
of
familiar.
I
think
the
the
only
thing
I'm
wondering
about
is
like
there's
this
metadata,
which
is
shared
across
all
the
package
versions
and
I'm
wondering
whether
that
ever
changes,
but
I
I'm
just
sort
of
trying
to
understand
what's
in
that
metadata.yaml
so,
but
it
looks
good.
B
D
B
Yeah,
so
that's
that's
an
extension
off
of
the
image
package
format,
or
rather
it's
it's
like
an
additional
piece
of
the
ecosystem.
B
So
if
you
want
to
build,
that's
like
basically
the
equipment
of
the
yum
repository
right
like
so
that
container
image
you're
like
hey,
I
want
all
of
the
versions
of
the
packages
that
are
related
to
each
other
at
this
time,
then
you
go
download
that
container
image
and
it
has
that
metadata
yaml
and
that's
basically,
all
it
is
it's
just
a
blob
that
has
the
metadata
yaml
and
then
it
points
you
to
other
image
packages.
C
B
B
And
then,
when
you
actually
build
that,
whether
it's
a
you
know
a
static,
yaml,
config
or
some
program
that
you
have
to
build
like
customizer,
ytt
or
jk
config
or
something,
then
the
image
lock
file
can
be
used
to
take
those
tagged
images
and
then
replace
them
with
shaws.
B
Add
metadata
to
the
thing
about
where
it
came
from,
there's
a
separate
tool
in
the
carvel
ecosystem
that
actually
I
didn't
get
it
until
I
started
using.
C
B
B
So
it's
like
you,
you
want
to
put
in
a
tag,
so
people
know
what
version
of
software
they're
using
if
they
examine
the
configuration,
but
you
want
to
put
in
a
sha,
because
you
want
to
promise
people
that
that
tag
is
never
going
to
change
and
k.
Build,
will
go
and
just
like
search
for
image
fields
wherever
they
are
arbitrarily
and
then
it
like
has
a
map
that
will
go
and
do
a
look
up
in
the
registry
to
be
like.
B
B
Yield
with
that
metadata
fields,
then
it'll
go
and
add
an
annotation
to
the
metadata
field
that
says:
hey.
I
updated
this
image
with
this
tag.
To
be
this
shaw,
so
you
can
like
get
that
information
just
by
looking
at
kubernetes
deployment
or
pod
or
whatever
so
pretty
useful,
and
then.
D
D
Yeah,
so
you
don't
necessarily
need
them
anyway.
The
media
is
not
necessarily
as
important
but
anyway
cool.
The
the
other
thing
was.
I
know:
we've
had
a
lot
of
debates
around
like
the
the
feasibility
of
pulling
from
private
oci
registries
or
private
image
registries.
Oh.
D
B
A
question
on
the
tag
shopping
now,
you're
making
me
wonder
about
a
behavior
say:
I
include
the
tag
and
shaw
in
the
image.
This
might
be
the
reason
why
we
don't
do
it.
D
B
Because
you
wouldn't
want
to
you,
wouldn't
check
every
time
right,
you
would
pull
the
tag.
You'd
have
the
shot
locally,
so
you
you're
good
if
you're
running
on
that
node,
but
then
the
next
time,
if
you're
pulling
the
shaw
and
the
tag
has
changed,
then
it's
like
the
shaw
is
really
the
only
thing
that
you're
actually
looking
for.
So
I
would.
D
That
that's
good,
the
the
so
the
credentials
and
is
there
a
workaround
for
or
how
how
are
credentials,
how
to
say,
cap
controller
or
whatever
it
is
get
that's
reading
these
get
the
credentials.
B
Yeah
we
have
configuration
to
like
allow
cap
controller
to
log
into
the
registries
like
centrally,
and
you
can
also
hook
up
the
cap
controller.
Has
the
image
package
repository
custom
resource
and
you
can
point
that
to
authentication
similar
to
like
a
flux,
source.
B
And
yeah:
that's
like
definitely
the
most.
C
D
B
Yeah,
the
private
registries
are
probably
the
more
important
use
case
for
a
lot
of
folks
that'll,
you
know
block
them
from
getting
all
the
way
to
corruption.
B
B
Yeah
lots
of
things
to
do
in
this
space
so
should
be
pretty
solid.
Once
we've
got
that
package,
perhaps
we
could
look
at
including.
B
And
you
could
point
your
you
could
package
your
operator
as
a
single
image
and
then
have
it
reference
itself.
B
For
the
config,
but
then
like
point
point
it
somewhere
else,
if
you
want
you'll,
be
pretty
good.
B
Yeah
you
just
swap
out
the
bundle
reference
and
then
have
it
go
somewhere
else.
That's
nice
that'd
be
pretty
cool.
B
Good
yeah
use
the
same
core
to
build
a
like
more
commercial
version
of
your
open
product.
B
Yeah,
that's
all
I
all
I
had
to
bring
up.
I'm
excited
to
help
get
that
contribution
in
and
yeah
excited.
C
B
See
some
folks
justin:
where
are
you
saying
you
were
gonna,
go
or
not.
D
Go
not
not
kubecon
n
a,
but
I
am
now
eyeing.
Kubecon
eu
2022.
B
2022,
it's
gonna
be
a
year
of
twos,
I'm
not
gonna,
say.
B
A
Yeah
thanks
a
lot
for
the
update.
Let
us
know
how
things
go
and
you
know
if
I
can
help
move
anything
forward
with
the
with
the
flux.
Folks,
I'm
very
you're,
very
happy
where
we
managed
you
to.
You
know,
build
some
or
have
some
new
connections.
You
know
as
part
of
cluster
add-ons.
You
know
that
things
are,
you
know
propagating
into
other
projects
now.
So
all
the
long
discussions
we've
had
here
over
over
the
two
years
longer
they're,
all
going
somewhere.
B
B
I
mean,
I
think
nobody
has
unified
the
add-on
space
and
having
this
group
to
chat
with
you
all.
Whoever
can
join
we've
had
a
pretty
diverse
set
of
contributors
and
decision
making
type
folks
joining
here.
B
That
has
created
a
lot
of
collab
we've
built
software,
we've
poc
things,
we've
talked
about
policy
talking
about
standards
and
that
stuff
needs
to
continue
because
it's
not
happening
anywhere
else.
Maybe.
A
D
Yes
close,
but
not
quite
there,
but
yes,
hopefully
we
are
keeping
an
eye
on
it.
Perhaps
but
yes,
it
close
on
how
about
on
deck.
Maybe
that's
the
correct
expression
like
in,
I
think
that'd
be
the
sports
metaphor.
I
probably
messed
that
up,
because
I
wasn't
sportsman,
of
course,
but
that
would
be
the
sports
metaphor.