►
From YouTube: 2020-11-09 Crossplane Community Meeting
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,
all
right,
the
recording
has
started-
and
this
is
the
november
9th
2020
cross
plane.
Community
meeting
still
got
some
folks
joining
in
now,
but
welcome
to
all
so
biggest
news
of
the
last
week
is
that
we
released
the
0.14
release
of
crossplane
on
friday,
including
releases
or
updates
for
all
of
the
providers
as
well
too.
So
you
can
get
more
information
about
the
release
and
what
was
included
in
there
in
the
release.
A
Notes,
excuse
me,
and
there
were
some
some
nice
community
contributions
as
well
during
this
release
cycle
cosro
added
the
leader
election
functionality
to
all
of
our
providers
across
across
all
of
the
the
ecosystem
there.
So
thank
you
for
that
work
and
that
contribution
causer,
appreciate
that
a
number
of
other
notes
here
as
part
of
the
release
notes,
if
phil
was
there
a
blog
post
already,
you
said
like
this.
That
was
0.13.
B
A
B
B
A
Published
yet
yup,
okay,
is
there
enough
post.
A
Okay,
cool,
yes,
and
thank
you
to
cause,
as
we
already
mentioned
and
casey
as
well
too,
for
the
contributions
and
help
on
this
release
here
and
everyone
else.
Obviously,
too,
they
contributed
to
all
the
all
the
great
functionality
that's
in
there.
So
that
is
great
that
we
got
that
out
before
kubecon.
Here
it
was
a
nice
effort
towards
the
stabilization
and
the
path
to
to
1.0,
which
we
can
talk
about
now
here.
A
So
the
items
the
fill
did
update
the
road
map
so
that
the
items
for
are
that
we're
targeting
for
a
v
1.0
is
listed
right
here
in
the
road
map.
Phil
also
made
this
a
little
easier
to
read
to
by
including
a
table
of
contents
to
be
able
to
jump
through
the
two
releases,
a
little
bit
easier
here.
So.
B
B
Oh,
if
you
actually
jump
over
to
master,
we
clean
that
up
on
friday.
B
Yep
and
we
got
leader
election
in
thanks
to
castro
his
contribution
there,
I've
been
0.14
so
yeah,
just
some
some
cleanup,
some
updates
on
composition,
dependency
management
for
package
manager.
I
was
largely
there.
Dan
had
had
it
there
for
a
0-14,
but
then
we
decided
to
push
that
out
to
1-0,
I'm
just
a
error
on
the
side
of
stability
for
preserve
up
14.,
and
we
got
a
ton
of
work
on
the
provider
co-generation.
That's
currently
going
on.
B
We
actually
have
move
office,
got
an
initial
set
of
aws
resources
that
for
the
api
gateway,
as
well
as
ecr,
that's
being
cogenerated
now
to
the
ack
pipeline.
So
that's
looking
really
good.
Casey's
made
a
ton
of
progress
on
the
code
gen
for
terraform,
and
so
I've
linked
in
the
wip,
the
the
very
whip
set
of
generated
resources.
Just
so
you
can
get
a
sneak
peek
there
and
then
also
you
know,
matthew
christensen
has
done
a
really
great
job.
Getting
the
ac.
B
The
azure
cogen
pipeline,
going
in
combination
with
casey,
so
yeah
we're
looking
like
we're
having
a
lot
of
great
momentum
on
the
code
gen
for
the
providers
and.
B
A
Yep,
so
we're
tr-
I
don't
know
if
this
has
been
quite
yet
updated,
since
we
literally
just
made
the
last
release
on
friday,
so
we
probably
need
to
do
some
cleanup
work
on
this
board.
I
would
assume,
but
it
might
maybe
it's
up
to
date,.
B
Yeah,
it
looks
fairly
clean
on
thursday,
okay,
okay,
so
it
should
be
pretty
close.
There
might
be
one
or
two
items
that
need
to
be
added
to
remove,
but
by
and
large.
A
Okay,
great,
that's
fantastic,
okay!
So
this
link
to
the
project
board.
Here
you
can
get
a
good
overview
of
everything.
That's
been
accepted
in
the
status
of
work
in
progress
as
well
too.
The
main
themes
of
the
effort
towards
a
1.0
release
are
kind
of
what
phil
was
mentioning
there
and
specified
a
little
bit
here
in
the
roadmap
entry
as
well.
A
You
know
phil
kind
of
gave
us
an
overview
of
the
you
know
a
little
bit
of
the
details
of
these
focus
areas
and
these
themes
for
the
1.0
release
are
there
owners
of
those
that
maybe
want
to
give
a
little
bit
more
details
about
what's
going
to
be
included
or
what
the
focus
area
is.
I
think
hardening
stabilization
is
kind
of
overall
general
thing,
but
anything
specific
for
composition
to
kind
of
dive
into
there,
or
that
summary
was
good
enough.
Sufficient.
D
And
there
are
a
few
things
that
we
still
want
to
do
before
1.0,
for
example,
there
is
a
pr
that
updates
a
claim,
like
updates
on
the
claim,
should
reflect
on
the
composite
resource
yeah.
These
are
the
ones
pretty
much.
I
would
say.
A
Yeah,
I
really
like
the
the
claim
update
propagation,
so
you
can,
you
know,
change
after
initial
creation
being
able
to
change
some
of
the
values
on
your
your
claim
to
a
particular
resource
and
then
have
that
flow
through.
D
A
Update
the
resources
very,
very
useful,
so
I
really
like
that.
One
cool,
okay,
dan!
Do
you
wanna
any
other
details?
Do
you
wanna
add
around
the
package
manager
updates
for
1.0
as
well.
C
No,
I
think
it's
it's
mostly
dependency
resolution.
I
guess
one
thing
that
came
up.
I
think
simon
who's
doesn't
look
like
he's
on
the
call
today
mentioned,
which
is
kind
of
a
smaller
thing,
but
updating
the
controller
config
to
be
able
to
override
the
image
of
the
controller
which
we
didn't
support
right
off
the
bat
mostly
because
that
kind
of
it
feels
like
it,
violates
the
integrity
of
a
package
to
change
to
fundamentally
change
the
controller
image
inside
of
it.
C
That
being
said,
we
are
allowing
you
know,
passing
arguments
and
that
sort
of
thing,
so
you
can
modify
some
of
it.
His
reason
for
for
wanting
that
was
that
he
had
to
use
a
a
registry
mirror,
so
he
wanted
to
basically
use
the
package
from
there
and
then
also,
but
not
have
to
rebuild
the
contents
of
the
package,
just
basically
pull
the
package
and
push
it
up
to
the
registry,
but
he
also
needs
to
be
able
to
pull
the
controller
image
through
that
as
well.
C
So
yeah
we'll
probably
look
at
that
a
little
bit,
but
that's
really
the
only
other
major
thing.
Besides,
just
you
know
any
sort
of
performance
enhancements
and
that
sort
of
thing
for
the
package
manager.
A
And
dan,
I
know
you
had
done
like
at
least
the
initial
basic
implementation
of
dependency
resolution
in
a
branch
or
something
is
that
is
that,
like
almost
ready
to
go
into
master
already
from
that
effort,
or
is
there
like
some
cleanup
and
stuff
to
do.
C
There's
definitely
some
cleanup
to
do.
I
don't
have
a
pr
open
for
it,
and
that
was
I
guess
about
a
week
ago
now
that
I
I
gave
that
demo
and
so
that
kind
of
got
put
on
hold
last
week.
So
there's
some
cleanup,
but
the
general
model
works
as
expected.
A
Awesome
and
then
the
the
aws
reference
platform
that
we
have
that
configuration
package
there.
I
believe
that
is
up
to
date
with
what
the
schema
and
the
intent
should
be,
such
that
the
dependencies
it's
declaring,
I'm
hoping
just
work
without
even
having
to
change
the
package
or
rebuild
the
package.
But
if
it
doesn't
work,
then
you
know
happy
to
change
the
whatever
the
whatever
the
details
are:
how
to
express
the
dependency
that
package.
If
it's
not
right,.
C
Yeah
exactly
that,
with
the
what
I
have
right
now,
there
should
be
no
changes.
A
D
D
D
If
we
can
get
them
in
this
week,
I
think
we
will
we're
gonna,
do
a
release
for
provider
aws
before
the
kubecon,
so
we
got.
We
thought
that
we
can
get
those
12
new
resources
in
and
then
I
will
move
on
to
expanding
the
support
for
new
class
of
resources.
Let's
say.
B
Yeah
that'd
be
awesome,
and
then
I
think
there
were
a
couple
additional
resources
that,
like
the
I
am
access,
key
user
access
key
and
then
the
s3
bucket
policy,
the
v1
data,
one
that
I
think
would
get
pulled
into
that
patch
release
as
well.
Unless,
again,
that
got
pulled
into
zero
fourteen
or.
B
Oh
just
those
two
hanging
pr's
that
we
had
that'll
get
rolled
into
the
patch
release
too.
B
Okay
got
it
so
we'll
do
another
minor
release
of
aws,
maybe
you'd
like
towards
santa
this
week.
A
That
sounds
good
right
now:
okay,
casey
yeah
you're,
as.
E
Well,
on
the
azure
side
like
like
phil,
said
dan
has
a
pr
up
against
provider
azure,
which
adds
the
generated
types
from
aso
co-gen.
E
He
took
pains
in
the
pr
to
make
sure
it's
very
clear
that
this
was
like
just
the
types
doesn't
really
do
much
experimental
and
there
are
some
things
we
want
to
change
like,
for
example,
all
of
the
aso
parameters,
kind
of
have
an
extra
level
of
nesting
like
they
have
at
the
top
level,
all
the
things
that
are
general
to
all.
E
Aso
resources
like
tags
and
what
group
it's
in
then
there's
a
properties
field
below
that,
and
one
thing
he
wants
to
do
is
kind
of
roll
that
up
another
level
similar
to
how
our
handwritten
azure
provider
resources.
Look.
So
take
a
look
at
that
and
give
feedback
on.
E
If
there's
you
know
any
other
kind
of
you
know
considerations
you
want
him
to
think
about
as
far
as
what
the
what
the
provider
with
the
resource
type
should
look
like,
but
he
and
I
are
also
working
on
a
design
doc
to
figure
out
how
we
can
leverage
their
code
generation
that
actually
takes
those
types
and
integrates
with
the
arm
to
to
manage
the
life
cycle
of
the
types.
E
So
there's
there's
a
little
bit
of
of
complexity
there
that
we're
still
sorting
through,
but
once
we
figure
that
out
we'll
be
able
to
generalize
the
aso
code,
gen
to
also
generate
cross
plane,
reconcilers
yeah,
then,
on
the
terraform
terraform
side.
E
You
know,
like
phil
mentioned,
we
have
types
that
represent
all
the
like
primitive
types,
excluding
all
the
deeply
nested
types
which
are
a
little
more
complicated,
and
so
this
week
I'm
working
on
getting
all
the
the
nested
types,
also
in
the
go
crd
output,
so
that
that
should
be
coming
sometime
this
week.
A
All
right
and
then
for
in
terms
of
a
release
for
the
v
1.0
release
the
hope
and
the
the
effort
is
towards
targeting
the
first
week
of
december,
as
we
mentioned
on
last
call
that
and
then
kind
of
you
know.
One
reason
for
that
would
be
that
that
is
an
anniversary
for
across
plane
december.
A
Fourth
was
the
first
public
release
of
cross
play,
and
so,
if
you
could
do
it
around,
then
that
would
be
cool,
but
we
will
obviously
have
to
look
at
our
you
know
the
way
we
were
trending
with
getting
into
things
we
need
and
get
the
right
quality
and
all
that
sort
of
stuff,
as
well
too.
So
we'll
continue
tracking
that
and
pushing
towards
that.
A
A
C
Yep,
so
we
should
we're
scheduled
to
have
the
red
hat
episode
next
thursday,
at
our
usual
time,
that
is
during
cubecon,
which
might
conflict
with
some
traffic
there.
So
we
could
either
move
that
date
or
we
might
just
do
it
and
say:
hey
here's
another
kubecon
thing
going
on
and
it
can
kind
of
be
part
of
the
announcements
coming
out
that
week
so
stay
tuned
for
that
I'll
definitely
make
sure
to
post
about
it.
If
that
does
change.
A
Cool
and
that's
not
like
you,
don't
your
talk
isn't
during
that
time
slide.
Is
it.
C
A
When
do
I
speak
all
right,
cool
thanks
dan
and
then
speaking
of
kubecon
talks,
you
know
we
recorded
and
submitted
and
got
all
those
in
for
the
two
talks
that
we're
doing
dan's
talk
with
with
steve,
I
believe,
and
then
my
talk
with
with
wonderful
and
andy
from
alibaba.
Those
are
all
submitted.
Everything
looks
good
there
and
then
you
know
during
our
sessions
we'll
need
to
be
present
for
the
live
q.
A
A
at
the
end
of
the
talk
so
make
sure
you
check
your
schedule
and
see
when
your
talk
is
and
be
there
to
answer
questions,
and
then
that's
probably.
This
is
probably
the
best
time
to
mention
this
so
phil.
You
said
that
there
is
links
here
at
the
bottom
for
all
the
talks.
B
Yeah
yeah,
so
if
you
just
scroll
down
and
then
in
this
blog
post,
there's
actually
a
great
intro
video
that
dan
did
with
some
of
the
folks
over
at
packet
or
edge
metal.
Now
you
know
and
then
basically
kind
of
walk
through
the
0.13
release
and
then
some
of
the
kubecon
preview
stuff
that
we
did
with
the
new
stack
so
definitely
check
that
out.
And
then
we
have
some
office
hours
on
wednesday,
and
so
you
can
just
register
for
the
zoom
there.
B
And
then
we
have
a
couple
talks
that
jared
and
dan
are
doing
that
jared.
Just
kind
of
walked
us
through
there.
So
yeah
looking
forward.
B
And
some
good
stuff.
A
Awesome-
and
I
have
already
added
these
to
my
skid,
so
you
can
click
on
these
links
and
then
add
them
to
your
kubecon
schedule,
your
personal
schedule
as
well
too,
which
is
nice
functionality,
dan
and
steven
you.
Your
talk
here-
was
a
tutorial
format
right.
So
that's
a
like
a
good
85
minute
session
thing.
C
Yeah
awesome,
yeah
and
we'll
go
through
see.
Steven
does
a
nice
intro
to
just
kind
of
like
why
cross
playing
and
cross
when
we're
on
time
are
valuable.
So
it's
it's
a
mix
of
tutorial
and
informational
and
then
we'll
be
around
in
the
chat
as
well
to
help
any
folks
who
want
to
follow
around.
A
Awesome,
that's
exciting.
I've
already
added
it
to
my
schedule.
So
I
can
just
you
know,
join
that
at
least
awesome
and
phil.
Did
you
the
crossband
office
hours
meet
the
maintainer
session
here?
Did
you
mention
register?
Is
there
a
place
for
people
to
register
for
it
or
they
just
go
yeah.
C
A
B
So
yeah
yeah
go
ahead
and
do
that
and.
A
Is
that
on
the
is
that
links
from
the
sketch
scan
page
yeah?
So
if
you
scroll
down
a
little,
I
think
there's!
Oh
here.
It
is
here
julian,
okay,.
D
A
A
Well,
thanks
for
adding
this
to
the
blog
post,
phil,
that's
useful
to
have
that
for
more
more
eyes
on
it.
Oh
wait,
okay,
cool
and
then
so.
The
project
pavilion
booth.
I
spent
some
time
last
week
to
get
that
fully
set
up
and
updated.
So
all
of
our
assets
and
materials
and
everything
are
up
to
date.
There
and
the
booth
is
ready
to
go
added.
Everyone
added
everyone
to
staffers
as
well
too,
that
had
expressed
interest
in
it.
So
we
everyone
should
be
registered
and
be
able
to.
A
I
don't
know
if
you
can
access
the
booth
not
yet
or
not,
but
everyone
should
be
registered
and
added
as
a
staffer
to
the
booth
there
and
then
so,
as
phil
was
talking
about
here,
our
project
office
hour
session
or
meet
the
maintainers
session,
and
they
are
kind
of
calling
it
two
different
things
different
places
like
some
places,
it's
called
office
hours
in
some
places
it's
called
meet
the
maintainers.
A
I
don't
know
what
exactly
their
the
official
name
is,
but,
as
phil
mentioned,
that's
on
wednesday
at
noon,
pacific
at
three
eastern,
I'm
still
looking
for
someone
who
it
to
be
to
take
to
drive
this
to
give
a
presentation
and
kind
of
drive
the
session
there.
So
I
think
it's
a
really
good
opportunity
to
kind
of
get
get
out
there
and
you
know
kind
of
kind
of
have
some
interface
with
the
public
in
the
community
a
little
bit
on
crossplane.
A
So
if
anyone
is
interested
in
that,
just
let
me
know,
I
think,
isn't
it
is
nick
on
the
call,
no
he's
not,
but
I
think
kirsten
like
just
put
nick's
name
name
down
on
the
sign
up
sheet.
So
we'll
see
when
nick
notices
that
but
yeah
it's,
I
think
it's
open
and
if
nick
wants
to
do
it,
that's
absolutely
fine,
but
anybody
who's
interested
in
driving.
This
is
what
I'm
welcome
to.
A
Right
and
then,
as
we
mentioned
before,
we
started
the
official
call
here
in
the
recording
the
call
for
proposals
for
the
next
cube.
Con
is
already
up
and
available,
and
the
deadline
is
december
13th.
So
you
don't
get
quite
a
full
month
between
the
end
of
this
cube
con
and
the
time
to
submit
a
proposal
for
the
next
one.
A
One
good
thing.
I
was
speaking
with
the
cncf
representatives
this
morning
and
they
we
gave
them
some
feedback
about
the
this
kubecon
here.
That's
just
about
to
start
for
north
america
that
the
the
length
of
time
in
between
being
accepted
to
speak
at
the
conference
and
the
due
date
for
recording
your
talk
was
very
short.
This
time
kind
of
it
didn't
really
work
well
for
for
some
folks,
including
myself.
A
So
he
gave
that
feedback
this
morning,
but
they
had
already
put
up
this
page
for
the
call
for
proposals
for
the
next
one,
and
I
think
they
got
that
they
said
that
they
got
that
feedback
from
a
lot
of
people,
that
there
wasn't
enough
time.
So,
there's
a
full
two
months
now
in
between
notifying
you
that
your
talk
was
accepted
and
and
at
least
the
the
doing
the
conference.
So
I
believe
they
said
there's
more
time
too
of
when
the
due
date
is
to
upload
your
your
talk
as
well
too.
A
So
it
seems
like
that
feedback
was
accepted.
So
that's
good,
okay,
so
that's
kubecon!
You
know
we
anybody
who
wants
to
discuss
things
or
has
questions
or
anything
they
can
find
us
in
our
slack
and
you
know
slack.crossplane.io,
and
we
can
talk
more
about
kubecon
and
stuff
and
we'll
be
online
that
whole
week
and
at
the
kubecon
booth.
So
looking
forward
to
chatting
with
everybody
there
move
off.
You
already
mentioned
these.
These
new
generated
resources
right,
there's
nothing
else
to
go
into
there.
Yeah.
A
Cool
and
then
casey
you,
you
had
mentioned
this
code
generation
pr
as
well
too.
Right
was
there
more
to
mention
there.
Oh
it's
what
I
talked
about:
okay,
cool
cool
and
then
we
also
talked
about
krish's
resources
that
went
in
for
aws
after
the
provider.
Aws
was
released
so
that
will
be
included
in
the
next
minor
release
that
we're
planning
on
doing
this
week.
That
incorporates
both
of
the
generated
resources
for
aws
and
krish's
handcrafted
with
love
provide
resources
as
well
too.
A
A
A
Okay,
cool
yeah,
so
kasper
do
you
want
to
kind
of
give
us
a
bit
of
a
description
here
about
this
effort
and
you
know
kind
of
the
scenarios
that
tilt
solves
and
helps
with.
F
Yeah
sure
so
tilt
is
a
developer
tooling,
that
mostly
you
work
with
it.
When
you
are
working
against
a
kubernetes
cluster,
what
it
does
is
it
watches
some
folders
and
does
something
with
it.
That's
something
can
be
just
building
the
image
reloading
the
images
deploying
a
new
workload
or
something
like
that
which
in
this
case
it
might
be
a
good
idea
to
use.
For
example,
we
can
just
tilt
up
against
the
the
core
crossplane
and
point
to
any
local
provider.
F
So
what
you
end
up
doing
is
essentially
just
moving
back
and
forth
between
your
editor
and
the
the
terminal
to
see
if
the
the
changes
is
applied
correctly
check
the
the
queue
code
logs
to
see
if
the
the
changes
is
done
correctly
or
not.
I
can
quickly
demo
something
if
there
is
time
otherwise.
A
F
Okay,
so
what
I
did
is,
I
just
went
ahead
and
started
a
calculus
locally
and
in
the
in
the
meantime,
actually
I
updated
the
builds
up
module
as
well
and
added
the
corresponding
teal
target
as
well.
So
what
what
we
need
to
do
essentially
stop
and
get
up.
F
A
F
F
Yes,
it
essentially
does
a
little
bit
more
than
that,
but
yeah.
A
F
The
essence
of
it
so,
for
example,
one
example
of
it
it
watches
for
changes
in
any
of
these,
and
then
it
executes,
for
example,
this
line
whatever
that
line
is,
for
example,
building
the
the
cross
plane
itself
outside
of
docker
image.
Then
it
goes
ahead.
You
can
define
it
to
build
a
docker
image
out
of
it
then
deploy
a
helm
chart
out
of
that
which
uses
this
on
the
fly,
images
and
what's
cool
about
it.
Is
that
whenever
there
is
a
change
here,
it's
not
going
to
change,
execute
the
whole
thing
again.
F
It
knows
that
it
builds
it
and
on
the
fly,
replace
the
binary
inside
the
running
container.
So
it
takes.
It
saves
a
lot
of
time,
so
changing
initial
running
the
tilt
may
take,
for
example,
like
I
don't
know,
maybe
10
seconds,
but
changing
the
goal
file
and
saving
it
it
it's
going
to
reload
the
the
binary
in
the
in
the
container
less
than
a
second
something
like
that,
so
it's
quite
efficient
in
that.
A
Cool
cool
cool
and
with
your
experiences
so
far,
does
it
have
with
two
questions
one
like
if
it
tries
to
sync
your
changes
to
your
development
cluster
with
like
every
time
you
save,
does
it
have
much
performance
impact
in
terms
of
like
trying
to
do
a
lot
of
things
in
the
background
and
using
some
resources
or
does
it
ever
deploy?
A
F
F
So
this
uses
the
direction
of
the
tilt
to
to
run
something,
for
example,
if
I
change
a
martin
file
right,
so
that's
that
is
something
that
potentially
can
be
limited,
but
otherwise,
if
you
just
put
it
in
the
whole
folder
in
the
world
repository,
it
still
is
not
super
aggressive
for
your
second
question.
F
Yes,
that
is
something
that,
for
example,
if
you
are
working
on
a
on
a
feature
which
touches,
let's
say,
four
different:
go
files
and
you're
working
actively
in
all
of
them,
and
if
you
wanna,
buy
habits,
change
something
safe,
go
to
the
next
file
change,
something
say
by
each
say:
it's
going
to
do
something
on
the
cluster,
so
for
some
time
in
between
it
does
something
it
deploys.
Something
in
your
cluster
and
your
cluster
or
your
workload
rather
is
unhealthy,
because
the
whole
feature
is
not
implemented
yet.
But
then
again
it's
not
a
big
deal.
F
F
That
depends
either
it's
a
it's
a
right
upfront
error
from
the
teeth
that
you
would
immediately
see.
There's
a
error
or
so
the
binary
was
not
able
to
build
properly
or
the
the
problem
is
maybe
more
subtle
and
you
save
it.
The
team
was
able
to
deploy
it,
but
the
error
would
would
pop
up
somewhere
on
the,
for
example,
deployment.
F
Then
again,
you
would
immediately
get
the
feedback
under
seconds.
Something
like
that.
You
change
something
you
go
in
your
bracket.
There's
some
error
popped
up
that
you
would
immediately
see
the
logs
of
the
of
your
parts
in
the
browser.
You
don't
you
don't
necessarily
need
to
just
dig
in
your
terminal
to
see
okay.
What
was
the
pod
name
again?
Do
I
need
to
follow
the
log
or
whatever
everything
is.
A
F
No,
it
was
an
independent
effort,
I
think.
Actually,
you
know
the
there
was
two
per
person
from
they
were
ex-googler
and
they
started
the
project.
F
A
Awesome,
that's
cool.
That
sounds
that
sounds
good
yeah
be
interested
to
see.
You
know
like
how
the
how
the
experience
goes,
or
you
know,
as
you
kind
of
finish
off
that
that
that
addition
there,
how
you
know
how
it
seems
like
it's
got
a
lot
of
potential,
so
that
sounds
pretty
cool.
Did.
Did
you
dan
makeup?
You
got
a
chance
to
look
at
this
already
too
right.
Did
you
already
have
some
some
ideas
about
you
know
using
it
as
a
dev
tool
and
and
the
improvements
that
come
from
it.
C
All
right,
I
definitely
think
it's
a
good
idea.
I
haven't
reviewed
this
pr
in
depth
yet
or
anything
yeah.
A
Okay,
yeah
cool
yeah.
I'm
excited
to
see
the
network
continue
on
that.
Thank
you
for
that
addition,
because,
that's
really
that's!
It
looks
really.
F
A
Yeah
no
worries
no
worries
cool,
so
that
is,
I
think,
that's
all
the
topics
that
we
had
on
the
agenda
is
there
anything
else
that
folks
wanted
to
bring
up
while
we're
still
together.
A
All
right:
well,
then,
next
week
is
kubecon,
we'll
see
everybody
there
and
online
for
sure
should
be
a
fun
and
exciting
busy
week
and
then
we'll
all
stay
in
touch
this
week.