►
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Kubernetes IoT and Edge Working Group - Steven Wong, VMware & Luwei He
Kubernetes describes itself as "a portable, extensible open-source platform for managing containerized workloads and services". There are edge and IoT use cases that challenge some aspects of Kubernetes. - Run Kubernetes full clusters at edge locations (e.g. retail store and remote branch office) under tight resource constraints - Run containerized workloads at edge with a remote Kubernetes control plane at a cloud or central location - Run devices using non containerized software at edge This session will survey of some existing solutions in the edge and IoT space, covering how they address issues like security, messaging, resource constraints, data communications, application lifecycle management, etc. while working within Kubernetes limitations. We will wrap up with a report on ongoing activity within the IoT Edge working group and details on how you can get involved.
https://sched.co/Nrqt
B
So
the
agenda
today
we're
going
to
get
into
a
survey
of
some
solutions
that
are
available
now
that
relate
to
edge
IOT
and
kubernetes,
because
this
is
a
survey
and
we're
going
to
cover
many
things
that
we
found.
It
won't
be
a
deep
dive
into
any
particular
one
of
them,
but
these
slides
will
have
links
so
that
you
can
get
detailed
background
on
each
of
these
things
and
the
links
that
are
there
are
curated
where
I
took
the
time
to
look
for
good
blog
articles,
there's
always
a
link
to
the
main
project.
B
So
what
we're
going
to
cover
is
some
of
the
aspects
that
are
unique
about
IOT,
an
edge
that
disrupt
the
original
design
of
kubernetes
and
might
call
for
some
alterations
or
compromises
or
add-ons
to
get
it
to
work.
So
one
what
option
you
have
when
you
land,
a
kubernetes
based
infrastructure
at
edge,
is
to
simply
put
a
whole
cluster
at
every
edge
location,
both
the
control
plane,
along
with
one
or
more
worker
notes.
Now
that
might
work
for
some
people.
B
If
they've
got
enough
infrastructure
to
support
this
and
I'm
talking,
you
know
this
might
be
running.
Whole
clusters
with
a
control
plane
at
each
location
might
entail
a
fair
amount
of
hardware,
as
well
as
physical
space
money
to
buy
this,
and
you
you're,
faced
if
you're
running
10,000
of
these
with
dealing
with
10,000
control
planes.
Potentially,
unless
you
have
a
mechanism
to
federate
these
option,
to
is
deploying
a
central
control,
plane,
managing
edge
locations
that
central
control
plane
could
be
in
a
public
cloud
or
it
could
be
in
your
own
on
prim
data
center.
B
But
the
idea
is
that
you
can.
You
would
install
a
kubernetes
control
plane
having
it
connect
to
these
edge
nodes
and
manage
resources
there.
There
are
various
ways
to
do
this.
The
central
control
plane
doesn't
actually
define
enough
of
the
aspects
here
of
what
I'm
getting
at
is.
Do
you
want
the
central
control
plane
with
literally
kubernetes
nodes
at
the
edge
locations,
or
is
it
possible
to
to
use
the
kubernetes
control
plane
with
modifications
to
control
things
that
aren't
actually
kubernetes
located
at
the
edge
and
we'll
get
into
this?
B
The
third
option
is
something
called
virtual
cubelets
that
could
manage
what
this
is
is
normally.
I
could
a
kubernetes
know
the
one
that
runs
the
workload
has
something
called
a
cubelet,
but
it's
possible
to
essentially
fork
the
cubelet
design
so
that
the
kubernetes
control
plane
thinks
it's
talking
to
a
cubelet.
But
it's
really
talking
to
something
acting
as
a
proxy
that
would
take
things
like
pod,
specs,
manipulate
them
and
send
them
out
to
the
to
the
leaf
edge
nodes,
perhaps
in
a
different
form.
B
That
would
take
the
kubernetes
paradigm
of
making
a
declarative
statement
of
what
you
want
the
desired
state
and
causing
it
to
happen.
Maybe
even
saving
these
these
packets
of
desired
states
so
that
if
your
network
connection
is
intermittent
and
you
get
disconnected,
they
would
continue
on
attempting
to
achieve
the
last
known,
desired
state
and
engage
in
resolution
as
the
connection
gets
reestablished
or
as
good.
B
So
we'll
move
on
to
some
variants
of
these
different
forms
of
using
kubernetes
for
IOT
and
edge
some
of
the
differentiating
factors
I'm
going
to
for
several.
But
some
of
them
are
pure
kubernetes,
meaning
pure
what
they
call
upstream,
no
modifications,
some
of
them
have
forked
components
of
kubernetes
where
some
parts
of
kubernetes
are
standard
and
others
have
been
modified
in
some
ways.
Some
adds
specialized
network
support,
which
is
often
very
desirable
when
you're
doing
IOT
and
edge
where
you
want
to
use
non
HTTP
protocols
like
mqtt
and
have
that
managed.
B
Some
ad
management
capability
for
the
hardware,
because
if
the
goal
is
managing
edge
without
skilled
administrators
being
there,
you
might
want
to
do
more
than
just
manage
containerized
workloads.
You
might
want
to
keep
track
of
hardware
health
firmware
on
these
hardware
devices,
and
some
of
these
things
will
describe
are
potentially
prepared
to
do
this,
and
another
common
feature
of
this
is
dealing
with
the
reduced
resources
commonly
available
at
edge.
So
we'll
go
into
form
one
and
the
previous
slide.
What
I
call
whole
clusters
with
control,
plane
and
edge?
B
There's
a
couple
links
here
to
use
case
examples.
These
are
retailers
based
in
the
US,
but
one
is
Target
stores,
which
is
a
retail
chain
common
in
North
America
and
they
wrote
a
blog
article
describing
their
use
of
kubernetes,
where
they're
running
kubernetes
in
retail
stores,
the
and
one
is
chick-fil-a,
which
is
a
fast
food
chain,
selling
chicken
sandwiches,
and
they
gave
a
presentation
at
cube
con
North
America
in
December.
That
was
very
interesting
where
they
described
three
physical
node,
tiny
kubernetes
running
in
these
fast
food
establishments
and
I'm.
B
Not
gonna
I
can't
go
into
detail
on
these,
but
the
link
is
very
interesting
and
in
that
chick-fil-a
case
the
presentation
got
recorded
it
as
part
of
cube
con
North
America.
So
go
take
a
look.
If
that
interests
you
so
first
solution,
I'm
going
to
cover
is
Rancher
k3s
and
he's
not
going
to
speak.
But
we've
got
a
representative
from
Rancher
here.
If
anyone
has
questions
at
the
end,
so
Rancher
k3s
is
an
edge
optimized
micro
distribution
of
kubernetes.
B
So
what
they
did
was
take
kubernetes
and
if
you
see
the
black
portion,
they
remove
some
things
that
aren't
going
to
typically
be
necessary.
For
example,
kubernetes
in
its
current
form
has
multiple
cloud
providers
compiled
into
the
code,
so
kubernetes
supports
running
in
Amazon
Cloud
running
in
Google
Cloud,
if
you're
running
at
an
edge
location,
you're,
clearly
not
going
to
be
on
Amazon
Cloud
or
Google
Cloud,
so
that
code
is
just
unnecessary
and
if
you
remove
it,
you'll
make
it
smaller.
B
Likewise,
it
includes
a
whole
bunch
of
storage
drivers
that
you're
on
it's
very
unlikely
that
you're
going
to
need
all
of
those.
It
adds
features
for
simplified
installation,
TLS
management,
the
automatic
MANET
manifest
and
help
chart
handling
and
there's
a
couple
swap
so
Etsy
D
was
deemed
to
be
resource
intensive,
so
k3s
swaps,
it
out
by
default
for
sequel,
Lite
I.
Believe
it's
an
option
to
go
back
to
Etsy
D.
If
you
want
to
and
you're
prepared
to
give
it
the
resources
they
made
some
decisions
for
you.
B
If
there's
one
standardized
thing
to
build
in
and
by
the
way
it
supports
nodes
with
memory
less
than
for
a
gig,
which
is
a
big
deal.
If
you're
will
you
have
a
limited
budget,
limited
space?
So
clearly,
this
is
it's
not
expecting
rack
mount
servers
resources.
If
you
want
to
learn
more
about
ranch
or
k3s,
the
landing
page
is
good.
B
There's
a
couple
of
blogs,
they're
very
recent,
so
a
rancher
right
now
I
think
is
considered
an
alpha
or
beta
and
still
moving
to
a
declaration
of
a
stable
release
and
that
YouTube
video
is
actually
very
good
at
giving
you
an
overview
of
it.
Now
we're
going
to
move
on
to
a
different
form
of
kubernetes
managing
edge
where
you've
got
a
central,
kubernetes
control
plane
in
a
cloud
or
in
a
big
data
center,
managing
things
out
at
edge.
A
use.
B
A
One
so,
firstly,
let
let's
say
the
age
outrage:
what
does
they
do?
It
moves
a
move
cloud,
animes,
lyrics
and
customer
applications
to
devices.
So
let
the
application,
the
wrapper,
can
focus
on
the
business
logic
instead
of
data
management.
In
that
case,
you
can
pack
your
application
into
a
standard
in
container
and
then
deploy
those
containers
to
any
of
your
devices
and
monitoring
them
from
the
crowd.
There
are
two
solutions
provided
by
a
draughty
agent,
a
judge
who
will
realize
logic.
A
One
is
why
is
water
cooler
when
users
need
to
deploy
application
on
their
own
PI
age
devices,
they
will
use
control
the
way
you
never
use
control.
Can
cuba
control
command
to
send
a
party
specification
to
layers
into
account,
for
example,
AWS
for
pocket
and
limo
chocolate
can
talk
with
ensured
LT
harvel
remotely
to
translate
the
pod
specification
to
the
aisle
to
edit
deployment
and
some
submitted
to
outer
hub
interface
out.
How
can
a
keys
can
orchestrate
applications
to
run
on
the
specific
devices.
A
A
A
B
Do
you
mind
if
I
step
in
and
explain
this
a
little,
so
the
first
slide
was
the
original
form
of
azure
IOT
edge
that
did
not
run
kubernetes
at
the
edge
locations,
but
this
new
one.
The
preview
which
just
came
out
a
few
months
ago,
is
a
different
form
that
actually
runs
kubernetes
at
the
edge
locations.
The
original
one
is
still
there,
so
you
have
a
choice,
and
this
is
just
a
second
version.
Go
this.
A
Project
this
project
will
pull
down
the
deployment
from
out
hub
and
the
translated
into
kubernetes
primitives
and
len-kun
len-kun
Aires
casters
at
age.
You
will
orchestrate
it
to
long
illness,
Pacifica
devices
here
less
no
hard
requirement
for
talker
you
just
you,
can
just
use
kubernetes
instead
and
the
list
solution
enables
users
to
deploy.
Egypt
88
were
close
to
cuban
artists,
cast
own
on
your
own
premise
and
will
not
need
a
water
cure
blood.
So
obviously
no
devices
are
controlled
by
kubernetes
at
acosta
at
edgy.
A
A
A
Cuba
eg,
which
is
the
open
source
project
and
country
working
on
now.
It
is
a
sense
of
sandbox
project,
Cuba
edge
care
of
the
two
kinds
of
reference
architectures.
Not
only
can
it
remotely
control
age,
but
also
it
can
deploy
the
clusters
at
the
age
for
Cinco
cuckoo-bananas
remote
control,
edge,
kinetic
crew,
edge,
Estelle's
proudnet,
you
can
internalize
the
application
orchestration
capabilities
to
a
house
at
age.
A
A
For
deploying
for
lightweight
craft
at
AG,
it's
a
new
feature
called
edge
sight
in
the
lead,
history's
release
of
Cuba
AG
version,
1.0,
H
30
uses
circulate
on
language,
ethnicity
and
the
most
low
cloud
part
down
to
H,
which
make
which
makes
controller
and
lavake
nose
can
work
at
the
same
age,
soul,
a
soul.
A
tone
need
so
little
need.
The
original
crowd
have
an
edge
hub
components.
A
If
you
are
interested
in
courage,
you
can
access
these
links
and
you
can
scan
the
QR
codes
to
focus
on
our,
which
are
the
public
account
and
join
our
technical
exchange.
A
group
and
the
better
way,
lo
Cuba
Cuba
edge
team
has
developed
a
demo
for
less
kill,
Kong
summit.
You
can
go
to
how
I
suppose
to
Lamar
about
it.
B
Okay,
now
we're
going
to
shift
what
we've
covered
so
far
is
variants
of
kubernetes
itself,
either
pure
upstream
kubernetes
or
specialized
forms
of
it,
but
I'm
going
to
move
on
to
tools
and
applications
that
run
with
kubernetes,
either
on
it
or
alongside
it
that
are
useful
in
the
IOT
edge
space,
I'm
not
going
to
contend
I
every
one
of
these,
but
the
for
example,
I
intentionally
left
off
commercial
products
in
order
to
be
on.
In
my
slide
deck.
B
These
are
all
open
source
projects,
and
this
comes
under
the
charter
of
this
edge,
IOT
and
edge
working
group,
because
we
at
our
meetings
we
discuss
not
just
kubernetes
itself
but
applications
and
tools
that
would
run
with
or
on
or
alongside
kubernetes.
So
the
first
one
is
a
project
called
on
mas
and
this
is
managed,
self-service,
self-service
messaging
on
kubernetes
with
built-in
authentication
and
authorization.
B
B
You
can-
and
this
manages
the
communication,
so
the
management
tier
that
effectively
it's
like
an
orchestration
for
your
messaging-
can
run
either
in
a
public
cloud
or
in
an
on-prem
cloud,
and
it
manages
different
patterns
like
request
response,
pub/sub
events,
eclipse
hanno
provides
a
remote
service
interface
for
managing
large
numbers
of
IOT
devices,
implementing
a
back-end
and
interacting
with
them
in
a
uniform
way,
regardless
of
the
device
communication
protocol.
So
you
might
even
have
devices
with
a
proprietary
protocol
or
something
that
used
MQTT
hanno
is
not
the
messaging
protocol
itself.
B
It
simply
puts
in
place
a
means
to
put
a
an
interface
there
that
you
can
manage
these
things
in
huge
numbers.
It's
designed
to
support
data
in
ingestion,
which
is
telemetry
data,
as
well
as
command
and
control
control,
playing
kinds
of
things
going
out
to
edge
devices,
and
it
has
features
for
supporting
provisioning
security.
B
This
control
plane
can
be
deployed
on
kubernetes
itself
if
you're
running
kubernetes
in
a
public
cloud,
and
the
links
are
here
to
learn
more,
including
a
video
that
goes
into
a
full
hours
worth
of
what
eclipse
I
know
was
about
more
than
I
could
cover
here.
Eclipse
ditto
is
an
open-source
project
intended
to
implement
the
concept
of
digital
twins
when
I've
got
things
like
IOT
devices
out
at
edge
that
aren't
always
able
to
connect
back
to
the
cloud.
B
So
it's
intended
to
deal
with
scenarios
where
you
have
intermittently
connected
edge
devices,
so
the
links
are
there
as
well
as
a
video
that
gives
a
deep
dive
into
what
eclipses
do
know
is
about
eclipse.
Hawk
bed
is
a
framework
for
rolling
out
software
updates
to
edge
devices
as
well
as
controllers
and
gateways.
You
know,
kubernetes
itself
publishes
software
in
the
form
of
docker
container
images.
But
what
do
you
do
when
you've
got
these
edge
devices
that
have
packages
of
things
that
aren't
containerized
software?
B
It
could
be
either
executable
binaries,
perhaps
firmware
whatever
might
be
associated
with
this.
The
eclipse
Hawk
bid
is
a
project
intended
to
support
that
scalable
to
millions
of
devices
and
terabytes
of
software
on
a
global
scale.
So
if
you
have
a
need
for
something
like
this,
you
might
want
to
take
a
look
at
this
rather
than
build
your
own
from
scratch,
and
this
can
this
can
run
on.
B
Kubernetes
can
be
deployed
on
kubernetes
at
the
control
plane
level
via
helm,
chart
and
once
again,
I've
got
links
there,
architectural
diagram
and
in
the
interest
of
time
we
can't
go
into
the
deep
dive.
But
I
think
that
if
you
look
at
the
landing
page
in
the
video
that
you
can
learn
more
about
this
Eclipse
io
fog,
now
this
one
I
just
added
this
morning.
This
was
just
announced
four
hours
ago.
So
I
had
to
modify
my
deck
this
morning,
because
I
actually
saw
a
tweet
go
out
from
somebody
with
the
CNC
L.
B
But
beyond
that,
I'm
not
going
to
tell
you
more
than
I
know
other
than
that
this
was
just
announced
today
and
I'm
trying
to
cover.
What's
out
there,
there's
a
there's
a
couple,
others
that
in
the
interest
of
time,
I
don't
have
full
pages
on
and
they're
more
kubernetes
related,
and
these
two
are
injects
foundry
and
a
crane.
Oh
they're,
open
source
projects
that
are
related
to
edge,
but
the
reason
I
don't
devote
a
full
page
to
these
is
I
think
in
their
common
form.
B
They're,
not
at
necessarily
super
kubernetes
centric,
but
I
found
evidence
that
some
people
using
these
are
using
these
alongside
kubernetes
or
managed
by
kubernetes.
Even
if
kubernetes
isn't
the
mainstream
way
today
to
operate
these
things,
so
I
thought
I'd
throw
those
links
in
there
because
I'm
trying
to
be
fairly
complete
here
to
do
the
research
on
what's
out
there
so
that
you
don't
go
reinventing
wheels
when
somebody
is
already
looking
at
open
source
approaches
to
problems
out
there
related
to
IOT
and
edge.
So,
thank
you.
That's
the
end
of
the
presentation.
B
B
Our
group
has
regular
group
meetings
to
each
month
and
we
have
split
these,
so
one
of
the
cycles
of
meetings
is
convenient
for
North,
American
time
zones
or
I
guess:
North
America,
South
America.
The
other
has
been
designed
for
Asian
Eastern
Europe,
so
the
times
and
the
next
meetings
are
indicated
there
just
to
give
you
an
idea
of
what
we
had
at
the
last
one.
B
We
covered
running
a
container
image
repository
on
on
an
edge
location
which
is
of
interest
if
you're
running
docker
eyes,
workloads
at
your
edge
locations
and
we've
got
a
YouTube
channel
that
has
recorded
some
of
these
presentations
that
have
come
out
in
the
past.
There
are
also
recorded
meeting
notes
and
agendas.
B
B
We
also
are
operating
a
channel
on
slack
and
the
group
has
is
maintaining
a
white
paper
that,
in
a
multi-page,
written
form
is
attempting
to
do
something
along
the
lines
of
the
survey
I
just
did
in
this
prison
tation.
Although
it's
been
several
months
since
that
white
paper
was
updated,
some
other
things
you
might
be
interested
in
cube.
Con
Barcelona,
took
place
just
a
month
ago,
and
the
presentation
of
the
IOT
and
edge
working
group
got
recorded
and
it's
published
on
the
sched
site
for
cube
con
Barcelona.
B
B
I'm
not
gonna,
purport
to
be
the
guy
person
to
make
it
I'm
afraid.
My
own
reaction
is
that
I've,
probably
seen
two
or
three
of
them
and
who,
who
I
don't
want
to
be
the
kingmaker
I,
think
that
it
for
the
purposes
of
our
group,
we're
declaring
that
a
lot
of
people
think
edge
might
be.
You
know
sensor
in
control,
but
we're
open
to
it
being
remote
branch
office.
B
There's
often
going
to
be
an
aspect
where
you
assume
the
communications
to
that
location
are
always
good,
because
the
realities
of
the
world
are
the
things
break.
So
that
might
be
another
thing
that
you
can
use
to
define,
what's
edge
versus
just
different
aisles
of
a
big
data
center,
which
I,
don't
think,
is
edge.