►
From YouTube: Cluster Addons 20201013
Description
Recording of the cluster addons biweekly meeting held on 20201013
A
Hello
everybody.
This
is
the
cluster
add-ons
bi-weekly
meeting
today
is
tuesday
october
13th
2020..
I
am
your
moderator,
facilitator,
justin,
santa
barbara.
I
work
at
google
a
reminder
this
meeting
is
being
recorded
and
what
we
put
on
the
internet
and
also
to
please
be
mindful
of
our
code
of
conduct.
There
aren't
too
many
people
here
today,
so
we
probably
don't
need
to
use
the
raise
hand
feature,
but
if
it
gets
exciting,
then
we
can
presumably
do
so.
A
A
If
everyone
anyone
is
new,
I
don't
see
anyone
new
a
review
of
the
agenda
items
and
then
general
discussion.
I
will
scroll
back
to
last
time
to
see
if
there
are
any
items
you
want
to
follow
up
on,
looks
like
the
only
one
that
I
can
see
is
an
oci
image
cap,
which
last
time
we
wrote
that
we
thought
it
was
a
good
idea.
It
needs
an
owner
and
nick
will
follow
up
with
evan.
I
don't
know
if
nick
did
that,
evan.
B
A
B
It's
it's
something
that
we
went
ahead
and
implemented
for
operator
framework
stuff
and
it
seems
to
be
generally
working
well
as
a
pattern.
It
does
make
a
lot
of
sense
to
look
at
oca
artifacts
as
well,
but
there
are
some
roadblocks
to
actually
using
that
on
on
the
cluster
right
now,
with
like
cri,
for
example,
doesn't
understand
those
favorite
effects.
B
A
Yeah,
my
guess
is
particularly
a
bit
about
how
it
could
like
how
it
can
be
used.
I
think
that
would
be
super
helpful
to
get
so
from
everyone
sort
of
focus
on
it,
and
I
will
once
again
try
to
take
a
look.
We
should
probably
put
a
link
in,
I
am
not
sure
of
the
link,
but
if
anyone
has
a
link
to
it,
if
they
can
paste
it,
we
can
put
it
in
the
notes.
A
B
B
Is
it
uses
builda
like
a
separate
out-of-process
build-up,
basically
to
pull
the
images
based
on
the
specs,
the
pulse
specs,
which
is
fine
and
works
fine
for
most
things,
but
then,
if
your
node
has
crit
special
credentials
loaded
into
it,
if
your
cubelet
is
authorized
for
private
repositories
or
something
like
that,
you
lose
all
of
that
and
so
for
unpacking
them
for
operator
framework
use
cases.
We've
just
been
using
a
pod
with
a
bunch
of
init
containers
that
extracts
everything.
B
So
I
talked
to
the
maintainer
of
that
a
little
bit
and
have
like
a
prototype
that
uses
cri
instead
of
builda,
but
there's
a
bunch
of
kind
of
hacky
stuff
around
that,
because
cri
doesn't
expose
a
whole
lot,
which
I
guess
is
a
long-winded
way
of
saying.
Maybe
I
should
include
some
of
the
things
around
the
volume
plug-in
in
this
cap
as
well,
because
I
think
that
that
actually
makes
it
significantly
more
useful.
A
Thank
you
for
that.
This
is
yeah.
This
is
great
and
timely,
and
I
think
we
can.
I
will
definitely
have
a
look
at
this
particularly
wrap
up
earlier.
It
seems
like
I'll
look
at
this
immediately
afterwards.
It
seems
to
me
like
whenever
I
don't
do
it
immediately.
It
falls
off
the
radar
and
if
anyone
else
has
any
comments
on
this
pr,
we
should
definitely
reopen
it.
Maybe
you
wanted
to
do.
A
A
A
A
A
C
C
I
added
this
item.
We've
got
a
couple
plus
ones.
I
personally
think
that
this
is
a
good
idea.
It
sounds
like
you
think
so,
too
justin.
Maybe
if
you
want
to
add
your
plus
one,
then
we
can
go
ahead
and
merge
it.
I
do
yes,
okay!
Well,
oh
yes,
I
figured
that
this
was
a
good
governance
thing
to
cover,
since
johnson
wants
to
double
down
on
their
contributions.
C
A
A
But
yes,
that's
that'll,
be
great.
I
don't
see
a
wretched
thunder,
pier
so
but
yeah.
Thank
you
for
all
your
hard
work,
and
that
is
a
great
one,
and
if
anyone
wants
to
be
a
a
reviewer
or
not
or
I
think
people
should
hopefully,
yes,
you
have
to
start
or
the
the
path
is
that
you
start
as
a
reviewer
and
that
you
later
become
an
owner.