►
From YouTube: Working Group: 2021-03-04
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
Hey,
what's
up,
everybody
welcome
to
working
group?
Actually,
it's
been
rebranded
right
to
office
hours.
Usually
big
j
is
going
to
be.
Javier
is
going
to
be
running
these,
but
for
today,
just
for
today
he
had
other
obligations.
So
I'm
going
to
be
running
it.
If
that's
all
right
just
want
to
keep
in
mind
that
there
is
a
dock.
A
That
is,
you
know
that
you
can
fill
out
with
agenda
items,
I'm
going
to
link
it
in
the
chat
and
I'll
give
you
maybe
like
a
minute
to
fill
something
out:
okay
and
how
about
how
about
some
tunes.
While
you
fill
stuff
out.
B
A
Sorry,
I
always
want
to
give
credit
to
hardworking,
recording
artists.
So
in
the
chat,
that's.
A
A
Y'all
can
see
my
screen.
Here's
the
agenda
for
today
we're
gonna
start
recording
and
I
do
have
an
architectural
review
of
kpac
that
I
wanted
to
share.
But
please,
if
there
are
any
other
items,
people
want
to
discuss,
we
can
we
can
go
through
with
it
sound
good,
okay.
A
So,
okay
back,
I
have
a
little
presentation
here
going
to
be
very
high
level.
So
kpac
is
an
open
source
project
that
is
basically
another
platform
right.
You
think
about
what
a
platform
is.
It's
basically
going
to
be
something
that
uses
our
life
cycle
to.
Do
I
don't
know
container
type
things,
but
first
of
all,
let's
just
talk
about
you
know.
I
don't
know
what
page
everyone
else
is
on.
Let's
just
talk
about,
let's
just
go
on
same
page
right.
This
is
a
kubernetes
cluster
right
in
this
very
smallest
form.
A
This
is
what
it
normally
looks
like
you
have
an
api
at
cd
and
a
worker,
and
you
basically
usually
talk
through
it
through
kukato
you
can.
You
can
use
other
methods
right,
but
you
usually
use
q
cuddle
to
talk
to
it.
The
the
std
is
where
all
your
metadata
is
stored.
Api
does
api
things
and
the
worker
is
where
your
container
workflows
get
run
right.
A
A
The
reason
we
have
this
is
because,
when
you're
sending
desired
state
to
the
api
through
cuddle
you're
sending
in
yamo,
which
is
usually
pre-written
right,
but
for
kpac,
we
want
to
make
it
a
little
bit
more
dynamic.
We
want
to.
We
don't
know
all
the
fields
ahead
of
time,
so
we
basically
need
our
brain
well,
capex
brain
to
be
basically
being
a
container
and
the
way
this
thing
works.
Is
it
talks
to
the
api?
A
B
A
With
using
bill
packs-
and
it
dumps
it
in
a
registry
right,
if
you
can
just
think
of
it
as
pac
in
the
cloud-
if
that
makes
things
a
little
bit
easier
and
the
way
it
does,
that
is
by
basically
making
these
build
containers,
that's
official
terminology,
and
these
are
a
little
bit
more
framework
right.
The
the
controller
is
going
to
be
there.
Your
entire
entire
span
of
your
install,
but
the
build
control
crawlers
are
going
to
be
there.
A
A
Export
will
show
all
my
information
out
to
the
registry,
and
so
just
a
little
bit
of
an
architectural
thing
here
right,
because
kubernetes
is
more
about
desired
state.
It
is
more
declarative
than
imperative
right.
It's
a
little
tricky
how
you
have
to
get
these
things
to
happen
in
sequence,
right,
like
let's
say
with
pac,
you
can
individually
say:
hey
I'm
making
this
container
and
take
the
outputs
of
this
to
the
next
container
and
right
right.
A
You
can
do
things
like
this,
but
because
we
we
can
only
really
make
one
container
what
what
kpac
is
doing
is
making
a
build
container
and
then
each
of
these
life
cycle
phases
are
implemented
as
discrete
init
containers,
right
that
that's
that's
how
it's
trying
to
get
sequential
behavior
happening
basically,
but
for
the
most
part
you
know,
if
you
can
just
get,
you
know,
wrap
your
mind
around
that.
That's
really
what's
happening,
the
completion,
which
is
the
actual
container
itself.
This
is
the
actual
thing
really
doesn't
do
too
much
right.
A
It's
really
just
there
to
satisfy
the
container
spec
right,
but
this
is
how
it
normally
works.
Cool,
okay,
the
other
big
component
here
is
kp.
So
kp
is
honest.
Honestly,
to
be
honest,
it's
really
just
supposed
to
be
like
a
something
you
pair
up
with
cubecardo
right,
like
you
could
do
everything
kp
could
do
it's
basically
just
you
know
a
way
to
interact
with
the
api
to
talk
to
your
custom
objects,
but
we
made
kp
to
be
a
little
bit
simpler
for
or
a
little
bit
more
kp
specific
right.
A
It's
basically
just
dna
container,
and
I
guess
just
for
parity
or
you
know
just
to
you
know,
make
things
as
least
complicated
as
ever
you
have
this
completion
container,
which
again
doesn't
doesn't
do
as
much
as
you
might
think.
Okay
and
lastly,
just
wanted
to
talk
about
this
itself
right.
The
image
itself
right,
which
we
know
as
the
builder
image
in
cave
pack,
it's
a
little
bit
more.
A
It's
just
a
little
bit
different
right.
A
builder
image
is
made
of
usually
the
the
same
things,
but
the
metadata
is
just
our
you
know
it's
just
structured
in
a
different
way.
You
normally
have
a
secrets
right,
and
this
is
a
kubernetes.
These
are
kubernetes
objects
that
I'm
pointing
to
you
have
a
secret.
That's
you
know,
stored
somewhere
that
the
builder
has
access
to
which
it
uses
to.
You
know
talk
to
your
registry
and
github.
A
Will
not
you
have
a
stack
with
a
cluster
stack
right,
which
is
basically
just
the
metadata
object
around
your
stack
right.
You
have
cluster
store,
which
is
again
a
metadata
object
around.
Basically,
your
build
packs
right,
but
these
all
these
all
work,
these
all
work
to
make
this
metadata
object
of
a
builder
which
corresponds
to
a
real
container
image.
That
capex
builds
to
you
for
you
and
puts
in
the
registry
which
it
uses
to
build
all
these
build
pods.
A
Okay!
It's
sorry,
sorry!
If
that
description
is
a
little
clumsy,
but
a
lot,
a
lot
of
the
actual
difficulty
of
kpac
is
really
around
the
metadata.
So
I
tried
to
distill
it
to
what's
a
real
thing
and,
what's
not
like
you,
know
something
that's
stored
in
scd
or
whatnot,
and
that's
all
I
have
for
you.
I
was
wondering
if
you
have
some
questions.
B
I
definitely
have
some
questions,
especially
around
this
last
section
here,
so
I
guess
maybe
you
could
elaborate
a
little
bit
more
about
the
idea
of
builders
right
is.
B
Are
we
saying
that
kpac
does
not
have
the
support
for
me
to
be
able
to
provided,
like,
let's
say
the
heroku
builder
or
the
google
builder
poker
so
forth,
given
that
it
has
these
like
pre-built
notions,
and
it
creates
like
this
ephemeral
ad-hoc
builder,
or
am
I
completely
missing
the
the
point
here.
A
B
A
A
kubernetes
object
called
a
builder
there's
a
kind
if
you,
if
you
know
kubernetes,
there's
kinds
of
objects,
so
you
have
to
no
matter
what
you
have
to
make
the
yaml.
That
says
this
is
my
builder
and
then
it
points
to
this
container
image
x
y.
You
can
make
you
can
make
it
your
own.
You
can't
you
can
make
these
your
own,
like
out
of
these
custom
objects.
A
But
your
question
was,
you
know:
can
I
use
a
honestly?
You
probably
want
to
do
it
like
this
right
that
that
way,
you
have
insights
into
into
like
the
discrete
pieces
of
a
builder
right
like
what
the
stack
is
and
what
the
store
is
and
whatnot.
But
theoretically.
B
A
Okay,
all
right,
maybe
okay,
I'll
try
my
best
here
right.
Like
you,
the
reason
you
want
these
objects
is
so
that
kubernetes
can
give
you
these
reconciliation
rules
right,
like
let's
say
you
update
a
bill
pack
right,
which
updates
this
metadata
in
a
cluster
store.
Kubernetes
knows:
oh,
my
cluster
store
is
associated
with
a
builder
I'm
going
to
recreate
my
builder
because
I've
recreated
my
builder
all
my
build
pods
that
have
been
built.
This
particular
a
particular
app
into
a
container
image
needs
to
be
rebuilt
right.
A
That's
why
you
want
all
these
metadata
objects
right
because
pac,
for
instance,
doesn't
have
all
these
reconciliation
loops
you!
You
don't
need
to
register
these
other
abstractions,
but
it's
still
the
same
thing
like
literally,
we
are
talking
about
a
run
image,
a
build
image,
some
build
packs
right
at
the
end
of
the
day,.
B
Then
that
builder
object
at
the
top
right.
Is
that
built
like?
Maybe
you
could
show
it?
I
don't
know
if
you
have
one
handy
like
the
definition
of
that
builder,
like
is
that
builder
then
pointing
to
things
that
are
in
the
cluster
stack
and
the
build
packs
that
are
on
in
the
cluster
store
as
references
or
are
they
completely
like?
You
know
two
separate,
okay
different
entities.
I.
A
Will
absolutely
the
tutorial
is
pretty
good.
I
will
try
my
best,
so
this
is
a
builder
definition
right
like
I
said
it
has
a
service
account
and
then
a
stack
which
is
another
kind
of
object
and
a
store
which
is
another
kind
of
object,
and
I
didn't
talk
about
this
in
the
in
the
whatever
the
slides,
but
you
know
you
can
order
the
the
bill
packs
that
they
show
up
in
right.
B
A
B
A
Is
that
show
you,
but
beneath
the
cursing
a
little
bit.
B
Yeah
yeah
totally.
I
have
more
questions.
I
don't
know
if
we
want
to
go
down
this
rabbit
hole,
but
if
other
people
have
any
more
high
level
questions,
maybe
I
could
yeah
if
we
omit
an
order,
can
the
build
image
already
have
build
packs
on
it
and
we'll
execute
through
those?
I
know
you
wouldn't
get
the
benefits
of
getting
build
pack
updates
like
individually,
but
could
you
use
an
existing
builder
and
create
the
metadata
around
it
and
still
have
it
execute
without
too
much
ceremony.
A
B
B
B
B
A
You
know
I
want
to
say
yes,
I
want
to
say
yes,
but
I
can't,
I
can't
say
it
with
certainty.
Sorry
this
was
this
was
supposed
to
be
an
intro.
You
guys
are
asking
her.
A
It's
all
good!
No,
it's
all
good!
Honestly!
I
want
to
say
yes,
but
I
just
honestly
I
just
can't
recall
yet
the
the
normal
depo
path
is
to
create
your
own
builder,
though.
A
A
Okay,
yeah,
you
know,
I
don't
I
don't
want
to
belabor
this.
Do
we
have
any
other
thoughts,
questions.
B
Do
you
know
I
guess
what's
next
for
kpac
as
far
as
like
any
features
or
anything
like
that,
or
is
it
like
stable
in
a
in
a
good
state
right
now,
where
it's
just
functional.
A
Here's
what
I'll
say
I
do
know
right.
You
know
I
do
know
that
they
were
working
very
hard
to
get
to
this
1-0
release.
Where
things
were.
You
know
basically,
whatever
feature
set
that
they
had
went
in
and
you
know
they
did
one
one
after
that,
and
I
think
things
are
are
very
much
settled
at
this
point
right.
A
There
isn't
like
a
a
big
rush
to
accomplish
another
milestone,
so
to
speak,
so
I
don't
know
what's
on
next
on
deck,
but
that's
you
know
if
you
can
think
of
like
your
product
cycle,
that's
sort
of
the
spot
that
they're
in
right
now.
A
A
Okay,
maybe
I
should
preface
this
yes,
I
used
to
be
on
the
team.
I
haven't
been
in
a
while
and
no
you're
asking
again
hardcore
questions.
B
Fit
in
the
flow,
but
that's
probably
related
to
even
like
some
of
the
project
tamil
stuff.