►
From YouTube: Community Meeting, March 7, 2022
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
everybody
Welcome
today
is
March
7th.
This
is
the
kcb
community
meeting.
If
you
are
just
joining
us,
we
have
an
issue
in
our
GitHub,
for
this,
so
I
will
paste
a
link
into
the
meat
chat.
If
you
would
like
to
add
any
items
to
the
agenda,
please
feel
free
to
do
so
and
we
do
try
to
use
racecand
in
Google
meet.
A
So
if
you
are
interested
in
chatting,
please
hit
the
raise
hand,
button
and
I'll
do
my
best
to
moderate,
and
if
there's
anybody
who
is
new
to
kcp
new
to
the
meeting
this
week-
and
you
would
like
to
say
hello,
please
feel
free
to
hit
the
raise
hand
button
and
introduce
yourself
if
not
that's,
okay,
but
I'll
I'll,
pause
here
and
see
if
anybody
does
want
to
say
hi.
B
So
I'm
I'm
Adam,
konowsky
I
work
over
on
the
ansible
project
and
I've
actually
stumbled
on
kcp
because
we're
looking
at
using
it
in
CI
system
we're
building
for
our
Upstream
users
and
it's
pretty
cool
tool
and
now
I'm
here.
So
that's
excellent.
A
B
A
David
wanted
me
to
demo
something
I
have
an
installer
that
I've
built
with
ansible
that
I've
been
using
locally.
That
can
build
and
stuff.
That
might
be
useful
and
I
can
show
you
later.
So,
if
you
have
time
more
than
happy
to
show
you
how
to
use
it.
A
Okay,
so
with
Mike
to
preview,
kcp,
Edge,
Edge
placement,
so
so
Mike
are.
D
Yes,
I
am
I
can
go
through
for
those
of
you
who
haven't
seen
it
otherwise
our
thoughts
on
on
interface
for
the
edge
placement
problem.
So,
as
you
know,
we
do
have
this
group
working
on
edge
multi-cluster.
It
is
a
distinct
problem
from
TMC.
Let
me
try
and
share
here
and
see
if
I
can
go
briefly
through
that
I'm
just
thrashing
over
here
to
the
actual
interface
okay.
Let's
start
with
that
and
then
go
back
to
the
meeting
and
try
to
share
my
screen.
D
Let's
see
here
present
entire
screen,
let's
see
if
that'll
work
share,
Chrome.
Okay,
let's
see
sharing
my
screen.
Okay,
so.
D
Right
and
let
me
make
it
a
little
bit
bigger
all
right,
so
so
in
the
in
the
Edge
MC
repo.
We
do
have
a
package
for
apis.
We
have
an
API
Group
called
Edge
and
in
the
V1
Alpha
One
you
will
find
Edge
placement.
D
So
the
idea
here
is
that
this
is
we
started
with
the
TMC
placement
and
made
the
changes
that
we
think
are
appropriate
for
Edge
I
will
say
just
sort
of
qualitatively
the
the
biggest
one
is
that
it
is
multicast
rather
than
any
cast.
So
like
the
TMC
placement,
it
has
what
I
call
a
wear
predicate
that
selects
amongst
possible
in
in
our
case
we
call
them.
D
Edge
clusters
or
I
may
speak
more
generally
of
destinations,
and
actually
this
is
in
particular
in
service,
we're
doing
a
proof
of
concept
that
is
deliberately
Limited
in
scope.
We're
not
exploring
all
of
our
ideas,
but
we
are
exploring
some
of
them,
and
this
multicast
is
definitely
one
of
the
ideas
we
are
exploring.
One
of
the
things
we're
not
exploring
is
the
possibility
of
multiple
Edge
clusters
in
one
Edge
location.
D
We
do
have
a
more
particular
usage
of
vocabulary
here
and
so,
while
TMC
I
think
has
a
very
general
potential
use
of
the
location
concept
or
data
structure
or
object
type,
we're
actually
poaching
on
the
sync
Target
and
location
from
TMC,
but
we're
giving
a
particular
interpretation
to
location
one,
that's
natural
for
Edge,
you
know
you
think
about
Edge
locations
and
in
general,
Edge
location
can
have
multiple
clusters,
but
in
this
case
in
this
PSC
we're
saying
it's
one
to
one
so
there's
a
one-to-one
association
between
sync
targets
and
location
in
this
POC
and
this
interface
with
us
at
this
level
of
development
anyway.
D
So
a
the
where
predicate,
which
so
you
know,
as
usual,
an
edge
placement
right.
It's
got
a
spec
and
a
status
and
in
the
spec
there's
a
where
predicate,
which
is
a
you
know
like
in
TMC.
It's
a
slice
of
label
selectors
over
location
objects,
I'm,
not
entirely
clear
on
whether
in
TMC
I
think
in
TMC.
It's
it's
a
selector
on
sync
targets,
but
I
think
it
makes
well.
D
It
doesn't
much
matter
here
because
it's
one
to
one
but
I,
think
it
defined
it
to
be
a
label
selector
on
location
objects
and
then,
as
the
spec
also
has,
of
course,
as
as
it's
it
really
this
this.
The
placement
object
here
is
a
binding
between
what
and
aware
right
so
the
wear
is
is
similar
to
the
TMC
placement,
but
it's
multicast
really
in
any
class
anycast
of
what
we
started
with
the
this.
D
So
that
is
really
the
what
and
the
where
in
an
edge
placement.
The
other
thing
I'll
say
about
Edge
is
a
difference.
Let's
see
somebody
put
their
hand
up
and
I'll
get
you.
Let
me
just
say
one
more
thing:
in
TMC
what
has
to
be
transported
is
relatively
bound
and
known
at
development
time,
because
in
TMC
only
the
computation
gets
moved
and
everything
else
stays
behind
at
the
source
of
server
in
edgemc.
D
We
want
to
transport
everything
and
produce
self-sufficient
Edge
clusters,
so
the
set
of
things
that
have
to
be
transported
is
not
known
at
development
time,
so
I'll
stop
there
and
ask
for
questions
and
I
can't
quite
see
in
this
format
who
raised
their
hand.
Let's
see,
who
is
that.
A
E
Sorry
that
was
muted
I
was
just
saying
that
yeah,
what
you
mentioned
about
non
you
know
being
able
to
define
the
what
perisource
and
not
per
namespace
I
think
we
already
have
an
issue
for
TMC
as
well,
because
there
was
also
the
requirement
to
possibly
Point
directly
to
some
resources
and
not
you
know,
stick
to
the
namespace
scope
in
terms
of
of
defining
the
what
in
the
placement.
So
that
might
be
interesting.
E
You
know
at
least
to
have
something
you
know
converging
or
or
consistent
here
that
we
have
the
same
on
TMC,
but
we
didn't
implement
it.
F
D
Please
do
review
what
I've
drafted
here
and
tell
me
if
you
think,
that's
appropriate
or
if
you
think
something
different
would
be
appropriate
to
converge
on.
E
We
might
you
know,
take
from
what
you
you
need
as
well.
I
mean
I,
don't
know
just
just
mentioning
that
the
the
same
need
exists
on
both
sides.
Obviously,.
D
Very
good,
thank
you.
We
have
another
hand
up
mengirdus.
C
Yes,
I
was
wondering:
is
this
still
a
path
to
go
and
was
there
any
considerations
to
do
something
more
like
Helm
stuff,
where
you
just
object,
encapsulates
a
different
object
or
list
of
objects
and
just
deliver
those
like
I'm,
just
interesting
that
what's
the
thinking
overall
on
this?
Yes,.
D
That's
a
very
good
question:
it's
a
question
that
we've
struggled
with
you
know
we
I
went
back
and
forth
throughout
last
year
on
this.
It
is
definitely
a
possible
way
to
go.
You
know
the
the
way
I
characterize
It
is
Well.
D
The
way
I
would
put
it
is
you
know
in
edgemc
you
need
some
kind
of
a
container
for
the
description
of
the
workload
and
the
question
is:
do
you
use
as
your
container
a
kcp
workspace
or
in
general,
a
I
describe
it
as
a
denatured,
API
server,
you
know,
that's
one
kind
of
path
to
go
and
the
other
is
to
define
a
container
object
type
and
you
can
find
other
projects
that
do
that.
For
example,
ACM
has
defined
a
container
object
type.
D
Another
way
you
can
go
is
in
some
sense
delegate.
So
git
Ops
is
all
about
saying,
oh
well,
the
container
is
git
rather
than
anything
in
kubernetes,
the
the.
D
So
that's
that's
another
way
you
can
go
and
in
fact
my
first
proposal
for
Edge
MC
last
year
was
exclusively
focused
on
git,
Ops
and
I
was
proposing
that
we
adopt
get
as
the
container
and
people
said.
Well,
that's
great
for
some
use
cases,
but
not
all
so
I
want
something
that
is
more
generic
and
works
with
the
whole
kubernetes
ecosystem.
D
So
that's
why
I
went
with
the
container
is
something
that
looks
like
a
regular
kubernetes,
API
server
and
then
the
consequence
of
that
is
that
it
has
to
be
denatured
because
it
has
to
be
only
a
container.
It
needs
to
not
process
the
objects
it
needs
to
just
hold
them,
because
the
actual
activity
on
the
objects
needs
to
be
happening
in
these
independent
self-surgent
self-sufficient
Edge
clusters,
not
in
the
central
place,
that's
holding
the
description.
C
D
So
there
is
an
outline
of
this
POC
that
is
merged
in
the
edge
MC
repo
that
you'll
find
that
there's
a
docs
folder
that
has
a
subfolder
for
this
POC.
D
We
do
not
currently
have
like
a
PR,
that's
discussing
the
overall
design
or
architecture,
I
believe
Andy.
We
do
have
do.
We
have
a
mailing
list.
G
Okay
and
that's
where
all
our
docs
are
located,
that
describe
the
interfaces
and
the
and
the
demonstration
that
we
planted
cool.
C
D
Let
me
move
on
to
the
status,
so
the
status
right
now
is
very
preliminary
and
spare
it's
just
tracking
the
generation
of
the
spec
and
the
number
of
locations
that
matched
in
general.
The
problem
of
returning
reported
state
from
The
Edge
extends
well
beyond
this
object.
D
You
know
we
have
a
fundamental
problem
in
kubernetes
which
connects
to
the
previous
question.
Actually,
the
the
kubernetes
object
types
are
defined
on
the
assumption
that,
for
every
object,
it's
basically
going
to
have
one
running
or
used
copy,
and
you
have
to
set
you
know
for
every
desired
State,
there's
one
reported
State
and
that
there's
a
status
section.
That's
these
data
types
it's
designed
to
report
on
one
of
them,
but
in
this
multi-cluster
world,
where
you're
explicitly
about
this
is
a
prescription
for
many
of
them.
D
That
data
type
is
not
appropriate,
so
part
of
the
edgemc
problem
that
I'm
not
trying
to
present
our
answer
for
now
is
how
do
we
deal
with
these
multiple
reported
States
I'll
just
say
briefly,
there's
kind
of
a
two-part
answer.
One
is
you
can
try
to
return
all
of
the
reported
States
and
keep
them
somewhere?
D
The
kind
of
the
in-spirit
of
answer
is
a
separate
objects,
so
this
POC
has
mailbox
workspaces
in
the
center
so
for
each
Edge
cluster
there's
a
corresponding
mailbox
workspace
in
the
center
that
has
all
the
objects,
and
so
the
individual
object
reported
State
can
appear
in
the
center
in
the
mailbox
workspace
objects,
but
back
in
the
original
description,
which
is
not
mailboxed,
there
has
to
be
some
kind
of
summary
then,
and
so
there's
this
issue
of
how
do
we
prescribe
the
summary?
D
D
Yes,
this
interface
is
in
the
repo.
Of
course,
it
is
all
you
know
in
some
sense,
in
in
spirit,
you
know
a
draft
in
progress
right,
we're
working
on
a
proof
of
concept,
so
nothing
here
is
carved
in
stone.
It's
all
subject
to
commentary
and
revision,
but
since
it
is
not
in
a
PR,
perhaps
the
best
way
to
comment
is
to
the
mailing
list
or
to
Slack.
A
If
y'all
do
want
to
follow
up,
as
Mike
said
slack,
just
the
kcb
dev
Channel
and
the
kubernetes
slack,
as
well
as
their
mailing
list,
thanks
Mike
next
up
is
Lionel
with
a
demo
of
installing
k-native
and
kcp
and
a
teaser
For.
An
upcoming
API
lifecycle
feature
so
over
to
go.
H
Pattern
here
with
Adam
and
and
me
now
all
right,
so
let
me
show
the
give
you
a
little
bit
of
context
on
the
internet.
Show
this
one
okay.
So
since
last
year
I've
been
like
kind
of
working
on
exposing
the
creative
API
in
a
in
kcp
right,
and
so
we
explore
like
there
are
like
three
ways
of
doing
it.
One
is
you
have
like
a
connective
cluster
and
you
use
a
SIM
card
to
expose
the
connective
API.
So
that's
very
simple.
This
works
very
well.
H
Binding
solution
where
you
start
first
with
installing
the
connective
API
in
a
workspace
and
then
and
then
you
bind
to
akinative
Cluster
right.
So
when
you
do
The
Binding
placement,
you
place
it
to
a
connected
cluster.
This
is
it's
a
good
scenario
when,
like
you
want
to
reuse
the
connective
or
any
controllers
without
having
to
make
them
kcp
aware,
so
that
you
can
imagine
like
yeah
I
mean
you
understand
the
idea
right
and
then
the
last
part
is
so
it's
the
the
CL,
the
the.
H
Give
only
kcp
to
the
service
provider
and
the
service
provider
install
the
connected
inside
the
inside
the
kitchen,
so
I'm
going
to
demo.
Just
this
part
this
one
right.
This
is
the
hardest
part,
because
Kenneth
has
so
many
manipulates,
very
low
level.
C
H
Endpoints
right,
so
let
me
switch
to
are
we
stop
sharing
this
to.
H
In
Chrome
yeah
window,
maybe
okay-
that
sounds
good.
It
should
be
this.
You
should
see
this
code
now
right.
H
Yes,
all
right
is
that,
like
big
enough
yeah,
it
looks
good.
Okay,
thanks,
Mario,
okay,
so
I
have
this
guide.
So
that's
so
I'm
going
to
show
how
we
install
connective
right
in
kcp.
For
that
you
need
a
special
Branch
that
supports
up.
E
H
Already
started
kcp
enabling
the
kcp
synchronal
feature.
This
is
because
we
need
to
have
part
being
upsyncing
to
to
kcp
right,
so
this
is
like
running
on
top,
then
in
the
middle
it
would
be
my
kcp
terminal,
what
I
call
it,
and
so
the
first
thing
is
akinative
service
provider.
The
thing
you
can
do
is
to
create
workspace.
H
H
Up
like
a
d
cluster,
so
I
have
on
the
bottom
terminal.
I
have
like
a
can
cluster
drawing
and
I
checked
out
the
the
branch
I
I
pushed
the
the
image
of
this
cluster,
and
so.
H
I
would
create
a
sync
Target
configuration
so
in
here.
I
need
a
couple
of
resources
to
be
synced
to
to
the
physical
cluster
like
for
Destruction
budget
policy,
Auto
scaling
and
pointing
Parts,
because
all
this
is
things
that
connective,
creates
and
I
also
enabled
the
kcp
singers
and
feature
Like,
This
Server
right
so
now,
I
can
create
so
apply
this
in
Target,
so
register
the
the
SIM
card
get
in
KTP
and
if
I
look
at
the
status
of
my
sync
Target
is
true.
So
it's
good
right.
H
H
So
the
first
thing
I'm
going
to
do
is
to
install
this
crd
and
that's
inserting
the
ncrd
is
in
my
workspace
in
the
connective
plus
page.
You
can
take
a
look
at
it
and
you
see.
H
I
C
H
Interesting
for
us
is
actually
the
the
last
one,
the
service,
that's
the
main
one.
H
H
Config
map
Services
bug
description,
a
lot
of
things
right.
The
only
thing
that
doesn't
install
here
is
the
the
the
horizontal
postcard
I,
don't
know
yet
why?
But
you
know,
that's
something.
I
need
to
investigate
at
some
point
all
right.
So
now
going
back
to.
C
H
H
Endpoint
synchronization
of
endpoint,
so
what
they
did
is,
if
you
add
an
annotation
on
on
a
service,
and
this
annotation
is
called
epsync
derived
resource
and-
and
you
give
the
name
of
the
resources
that
you
want
to
absync,
then
the
derived
resources
are
going
to
be
thinking
to
the
to
the
kcp
workspace
right.
So
in
this
case,
Kinesis
service
installed
the
service
that
is
called
activator
service.
And
can
it
one
of
the
connective
controller
checks
that
the
endpoint
of
these
Services
ready
is
there
to
to.
H
That's
my
in
space,
where
I
installed,
connective
I
have
the
the
activator
and
I
have
the
activator.
F
H
Yeah,
this
is
again,
this
is
all
available.
H
Two
zeros
I,
don't
know
I
mean
this
is
I,
think
it's
a
problem
with
I.
Have
it
at
the
end
yeah
yeah,
it's
a
replica.
It's
set
by
default
to
zero
I.
Believe.
E
H
Can
do
quickly
delete
the
together
service
and
I'm
going
to
reinstall.
H
It
doesn't
rain
on
Monday,
okay,
well,
okay,
let's
see
for
the
next
one.
So
let's
continue
and
let's
see
if
it's
working
for
the
the
second
one,
because
we
have
the
same
issue
for
the
for
the
networking
layer.
So
can
you
keep
you
have
like
different
plugins
for
the
network,
so
I'm
going
to
install
it.
H
H
F
C
H
So
we
have
a
bunch
of
admission
controllers.
They
are
all
service
based
admission
controllers,
I
didn't
change
this
and
kcp
does
not
support
that.
So
I
need
to
be
this
immersion
controllers.
H
Right
and
I'm
going
to
tell
cunitive
that
using
Corey
as
my
Ingress
oh
I,
know
right
now:
okay,
that's
something
different
and
I
can
verify
that
probably
is
working.
H
H
Besides
this
small
problem
and
so
I'm
ready
now
to
deploy
the
first
community
service,
so
this
is
like
a
very
minimal
connective.
D
H
D
H
Service
is
this
annotation
because
I
disabled,
the
mutation
actually
defaulting
web
hook
and
a
meeting
web
whatever
and
I
also
need
to
tell
you
know
kcp
to
upsync
the
the
end
points
right.
That's
done
this
way,
and
so,
if
I
do
this.
H
Okay,
at
some
point,
this
will
become
ready
right,
but
it's
not
going
to
work
now
because
the
because
of
the
the
issue
I
had
before
so
equations.
A
Maybe
you
want
to
take
a
look
while
we
move
on
to
some
other
topics
and
if
you
can
figure
out
what's
going
on,
we
can
Circle
back
and
show
the
rest
of
it.
Yeah
sure
that
works.
E
E
Ahead,
maybe
just
to
comment
about
you
might
wonder
about
you
know
this
requirement
to
Adam
an
annotation
to
I.
Think
the
endpoints.
The
the
point
of
this
is
mainly
that
we
don't
want
to
by
default.
Absync
derived
objects
like
endpoints
in
any
case,
because
that
would
really,
you
know,
add
many
unnecessary
objects
at
the
kcp
side.
On
the
other
hand,
finally,
we
would
not
have
to
add
those
annotations
manually,
because
you
know
in
in
with
the
whole
picture.
We
could
do
that
with
the
coordination
controller.
E
The
whole
picture
I
just
wanted
to
to
to
to
to
to
provide
it
as
well
is
mainly
that
you
would
have
an
API
export
having
the
the
corresponding
cids
of
K
native,
you
know,
but
as
an
API
export,
and
you
obviously
would
have
when
you
bind
to
the
S
this
API
export,
you
would
also
bind
that
is
you
know,
joint
to
to
a
coordination
controller
that
would
obviously
look
at
the
corresponding
services
and
add
this
annotation
automatically.
E
So
the
whole
point
of
having
API
exports
with
permission
claims,
coupled
with
coordination
controllers,
is
that
you
can
have
you
know
a
complete
behavior
that
gathers
both
apis
and
possibly
add
some
some
specific
behavior
on
on
those
apis
like
adding
this,
this
directive
in
The
annotation
and
provide
an
overall.
You
know
consistent
experience
for
for
Kennedy,
for
example,
so
I
mean
we
have
to
keep
in
mind
that
we
would
not
have
to
add
this
annotation
by
hand.
Finally,.
I
E
No,
in
fact,
The
annotation
is
I
mean
at
least
in
the
in
the
pull
request.
It's
not
merged
for
now,
but
The
annotation
is
is
quite
generic
because
it's
part
of
sort
of
part
of
the
API
internal,
but
as
for
knowing
what
is
a
derived
object,
there
is
no.
For
now
you
know
generic
mechanism.
There
is
a
specific
here
because
it's
you
know,
endpoints
are
standard,
Cube
objects.
E
E
I
Right,
so
this
is
right
now
it's
specific
to
the
particular
use
case.
It's
not
something
that
can
be
generalized
yeah.
E
I,
don't
think
it
can
be
generalized
I
mean
completely
based
on
owner
apps
I
mean
it's
it's
more
complicated
than
that
and
usually
tied
to.
You
know
specific
use
cases
of
the
of
the
user,
but
but
obviously
there
there
is
some
follow-up
to
do
in
order
to
allow
you
know
up
thinking
for
other
type
of
objects
and,
although
obtain
into
upsyncing
other
type
of
objects,
and
then
this
would
be
the
the
responsibility
of
the
third
party
to
provide
the
the
right
agent
on
the
physical
cluster.
E
That
would,
you
know,
flag
the
the
other
objects
instances
to
be
absinct,
so
we
might,
in
the
future,
remove
the
the
limitation
of
having
of
how
hard
coding
the
the
type
of
objects
that
can
be
absinct.
But
what
I
think
is
that,
as
for
implementing
the
logic
of
what
are
the
instances
that
will
be
absinct,
this
will
in
any
case,
be.
You
know
something
added
on
the
physical
cluster,
possibly.
I
Yeah,
it
does
I
still
think
in
that
use
case.
We
discuss
with
a
cross-plane,
creating
secrets
and
be
able
to
upsync
them
back.
E
Yes,
I
I
think
that
there
are
many
use
cases
that
you
know
have
a
really
dedicated
logic
and
that
it's
quite
hard
to
you
know
and
possibly
impossible
to
implement
generally.
But
what
we
have
to
provide
is
enable
the
enablers
to
you
know,
obtain
add
additional
resource
types
and
possibly
rules
for
for
marking,
instances
for
our
thinking
and
and
based
on
this.
You
know
Machinery
available
Machinery.
Then
then
you.
H
No,
no
justice,
just
a
teaser,
so
I
have
a
demo
but
I'm
not
ready
for
today.
No.
A
Worries
thanks.
Well,
let
me
re-share
my
screen
real
quick.
A
So
I
have
a
small
update
on
documentation,
so
I've
updated
the
configuration
for
the
docs
so
that
we're
using
a
much
easier
internationalization,
Library
you'll
notice
that
what
used
to
be
where
my
cursor
is
next
to
the
search
bar
where
you
could
pick
languages
is
gone.
That's
because
we
don't
have
any
translations
so
as
soon
as
we
have
at
least
one
one
file
in
another
language
that
will
show
up
here
and
if
anybody
is
interested
in
trying
to
do
any
translations.
A
We'd
love
to
have
those
contributions
and
not
too
much
else
has
changed.
Although
one
other
thing
that
I
did
to
mirror.
What
we
had
in
Hugo
over
to
make
docs
is
I
added
a
little
bit
of
code
that
will
auto-generate
this
summary
page
for
the
section,
and
it
takes
the
description
from
each
of
the
individual
markdown
files
and
renders
it
below
which
is
kind
of
nice.
A
And
the
last
point
I'll
make
is
that
if
you
are
adding
a
new
file
anywhere
in
the
docs
tree,
the
thing
that
you'll
want
to
keep
in
mind
is
that
the
navigation
bar
over
on
the
left
is
sorted
based
on
file
name,
which
was
a
surprise
to
me.
I
thought
it
would
do
it
based
on
the
the
title.
So
what
that
means
is
that
you
generally
want
to
try
and
make
sure
that
when
you
are
creating
a
new
file,
if
you
go
into
docs
and
then
you
go.
A
And
then,
for
example,
Concepts
you'll
want
to
try
and
make
sure
that
the
file
name
roughly
matches
whatever
the
first
section
heading
in.
So
if
we
look
at
registering
kubernetes
clusters
using
syncer
you'll
see
that
the
this
Title
Here,
the
single
pound
sign
or
the
H1.
This
is
what
gets
rendered
on
on
the
left
nav.
So
you
just
want
to
make
sure
that
the
file
name
is
close
to
whatever's
in
here,
so
so
that
it
renders
roughly
alphabetically
and
that's
all
I
have
for
docs.
A
If
anybody
has
any
questions
or
wants
to
know
more,
please
feel
free
to
reach
out
offline
and
next
up
Andy
with
a
good
first
issue
for
kcp
Edge.
G
Yeah
and
our
good
first
issue:
Quest
we've
got
a
few
new
ones
in
there,
mostly
tied
around
documentation,
as
Andy
showed
the
k-speed.io
page
that
he's
got
using
doxy
I
was
able
to
do
something
very
similar
with
kcp
Edge
I
showed
that
last
time
we
were
on
the
call,
so
I
won't
go
through
that,
but
some
of
the
some
of
the
newer
items
we're
trying
to
connect
the
dots
for
our
quick
start
and,
let's
see
if
I,
can
show
you
here.
G
So
in
our
quick
start
now
we
have
a
blog
post
that
that
Paulo
put
together
with
the
help
of
others,
and
it's
out
there
now
we've
been
promoting
it
pretty
heavily
and
it
goes
through
the
steps
of
how
to
install
kcpe
and
make
it
you
make
it
useful
in
the
kcb
edge
use
case.
G
You
know
for
deploying
one
to
many
instead
of
one
to
any
and
so
we'll
be
taking
that
in
the
next
week
or
so,
and
configuring
it
into
something
that
looks
more
md-like
markdown
and
in
doing
so
it
mimics
a
lot
of
you
know.
This
is
exactly
what
the
kcp
quick
start
looks
like
at
this
point,
but
we
need
to
add
on
to
that,
of
course,
what
is
specific
to
kcp
Edge,
and
then
we
get
into
the
weeds
here.
So
some
of
the
the
areas
where
we're
experimenting
right
is
in
the
edge
scheduler.
G
So
if
somebody
wanted
to
come
in
and
take
a
look
at
what
we're
doing
we're
watching
our
analytics
page-
and
we
see
you
know
the
second
most
popular
item
here-
is
the
quick
start
guide.
You
know
no
surprise.
So
we
want
to
kind
of
get
people
to
link
what
we
do
in
the
in
the
quick
start
and
we've
already
got
a
ticket
open
for
that.
An
issue
open
for
that,
but
to
get
them
all
the
way
down
to
the
point
where
they
can
start
experimenting
with
the
edge
scheduler.
G
We
thought
it
might
be
a
good
idea,
or
a
good
first
step
is
to
create
some
kind
of
a
make
Target
that
would
install
the
items
that
were
necessary
and
the
components
and
to
get
you
up
and
running
so
just
wanted
to
leave
that
out
there
if
people
are
interested
in
tagging
along.
This
is
like
kind
of
a
low
hanging
fruit
type
of
thing,
we'd
love
to
have
your
contribution.
A
Yeah,
thank
you.
I,
don't
see
any
hands
going
up,
so
that
is
the
end
of
the
agenda
for
today
and
I'm
going
to
propose
that,
given
that
we
only
have
a
couple
minutes
left
until
the
official
end
of
the
meeting
that
we
skip
the
triage
for
today
and
if
there's
time
next
week,
we
can
resume
then
so
thanks
everybody
for
joining
and
we'll
see
you
next
time
have
a
great
rest
of
your
day.
Thank.