►
From YouTube: Kubernetes WG IoT Edge 20181221
Description
December 21 2018 meeting of the Kubernetes IoT Edge Working Group - discussion of future meeting times and Open Glossary Project
B
B
A
B
B
B
C
B
C
D
A
E
A
D
Hey
this
is
dwayne
bradley
from
duke
energy
dejean.
I've
actually
talked
to
you
after
the
deep
dive
session
there
at
kubernetes
or
at
kubecon
the
other
week.
So
I'm
just
trying
to
this
was
first
I'd
heard
of
it
the
whole
working
group
for
the
edge
and
it's
something
that
we've
been
definitely
looking
at
at
duke
energy.
For
you
know,
pushing
kubernetes
out
to
the
edge
of
the
electric
grid
to
have
applications
run
along
the
edge
of
our
our
feeders,
and
so
I'm
definitely
interested
in.
B
G
So
recently
I
heard
about
this
from
the
kubecon
conferences
that
near
this
new
working
group,
which
has
been
basically
monitoring
on
on
developing
the
framework
for
pushing
the
kubernetes
at
the
edge
and
I'm
interested
in
looking
into
this
at
a
scale
how
this
could
be
deployed
and
what
how
this
framework
comes
up
and
how
we
can
leverage
that
that's
my
interest
and
I'm
interested
in
yeah
con.
You
know
I'm
interested
in
contributing
for
this
group
and
then,
whatever
the
documents
come
out,
I
can
review
that
and
provide
my
feedback.
A
H
I
guess
I
could
introduce
myself.
This
is
david
lyle.
I
worked
for
intel
and
attended
the
sessions
at
kubecon,
but
we
have
a
pretty
broad
set
of
interests
from
the
iot
space
to
more
of
a
traditional
edge
space
as
well
so
interested
in
participating
in
this
group
run
on
all
those
levels,
essentially.
A
B
A
Yeah,
so
just
for
the
it
keep
going
cindy
asked
if
he
could
move
this
meeting
for
one
hour
later,
basically
to
like
9
a.m:
pacific
time,
which
is
fine
for
me,
but
basically
that
means
pushing
to
the
6
p.m,
or
you
know
even
later
for
friday
evening
for
for
for
other
people
in
europe
and
more
to
the
east.
So
so
then
we
started
discussing.
Should
we
move
it
to
some
other
day
or
something
else?
I
don't
have
a
definite
answer
now,
so
I
started
a
little.
A
You
know,
doodle
poll
just
to
see
where
people
are
with
you
know
wednesday,
thursday,
friday
this
hour
and
one
one
hour
later,
but
there
was
some
questions
from
china
as
well
that
that
these
meetings
time
are
not
perfect
for
for
people
in
china,
and
preferably
also
in
india
right,
so
anybody
having
any
thoughts
preferences
about
it.
So
it's
not
not
something
we
should
decide
today,
especially,
is
because
it's
it's
holiday
and
and
a
lot
of
people
are
not
here,
but
I'm
just
saying.
B
A
I
B
The
other
thing
I'd
suggest
is,
I
personally
would
like
to
avoid
thursdays,
because
it's
already
a
congested
day
for
a
whole
tier
of
you
know.
The
kubernetes
project
has
lower
level
working
groups
and
sigs
that
fold
up
into
the
community
sig
in
the
architecture.
Sig
and
many
of
those
are
on
thursday
morning
and
I
like
to
go
to
them,
and
you
know
it-
you
pretty
much
can't
get
a
slot
thursday
morning
that
doesn't
conflict
with
some
of
those
top-tier
kubernetes
sigs.
B
A
B
Yeah
I
see
bill
left
to
come
in
in
the
chat,
saying,
there's
no
good
time
for
everyone
and
we
should
alternate-
and
that
sounds
reasonable
to
me
whether
we
alternate
every
meeting
every
other
meeting
or
quarterly.
I'm
not
so
sure.
It's
tough
to
remember,
if
you
step
away
which
which
one
is
active
for
the
next
slot,
if
you
do
it
every
time,
but.
F
B
A
Yeah
yeah
I'll
I'll
pass
this
as
a
reply
to
the
mailing
list.
Just
as
one
of
the
ideas
that
you
know,
we
won't
left
any
anybody
hanging
so
we'll
you
know,
wait
a
little
bit
after
the
holidays
to
to
you
know,
see
what
our
preference
is
for
now,
but
into
the
future
that
we
plan
to
to
you
know
alternate.
B
B
C
That
there's
three
of
us
now
on
the
you
know,
sharing
by
video.
So
if
you
are
able
and
comfortable
sharing
by
video,
I
would
suggest
you
do
that.
I
think
it
makes
the
meetings
a
lot
more
personal
and
somebody
just
turned
on
their
video.
How
awesome
yeah
don't
feel
obligated
to.
I
know
some
people
aren't
comfortable
with
it,
but
I
like
it
a
lot
and
I
think
it
helps
get
to
meet
people
that
you
don't
actually
get
to
meet
in
person
very
often,
since.
F
B
Well,
I'll,
try
and
I'll,
let
maybe
some
of
the
other
people
speak
too,
because
it
might
you
know,
I'm
not
claiming
that
I'm
I'm
authoritative,
but
it's
addressing
the
subject
of
utilizing
kubernetes
at
edge
or
iot
locations
where
you
might
face
issues
like
a
network
that
isn't
constantly
connected
heavy
resource
constraints,
unattended
operation,
where
you
don't
have
it
staff
to
maintain
it
and
a
number
of
other
issues
there.
So.
I
B
Anybody
else
want
to
contribute
to
the
thoughts
on
what
this
group
is
about
and
if
you
watch
the
recording
from
kubecon
the
intro
to
this
group,
we
opened
the
presentation
with
kind
of
about
what
this
group
is
about.
Okay
and
the
link
to
that
recording
in
the
deck
is
in
the
meeting
notes,
I
see
that.
I
So
one
thing
I'll
add
that
I
think
is
one
of
the
trickier
areas
to
to
kind
of
define.
This
is
the
other
end
of
the
spectrum,
in
other
words,
how
to
differentiate
from
hybrid
environments.
So
how
much?
How
much
edge
is
too
big
to
still
be
considered
edge?
I
think
that's
still
a
you
know:
evolving
evolving
threshold.
A
And
just
to
round
all
this
up,
I
think,
like
we
defined
couple
of
actually
goals
for
the
group
and
that
that
is
to
like
try
to
educate
the
the
community
in
person.
Try
try
to
get
you
know
best
practices
known
so
far.
That's
why
having
these
kind
of
demos
and
and
on
the
topic
of
the
demos.
So
if
you
go
to
the
agenda
doc,
you
can
see
for
the
last
couple
of
of
of
meetings.
A
We
have
different
kind
of
demos
from
from
and,
and
you
know,
from
different
kind
of
companies
and
and
the
groups
here,
which
were
you,
know,
very
well
valuable
in
in
terms
of
giving
giving
us
the
the
use
cases
and
and
the
problems
and
the
challenges
and
how
they
solve
it.
So
that's
one
of
one
thing.
The
other
thing
would
be
to
try
to
to
you
know
document
all
these
best
practices
to
try
to
find
the
the
shortcomings
comings
in
the
in
the
kubernetes
project
and
maybe
try
to
resolve
those
within
the
proper
six.
A
B
A
Okay
yeah
another
thing
I
I
wanted
to
briefly
discuss,
maybe
today
and
and
we
can
continue,
but
I
I
want
to
just
I
wanted
to
talk
about
this
even
at
coupon,
but
it
was
too
busy.
So
we
we
never
found
time,
and
that
is
maybe
over
the
holidays.
Everybody
should
think
about.
You
know
what
are
some
particular
goals
we
want
to
achieve
in
in
2019,
so
you
know
what
what
should
we
focus
on
and
you
know,
for
example,
you
know
how
we're
going
to
proceed
with
the
white
paper.
A
C
C
I
would
really
like
to
see-
and
I
think
there's
a
lot
of
others
that,
like
to
see
sort
of
reference
designs
or
at
least
architectural
patterns
for
using
kubernetes
at
the
edge,
you
know
to
cover
the
the
distinct
use
cases
entirely.
You
know
on
the
device
edge
running
on
a
device
on
the
device
edge
running
on
a
rack.
That's
near
the
device.
A
combination
of
you
know,
infrastructure,
edge,
plus,
plus
device
edge.
C
Those
patterns
and
putting
some
thought
into
how
kubernetes
will
work
where
the
gaps
are,
where
technology
needs
to
be
built,
where
things
need
to
be
proven
out.
I
think
that
would
be
just
incredibly
valuable
for
not
only
the
kubernetes
community
but
the
wider
community.
That's
thinking
about
how
to
develop
apps
for
edge
in
general.
I'd.
Second,
that.
B
You
appear
to
be
muted,
sorry,
I
was
muted,
so
I
added
that
to
the
notes
and
I'm
wondering
what
the
best
way
to
get
started
on
that
is.
You
know
that
I'm
sort
of
thinking
that,
rather
than
just
put
out
a
blank
document
and
have
people
start
throwing
paragraphs
in
there
that
maybe
some
people
who
are
actively
working
on
this
could
give
presentations
on
ideas
for
reference
architectures
and
why
you
came
to
the
conclusion
that
these
patterns
are
a
good
idea.
A
But
I
also
think
that
you
know-
maybe
this
introductory
white
paper
is,
is
not
not
the
best
place
to
do
it.
So
you
know
it
should
have
a
limited
scope.
Just
to
you
know,
introduce
people
to
the
topic
and
then
also
you
know,
maybe
each
reference
like
architecture
deserves
its
own
kind
of
place
right,
so
it
not
not
so
far.
We
saw
that
you
know
they're
all
very
different
and
and
very
individual.
So
so
maybe
we
should,
you
know
tackle
them
one
by
one.
B
Yeah,
I
think
that
my
experience
just
chatting
with
random
people
at
those
sessions
at
kubecon
are
that
people
are
coming
to
this
group
with
anything
from
small.
But
you
know,
maybe
you
know
multiple
server,
kubernetes
installations
that
edge
to
tiny
things
based
on
microcontroller
boards
and
the
reference
architecture
for
those
two
things
might
be
quite
different.
B
B
Anyway,
I
don't
hear
any
objections
to
working
on
it.
The
only
issue
is
how
we
get
started
in
what
form,
ultimately,
it
is,
is
recorded
in
a
doc,
would
seem
good
as
an
end
goal,
but
maybe
to
get
started.
This
should
be
more
of
you
know
the
closest
we
can
come
to
a
whiteboard
discussion
over
zoom,
which
means
discussions
presentations.
That's
just
my
thoughts.
A
In
my
mind,
the
the
best
like
end
goal,
like
of
deliverable
for
each
would
be
like
some
kind
of
a
github
repo
with
something
that
could
be.
Actually
you
know
deployed
somewhere
and
and
demoed.
It
might
not
be.
You
know
possible
for
for
every
use
case,
but
you
know
where
possible,
it'd
be
good
to
hear.
A
B
C
Thing
sure
yeah,
so
one
of
the
things
that
I'm
looking
to
put
together
is
a
bunch
of
panelists
to
lead
a
panel
discussion
on
edge
computing
that
I'm
gonna
pitch
to
you
know
all
the
interesting
shows,
starting
with
oscon,
which
I
wanted
to
have
an
open
source
flavor.
So
I
think
the
title
kind
of
like
open
source
at
the
edge
and
the
oscon
deadline
is
january
15th.
So
that's
gonna
be
the
first
one
that
I
submit
to
and
I'd
love
to.
C
Have
you
know
one
or
two
people
from
this
working
group
or
more
raise
their
hand
and
say
yeah
if,
if
it
works
out,
if
the
timing
is
convenient,
I'd
love
to
be
considered
as
part
of
the
bench
for
panels
like
that
when
is
oscon
and
what
oscon
is
july
15th
through
the
18th
and
it's
in
portland.
The
cfp
is
due
on
the
15th
of
january.
D
B
B
C
Get
it
okay?
How
about
I
do
this
I'll
I'll!
I'm
gonna
put
I'll
put
you
know
sometime
in
the
next
week
or
so
I'll,
put
together
a
list
of
the
conferences
that
I'm
proposing
and
I'll
just
send
it
to
the
email
list
and
anybody
that
wants
to
raise
their
hand-
and
you
know,
if
not,
I
can
try
to
represent
this
group
on
the
panels
as
well,
so
we'll
just
handle
it
formally.
But
I'd
like
to
have
you
know,
participation
from
from
cncf
and
kubernetes,
and
I
think
this
is
all
right
and
I
I.
B
Think
that
the
last
kubecon
was
the
first
one
we
had
from
this
group
with
the
intro
and
deep
dive
sessions
and
once
again
any
newcomers.
The
links
to
those
videos
and
decks
are
in
the
meeting
notes,
but
I
suspect
that
we'll
that
will
become
a
regular
occurrence
at
all.
The
cube
cons.
I'd
certainly
be
amenable
to
doing
that
myself
and
I'm
planning
on
being
at
those.
So
I
think
the
next
one
up
is
kubecon
shanghai
coming
up
in
in
june
and
shortly
thereafter,
barcelona.
B
I
believe
I
think
barcelona
is
before
oh
before,
okay
and
then
without
official
sanction.
I
gave
a
presentation
on
edge
and
iot
at
the
open
source
summit
in
europe,
and
I
think
I
plan
on
doing
those
on
a
recurring
basis
too,
as
part
of
my
job.
So
great
I'll
I'll
put
you
down
as
a
tentative
volunteer.
C
A
So,
by
the
way
on
the
similar
topic,
I
think
I
checked
the
other
day
and
and
for
for
kubecon
europe,
the
the
the
cfp
actually
closes
something
similarly
like
january
18,
or
something
like
that.
So
if
you
have
some
other
idea,
I'm
not
sure
if
we
would
have
the
same
working
group
sessions
they're
assigned.
But
if,
if
anybody
wants
to
present
anything
else
on
the
topic,
I.
B
Think
I
I
think
dan,
the
normal
expectation,
because
I'm
chair
of
another
sig,
is
that
the
groups
and
sigs
put
on
an
intro
and
deep
dive.
That
doesn't
mean
the
content
has
to
be
the
same,
although
it
is
acceptable
and
seems
fairly
common
to
repeat
when
you
do
it
in
different
geographical
regions,
because
you
do
get
different
people
there.
So.