►
From YouTube: Kubernetes WG IoT Edge 20230222
Description
Frebruary 22, 2023 meeting of the CNCF IoT Edge Working Group. Discussion of edge related open source projects, recent edge books and articles, The KCP Edge project what it is, and recent milestones
A
B
A
A
Okay,
yeah,
okay,
leave
it
we'll
just
have
to
clip
off
the
junk
at
the
beginning,
yeah.
Unfortunately,
it
starts
recording
as
soon
as
the
first
person
arrives.
So
you
end
up
with
a
bunch
of
minutes
of
dead
time
at
the
beginning,
okay,
I
I,
don't
have
the
agenda,
but
when
I
looked
at
it
earlier
this
morning,
there
was
nothing
on
it
which,
in
our
tradition,
doesn't
mean
that
we
cancel
the
meeting,
but
we
just
open
it
up
for
free
form,
discussion
of
whatever
people
want
to
chat
about
or
came
across
recently.
That
was
interesting.
A
A
I
think.
At
this
point,
the
number
of
things
coming
in
per
week
has
slowed
down
for
a
while.
We
were
getting
a
lot
of
them
per
week
and
now
it's
a
trickle,
but
it's
time
to
classify
those
things
and
I
made
some
attempt
to
come
up
with
a
list
of
possible
categories
on
one
of
the
tabs
of
that
spreadsheet.
I
think
right
now
the
categories
are
too
big.
It's
like
20
I'd,
rather
see
it
down
to
about
10,
but
it
would
require
coming
up
with
better
categories,
to
combine
things
and
I.
A
Think
over
in
the
eclipse
and
Native
meeting
a
week
ago,
Robert
had
suggested-
and
he
gave
me
a
link
to
a
document
put
out
by
the
eclipse
foundation
for
Edge
that
classified
projects
not
on
one
axis,
but
on
two
kind
of
based
on.
You
know
what
it
runs
on
and
where
it
is,
and
maybe
where,
in
the
sense
of
you
know,
far
Edge
at
the
device
level
low,
combined
with
low
resource
to
running
in
mezzanine
and
public
cloud
and
I.
C
C
C
B
Yeah
yeah,
so
I'm
Dan
I'm
working
for
red
hit,
yeah
I'm,
one
of
the
founders
of
the
group,
so
we've
been
here
for
a
while:
I
worked
in
Eclipse
Society
space
for
for
quite
a
bit
working
on
a
redhead
sponsors,
drug
iot
projects
at
the
moment
and
yeah.
That's
my
whereabouts
write
to
me
is
drugs
or
go
next.
D
D
F
B
F
G
I'm
Frederick
with
the
eclipse
foundation,
so
I
managed
there
I
do
iot
and
Nash
Computing
programs,
so
I
had
the
pleasure
to
work
with
Diane
and
our
there
are
a
few
other
names
on
this
call.
I
recognize
anyway.
So
the
eclipse
Foundation
is
a
member
of
the
cncf,
a
member
of
lfedge,
and
so
we're
trying
to
just
well
cross-breed
our
open
source,
ecosystems
and
I'm
really
happy
to
be
here.
I
G
I
Next
so
Andy
Anderson
with
IBM
research
representing
kcp
Edge,
we
are
a
very
small
community,
we're
trying
to
get
a
little
bit
more
momentum
and
I've
been
attending
these
meetings
here
on
and
off
for
a
few
months
now,
so
just
trying
to
stay
in
touch
with
what
the
rest
of
the
community
is
doing,
especially
in
the
care
area.
Iot
Edge.
H
E
I
guess
I
might
as
well
speak
also
I'm
also
with
IBM
research
and
I've.
You
know
looked
into
this
group
a
few
times
before
and
I'm
working
also
on
problems
of
running
kubernetes
clusters
on
the
edge
mainly
focused
on
the
workload
layer
rather
than
the
infrastructure
layer
and
and
currently
pursuing
it
in
the
context
of
kcp
as
I'm
with
the
people
that
Andy
mentioned.
C
J
Foreign,
my
name
is
one
I'm,
a
program
manager
in
Azure
I'm,
currently
working
on
building
a
developer
solution
for
in
for
building
the
edge
applications.
I,
don't
have
any
specific
topic
to
discuss
today,
but
I
do
have
some
related
questions.
I
talk
with
Kate
offline,
but
I
will
repost
those
questions
in
the
bigger
Channel.
C
J
A
Okay,
I
guess
I'll
do
an
intro
now
I
finally
got
back
up
on
my
laptop
with
the
camera
functional,
so
I'm,
not
quite
a
founder
of
the
group
like
Diane,
but
I,
think
I've
gone
back
to
pretty
close
to
the
clowning
and
I
work
at
VMware.
As
a
software
engineer,
I'm
got
a
role
at
VMware
that
isn't
a
hundred
percent
agile
aligned,
it's
just
open
source
kubernetes
related.
A
However,
in
my
career,
I
have
worked
in
iot
Edge
industrial
control
for
decades
having
done
a
startup
in
the
field,
so
I
moved
from
there
to
more
corporate
I.T,
but
I
became
convinced
that
kubernetes
is
a
real
opportunity
to
redo
some
of
the
Legacy
implementations
that
are
in
popular
use
for
Edge
native,
particularly
in
industrial
control.
So
I
joined
this
group
and
have
been
frequent
participants
since
then.
B
A
Yeah
you
can
mention
the
title
and
I
did
bring
it
up,
but
maybe
people
missed
it.
My
capsule
summary
was
you
know
we
are
compiling
this
list
of
edge
native
open
source
software.
A
lot
of
them
are
managed
by
the
eclipse
Foundation.
The
book
covers
pretty
much
all
the
ones
that
are
deemed
current
and
excellent
coverage,
and
it's
very
fresh
because
this
thing
just
came
out
it.
A
What
was
it
February,
I
think
early
February,
so
often
the
the
sell
by
date
on
Tech,
Publications
and
books
in
rapidly
moving
Fields
makes
things
you
might
find
out
there
almost
dangerous
because
they
tell
you
things
that
become
wrong,
but
this
one
at
least
at
this
point
in
time,
is
very
good
and
it's
while
it's
still
fresh,
get
it
while
it's
fresh
and
if
there
were
faults,
I'm
sure
they'll
be
fixed
in
version
two,
but
by
Design.
If
you
even
look
at
the
title,
it
I
think
it
has
the
word
Eclipse
there.
A
So
some
of
the
projects
that
are
not
under
Eclipse,
like
they're
under
cncf
and
things
are
lightly
covered,
or
maybe
not
even
mentioned,
but
hey.
You
know
I
I,
think
if
you
tried
to
do
everything
now
that
we
have
this
list
underway,
you'd
appreciate
that
that
would
be
maybe
too
much
to
take
on
that
spreadsheet.
A
G
And
from
from
a
net
Computing
perspective,
I
I
should
say
that
the
edge
Computing
chapter
in
there
is
probably
one
of
the
most
less
eclipsey
one
in
the
sense
that
Eclipse
project
car
mentions,
but
there's
detailed
coverage
of
project
Eve.
We
mentioned
web
assembly
in
a
from
a
generic
perspective,
so
you
know
things
things.
There
are
a
bit
less
project
oriented.
A
D
B
C
A
Well,
this
is
the
birds
of
a
feather,
so
let's
just
throw
it
out
there
to
things
that
you
may
have
recently
discovered
that
you
were
found
interesting
and
wanted
to
chat
about
I.
Think
I
threw
one
out
recently
or
did
I
in
the
slack
channel
on
an
article
provocatively
entitled
big
data
is
dead
and
I
found
that
kind
of
a
re.
A
Think,
from
my
perspective,
this
article
kind
of
portrayed
it
as
maybe,
if
you
try
to
do
this
big
data
of
gather
everything,
you've
got
put
it
together
in
a
cloud-hosted
reservoir
that
maybe
you've
got
a
hoarding
problem,
because
there
are
issues
with
paying
for
all
of
this
storage.
Obviously,
you've
got
to
pay
for
any
analytics,
there's
privacy
rules
that
mean
that
your
cost
isn't
just
to
Move
It
from
where
it
came
from
and
put
it
in
this
pool,
but
potentially
because
people
have
a
right
to
be
forgotten
under
certain.
A
A
second
video
cameras
and
then
you
could
potentially
say
that
I'm
going
to
gather
everything,
we've
got
from
every
Edge
location,
move
it
up
and
stored
in
the
giant
database
in
the
cloud.
But
you
have
to
ask
yourself
whether
you
really
want
to
do
that
and
how
this
ties
into
Edge
is
that
if
you
start
looking
skeptically
at
the
idea
of
whether
you
really
want
to
pull
this
I
think
it
leads
to
a
scenario
where
you
host
more
intelligence
and
apps
out
at
the
edge
to
filter
this
clean.
A
A
H
E
E
It
was
incomplete,
I'm
trying
to
begin
I
just
want
to
ask
Escalon
for
excellent
for
clarification.
He
asked:
can
our
Edge
native
principles
be
applied
to
apps
running
on
medium
and
heavy
Edge
as
well?
I
was
not
sure
whether
he
met
I'm.
Sorry
I,
you
know,
haven't
been
paying
close
attention
here
by
by
just
medium
and
heavy
edge
mean
relatively
high
capacity
nodes
at
the
edge,
or
is
he
referring
to
intermediate
vertices
in
some
hierarchy?.
J
Yeah,
what
I
mean
by
I
can't
give
you
an
example,
for
instance
HCI
on
from
Azure.
We
consider
it
as
a
heavy
Edge
solution.
So
that's
basically
that's
basically
from
our
lessons
from
customers,
some
of
our
customers.
They
have
like
a
chain
stores
or
like
running
the
chain,
restaurants,
for
each
in
each
of
their
store
or
restaurant.
They
will
have
a
better
mixed
group
of
infrastructure.
J
They
will
use
the
iot
devices
like
sensors
or
on
cameras
to
crack
the
data,
but
due
to
the
data
privacy
concern
or
some
latency
concern,
they
were
also
running
some
heavy
Edge
or
median
Edge
infrastructure
inside
the
store
to
processes.
The
data
collected
from
the
sensors,
but
so
my
question
is
because
we
have
this
white
papers
to
guide
the
users,
the
developers
how
to
write
the
what's
the
best
practice
for
writing
the
edge
applications,
I'm
wondering
for
those
applications
which
are
not
specifically
running
on
the
light
edge
devices
like
iot
devices.
J
A
Yeah
I
think
a
common.
If,
if
I
saw
the
words
light
edge
heavy
it
to
me,
it
would
imply
the
amount
of
compute
resource
and
often
what
goes
along
with
that
is
restrictions
on
the
network
Resource
as
well.
Although
those
are
two
orthogonal
issues,
you
know
it
is
possible
to
have
a
very
heavyweight
compute
at
an
edge
location.
A
You
know
even
something
like
rackmount
servers
and
still
be
challenged
with
regard
to
your
internet
access
capability
or
network
connections,
maybe
just
because
it's
in
a
really
rural
location
or
even
in
a
a
mobile
vehicle,
or
something
like
that.
So
I
think
it's
careful.
It's
important
to
keep
those
things
separate.
The
other
observation
I've
had
being
in
this
group
for
five
plus
years
now
is
that
what
constitutes
being
heavy
versus
light
is
not
a
constant.
You
know.
Compute
has
really
I
think.
A
Maybe
the
old
thing
of
technically
the
Moore's
Law
of
more
transistors
per
device
is
dead
but
still
device.
Even
low
power
devices
have
gotten
far
more
capable
today
versus
five
years
ago,
and
this
applies
not
just
to
traditional
compute,
but
to
that
there
are
certain
classes
of
I'd,
almost
call
them
Edge
native
machine
learning
acceleration
devices
so
that
what
you
have
to
be
very
careful
of
Articles
written
five
years
ago
on
the
best
architecture
for
doing
things,
because
things
have
really
changed
five
years
ago,
something
like
Nvidia
or
sensor.
A
Chip
was
something
you'd
only
be
able
to
run
in
a
large
public
Cloud.
You
didn't
have
the
power
or
dollar
economic
budget
to
put
them
at
Ed
at
Edge,
and
you
prop
for
those
particular
device
five-year-old
devices
you
still
don't,
but
there's
new
ones
out
there
that
are
becoming
pretty
fascinating,
I'll.
Look
it
up
and
post.
A
It
drop
the
link
in
the
chat,
but
as
part
of
that
effort
of
coming
up
with
the
edge
native
software
spreadsheet
list,
I
actually
came
across
a
very
interesting
open
source
project
for
doing
machine
learning
on
camera
Feeds
out
at
Edge
to
the
point
where
people
contend,
that
this
is
runnable
on
Raspberry
Pi's,
but
doing
full
full
ml
based
identification
of
objects
and
I'm.
Reading
this
going.
A
E
General
point
is
true:
right.
I
want
to
make
two
points
here.
Power
increases
over
time
generally
and
as
X1
was
saying,
depending
on
the
scenario
you
may
have,
you
know
very
different.
Unless
power
available
right
in
a
retail
sort
of
setting,
you
may
well
run
it
have
a
small
cluster
of
machines.
You
may
have
a
rack
in
each
store
or
location
whatever
that
that's
perfectly
plausible
for
running
applications
at
the
edge.
A
Yeah,
so
the
project
I
was
talking
about,
is
called
frigate
and
what
it
does
to
pull.
This
off
is
I,
wasn't
even
aware
of
this
device
either
I
just
recently
ordered
one
and
the
backlog
is
months
on
these
things,
but
I'm
expecting
to
get
mine
in
about
a
month
so
device
Google
made
called
Coral.
That
is
not
powerful
enough
to
train
a
model,
but
it's
specifically
been
optimized
to
run
one
and
they
sell
it
in
a
USB
key
form
factor
or
in
these
mini
PCI
Express
cards
and
they're
low
power.
G
B
But
I
would
I
would
add
to
to
the
questions
so
I
I
think
the
principles
are
basically
a
good
applied
wealth
to
the
medium
heavy
and
heavy
Edge
right,
it's
their
sketchable,
whether
you
can
apply
them
to
the
light
edge,
but
but
this
is
where
they
would
be
applied
right.
So
just
to
answer
the
question.
C
F
C
Everything
called
but
I
think
when
you're
writing
it
we
said
Tiny
Edge
is
where
we're
not
really
talking
about,
because
we're
talking
about
the
compute,
that's
interacting
with
those
devices
if
we
Define
tiny
Edge
as
sensors
MCU
class
devices,
but
I
agree
with
what
Dahan
said.
I
think
it
can
be
heavy
Edge
I
think
you
have
more
freedom
with
the
more
compute
that
you
have.
So
obviously
you
have
to
be
less
resource
aware.
B
And
it
may
be
the
good
idea
for
for
some
future
revision
of
this
would
be
to
to
maybe
categorize
the
principles
based
on
the
heavens
on
the
edge.
So
so,
what's
most
important,
more
important
on
the
on
the
heavy
side,
what's
more
important
when
you,
when
you're
going
to
the
medium
and
the
night
edges
or
something
like
that,.
J
Yeah
I
would
say
based
on
our
customer
conversations.
Yes,
the
heavy
Edge
does
provide
more
computer
resource,
but
for
the
network
for
the
networking
issue,
almost
I
would
say.
Almost
90
of
our
customers
have
the
networking
issues
because
they
have
thousands
of
stores
running
in
the
different
locations,
and
sometimes
they
will
have
some
like
a
weather,
very
bad
weather
conditions
or
I.
Don't
know
some
other
issues
make
them
accessible
to
the
networks,
so
they
are
looking
for
and
such
a
solutions
to
help
them
to
solve
the
networking
issues.
C
J
I
think
they
probably
are
looking
for
like
the
end-to-end
solution
like
yeah.
How
do
they
recover
immediately
from
the
downtime
issues
or
maybe
I'm
just
making
up?
Maybe
when
they
designing
the
applications,
should
they
consider
how
to
catch
their
datas,
the
only
so
what
they
want
is
when
this
networking
failures
happens,
this
deal,
can't
the
each
store
or
in
each
location
can
still
operate
normally.
J
E
C
E
Well,
I
would
say
first
off
one
of
the
questions,
I
think
about
platform
and
applications.
So
there's
a
division
of
responsibilities,
question
so
I'm
trying
to
work
on
platforms
that,
to
the
degree
possible
support
applications
through
interfaces
that
the
interface
does
not
demand
online
connectivity.
The
interface
is
state-based,
and
so
the
implementation
can
either
be
online
or
not,
and
the
application
doesn't
need
to
know,
but
it
in
general
I
suppose
there
are
situations
where
the
application
will
need
to
know.
E
E
So
there's
some
different
issues:
right,
pull
versus
push
is
different
from.
Can
you
expect
to
pull
at
any
time?
Can
you
expect
to
pull
at
full
rate
at
any
time
right,
so
I
I
think
there
are
two
different
issues
that
I
think
the
pull
versus
push
is
more
a
matter
of
you
know
stuff
like
typical
Arrangements
of
firewalls,
who
who
can
succeed
to
open
a
TCP
connection,
and
yes,
it's
often
arranged
such
that
it's
easier
for
the
edge
to
open
a
TCP
connection
to
the
sender
than
vice
versa.
C
I
think
you
can
get
into
a
lot
of
details
with
what
does
the
word
pull
versus
push
mean
for
people,
but
and
what
I
was
trying
to
say
there
with
that
terminology
is
I,
think
having
the
edge
fetch
information
from
the
cloud
is
a
better
model
than
having
the
cloud
have
a
cron
fetch
to
the
edge
where
the
cloud
never
knows.
If
the
edge
is
going
to
be
available
or
not,
but
I
know,
pull
and
push
is
a
like
a
kind
of
a
overloaded
term.
So
there's
also
so
many
new
nuances.
B
I
We've
got
a
Blog
set
and
a
coding
Milestone,
that's
out
there
now
and
I
just
want
to
I'm.
Just
sharing
that
with
you
now
we're
working
on
a
set
of
a
set
of
initiatives
and
elements
for
a
proof
of
concept
that
will
be
showing
off
at
the
end
of
March
and
I
thought.
It
would
be
useful
for
you
to
see
that
information,
as
well
as
we're
starting
to
build
a
medium
blog
post,
Depot,
so
to
speak
for
curated
information
about
kcp,
Edge
and
kcp,
which
I
just
dropped
in
there
as
well.
E
I
We're
tracking
use
cases
in
Telco
agriculture,
space
era.
You
know
and
aerodontics
with
the
we're
working
with
the
European
Space
Agency
we've
started
talking
with
Chick-fil-A,
so
in
the
fast
food
area.
We've
also
done
work
there
too.
So
sure
I
can
recap
that
I
don't
have
the
ability
to
share
right
now.
But
if
you
would
allow
me
to
I
can
show
you
my
screen
as
to
what
I'm,
looking
on
and
Mike
feel
free
to
chime.
In
as
you
feel,
necessary,.
A
I
E
E
D
E
I
E
So,
as
I
said,
we're
looking
at
specifically
the
issues
of
making
a
platform
that
can
help
with
people
organizations
doing
age
Computing
where
they
want
to
run
applications
on
kubernetes
clusters
at
the
edge,
and
so
the
problems
that
that
you
know
that
arise
are
first,
was
we've
been
alluding
to
so
I
I?
Take
it
as
a
given
that
these
applications
are
going
to
run
on
a
coup
cluster.
E
Now
that
can
be
a
single
machine
or
it
can
be
a
you
know,
several
machines,
depending
on
the
actual
scenario
at
hand
right.
There
are
coup
distributions
that
are
engineered
to
run
on
relatively
low
resource
machines,
but
it
doesn't
have
to
be
that
white
now,
Chick-fil-A,
as
you
mentioned,
for
example,
has
the
cluster
of
three
physical
machines
in
each
restaurant.
E
Another
facet
of
the
problem
is
clusterscoped
API
objects,
so,
for
example,
in
the
TMC,
which
is
transparent,
multi-cluster
project
in
kcp
they've
defined
a
different
kind
of
multi-cluster
problem.
They
call
transparent,
multi-cluster
and
in
transparent
multi-cluster.
A
workload
is
something
that
appears
in
one
kubernetes
namespace,
but
we
believe
in
general
workloads
are
not
so
confined.
We
need
to
be
able
to
handle
clusterscoped
API
objects
as
well.
E
Also,
as
I
mentioned
earlier,
there's
a
need
to
support
a
general
hierarchy
right,
as
was
touched
on
earlier.
You
can't
expect
to
transfer
all
the
data
back
to
the
center.
You
don't
always
want
to
it's,
not
always
feasible.
You
have
to
do
some
processing,
it
may
not.
You
know,
and
it
may
not
be
as
simple
as
Center
and
Edge.
You
may
have
intermediate
levels
of
hierarchy.
E
E
Also,
we
touched
on
the
need
for
each
Edge
location
to
be
self-sufficient
and
by
location.
I
really
mean
that
boundary,
this
sort
of
the
lowest
useful
boundary
for
management.
Here
in
the
case,
so
it
may
be
a
restaurant
with
a
cluster
of
three
machines.
It
may
be
what
only
in
one
machine,
whatever
it's
the
lowest
layer
of
the
hierarchy
where
it
it.
You
have
a
that,
it's
a
real
boundary
in
terms
mainly
of
communication.
E
You
know
you
may
have
regulatory
or
data
sovereignty
issues
as
well
as
communication
issues,
but
you
you
want
to
have
each
Edge
location
self-sufficient
and
again
this
is
a
distinction
from
TMC.
Although
again
I
don't
know
how
many
of
you
people
are
familiar
with
TMC
another
one.
Is
that
there's
a
complex
arrangement
of
roles
and
responsibilities
right?
If
you
look
at
a
lot
of
the
kubernetes
world,
it's
focused
on
the
devops
Paradigm
or
a
development
plus
SRE
division,
but
it's
in
Edge.
E
E
E
There's
a
one-to-many
relationship.
You
can,
unlike
you
over
near
ordinary
kubernetes,
right
between
workload,
description
and
running
copies.
We
want
many
running
copies,
given
one
workload
description,
and
this
has
lots
of
implications
which
I'm
going
to
try
to
summarize
it.
It
does
call
it
a
lot
of
implications
and
then
the
other
is
another.
One
is,
is
again
a
large
one,
not
again
large
number
of
edge
clusters.
E
So
one
of
the
things
you
need,
when
you
have
multiple
copies,
is
you
generally?
You
need
to
be
able
to
customize
the
workload
for
each
destination,
but
you
wouldn't
want
to
maintain
a
customized
with
k,
a
prescription
for
each
location,
because
that's
that's
just
infusably
tedious.
You
need
pattern-based
descriptions
of
how
to
customize
and
that's
just
one
example.
A
E
A
F
E
E
What
they've
done?
One
of
the
things
they've
done
is
they've
introduced
a
higher
level
of
virtualization
in
the
API
server,
so
above
namespaces
they
have
something
you
might
call
Super
namespaces.
They
call
them
logical
clusters,
but
they're,
not
full
clusters,
they're,
really
just
an
extra
level
of
division
of
the
objects
within
the
API
server
and
in
with
the
corresponding
in
the
storage,
but
then
with
the
TMC.
E
E
No,
it's
not
isolated,
it's
not
a
complete
isolation
and
in
fact
this
is
one
of
the
issues
we'd
like
to
get
Upstream
into
regular
kubernetes,
this
additional
level
of
virtualization,
but
if
we
sell
it
as
multi-tenancy
or
complete
isolation,
that's
just
not
going
to
go
because
it's
not
true
but
I.
Think
for
this
use
case
and
others.
The
idea
of
an
extra
level
of
virtualization
is
useful
and
I
I
would
like
to
see
that
make
it
into
plain
kubernetes.
E
Right
indeed-
and
there
is
in
part,
because
in
kubernetes
there's
things
that
are
not,
there
are
objects
that
are
not
namespace
scope,
they're
cluster
scoped,
so
this
extra
level
of
virtualization
solves
that
problem.
So
with
in
with
the
kcp
logical
clusters,
each
logical
cluster
has
its
own
set
of
crds,
for
example
its
own
set
of
API
resources,
okay,
but
it's
still
one
server,
so
you
can
still
have
you
know
performance
interactions
between
users
of
that
server,
and
so
you
know
it
would
be
a
mistake
to
try
to
sell
it
as
complete
isolation.
H
I
Yes,
actually
we're
on
the
kcp
dash
Dev
Channel
over
in
the
kubernetes
slack,
and
the
community
meeting
happens.
Our
next
community
meeting-
we're
bi-weekly,
will
be
on
the
on
tomorrow
morning.
So
if
you'd
like
to,
we
can
rope
you
in
there
there's
a
Google
Google
Calendar
connected
at
the
bottom
of
that
edge
MC.
Let
me
let
me
share
now.
I
guess
now
is
appropriate.
Let
me
see
if
I
can
get
my
Safari
there.
It
is
okay.
I
So
right
so
we've
got
a
a
docs,
kcp,
Edge,
dot,
IO
and
of
course,
then
there's
our
repo
and
at
the
bottom
of
the
for
the
readme
in
the
repo
you'll
see
there
is
a
community
calendar
in
Google
that
you
can
connect
to
and
get
our
contact
info.
If
that's
not
sufficient,
then
feel
free
to
slack
me
in
kcp
Dev,
and
here
we
go
kcp,
Dev
and
I'll
be
happy
to
respond
with.
You
know
a
link
to
an
invite
or
anything
else,
and
that's
where
we
hang
out.
A
Just
jump
in
if
you
do
in
the
meantime,
a
couple
conference
reminders,
the
kubernetes
on
the
edge
days
submits,
came
in
very
strong.
The
program
committee
is
still
going
over
those
to
come
up
with
a
schedule,
but
it
looks
like
that's
going
to
be
a
a
really
nice
conference
going
on
in
Europe
in
April.