►
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Edge Computing using K3s on Raspberry Pi - Jeff Spahr, Lenovo
K3s is a lightweight single binary Kubernetes distribution that is simple to install, and it's a perfect match for the latest Raspberry Pi 4. Join the speaker as he walks through the design, implementation, and trade offs you'll have to consider for this edge architecture. In this talk I'll cover the following:
The why and how of deploying a production grade highly available 3 node K3s cluster.
How to capture all the configuration as code and drive changes through GitOps.
How to manage automatic updates for the cluster and operating system through the Kubernetes API.
The speaker will be building on https://github.com/jeffspahr/k3s-on-pi for this presentation.
A
A
So,
let's
start
with
what
is
edge
computing,
it's
when
you're
bringing
compute
and
storage
closer
to
the
source
of
the
data.
This
is
typically
sites
that
are
not
data
centers,
so
it
could
be
factory
floors,
vehicles,
retail
stores
or
restaurants,
wind
farms.
It
could
be
constraints
around
space
power
or
cost.
A
A
A
For
me
that
was
yep
that
that's
enough
to
go
ahead
and
run
a
kubernetes
node
with
the
applications
I'm
interested
in.
So
this
will
be
a
fun
home
lab
project.
They
all
have
the
same
processor,
it's
a
quad-core
arm,
64.,
they're,
small
and
quiet
they're
inexpensive
and
they
have
low
power
consumption.
A
A
A
A
A
A
I
bought
this
in
pieces
too.
If
I
did
it
all
at
once,
I
probably
would
have
thought
twice
because
I
didn't
realize
I
spent
400
on
this
present,
but
still
it's
relatively
inexpensive
compared
to
you
know,
buying
three
three
servers
and
doing
anything
with
them
core
project
goals.
For
me,
I
wanted
to
get
to
the
kubernetes
api
as
fast
as
possible.
A
Every
every
layer
below
that
was
slowing
me
down,
and
it's
important
to
note
that
this
was
my
goal
spin
time
on
the
lower
layers.
If
you
haven't
already,
I
wanted
to
be
so,
I
wanted
to
be
able
to
take
nodes
out
whether
it's
for
an
upgrade
or
you
know
to
swap
it
out,
because
there
was
a
hardware
failure
without
disrupting
the
application
I
had
running
on
there.
I
wanted
it
to
be
relatively
inexpensive.
A
So
step
one
was
create
an
image
I
used
ubuntu,
there's
really
good
arm.
64
support
with
ubuntu
there's
a
tutorial
linked
to
how
to
image
your
sd
card
around
this.
But
basically
I
was
using
a
mac
at
the
time
to
do
this
list.
Your
volumes
unmount
the
one:
that's
the
sd
card,
and
do
this
little
one
liner,
where
you're
unzipping
the
image
and
dding
it
to
that
sd
card.
A
It
was
important
to
me
to
have
this
just
join
the
network
and
and
get
an
ip
address
on
boot
because
I
didn't
want
to
have
to
hook
each
one
up
to
a
monitor
and
keyboard
and
configure
network.
So
I
use
netplan
to
do
this.
Pretty
simple
configuration
just
here's
your
the
name
of
your
access
point:
here's
the
secret
to
join.
A
A
You'll
see
the
the
first
thing
I'm
doing
is
just
setting
the
host
name.
Then
I'm
adding
my
user
saying
don't
require
a
password
for
sudoing
with
my
user,
I'm
putting
my
ssh
key
on
there,
and
this
is
a
pretty
useful
trick.
If
you
don't
know
about
it
already
is
you
can
just
grab
those
off
of
github
and
then
this
was
the
important
one
enabling
c
group
in
this.
This
boot
option
that
that's
required
in
order
to
run
keys
or
kubernetes
in
general.
A
A
A
A
And
I'll
walk
through
what
the
install
file
does
so
really
simple:
back
script,
just
wrapping
the
racking
ketchup.
Here's
my
kubernetes
version,
here's
my
my
three
different
nodes:
here's
the
user!
I
want
you
to
connect
as
the
first
one
catch
up,
install
and
the
second
node
is
catch
up,
join
and
the
third
node
same
thing.
Catch
up,
join
and,
at
the
end
of
here,
remind
you
to
set
your
cube
config
and
tell
you
where
it
is.
A
A
So,
while
that's
running
I'll
talk
through
some
of
the
bootstrapping
mechanisms
that
you
can
use
any
any
manifest
or
or
helm
chart
that
that
sits
in
this
folder
on
the
server
var
lib,
rancher
keys,
server,
manifest
will
get
applied
as
if
it
was
a
coupe
ctl
apply
dash
f.
So
this
is.
This
is
all
stuff
that
comes
out
of
the
box
core
dns.
A
I
mentioned
that
local
storage
provider
metric
server
and
that
traffic
ingress
controller,
but
you
could
use
this
if
you
wanted
to
to
add
your
own
manifest
for
things
that
you
wanted
to
bootstrap
and
then,
if
you
do
have
constraints
around
not
having
an
internet
connection,
there
are
some
tricks.
You
can
do
with
cri
ctl
to
manually
unpack
an
image
you'll
just
do
that
on
each
of
the
nodes.
A
A
A
A
A
A
So
that's
exciting.
That
was
pretty
low
effort
to
get
a
three-node
kubernetes
cluster
out
the
door.
Some
of
you
all
might
notice.
The
the
age
of
these
is
is
more
than
just.
You
know
a
couple
of
minutes.
That's
because
I've
already
gone
through
this
several
times,
but
you
can
rerun
the
ansible
playbooks
and
you
can
rerun
the
install
and
it'll
actually
go
through
and
do
it
all
again.
A
A
So
here
we
have
an
upgrade
plan
that
includes
a
server
which
is
which
is
the
control,
plane,
node
and
keys
terms,
as
well
as
an
agent
which
is
just
a
worker
node.
For
this.
For
my
my
cluster,
we
really,
we
only
have
servers
they're
all
control
claim
nodes,
but
I
included
them
both
in
here
in
case
that
changes.
A
A
And
as
that
job
starts
running,
we
should
see
that
cycle
through
each
of
the
kubernetes
okay.
So
this
is
actually
a
good
good
sign.
You
see
that
my
connection
to
the
api
server
failed.
This
is
something
that
I'll
talk
about
in
one
of
my
next
slides.
It's
the
it's
the
only
piece.
That's
not
so.
This
is
in
the
sense
that
there's
three
control
plane
nodes,
they're
all
running
at
cd,
and
that's
that's
clustered.
A
A
A
A
A
My
original
intent
was
to
watch
this
folder
with
our
ucd,
so
we'd
have
a
git
ops
flow
where
I'd
upgrade
or
update
the
the
repo
and
then
that
would
automatically
get
applied
to
the
cluster
I'll.
I'm
gonna
be
coming
back
to
that
argo
cd
doesn't
have
an
rm64
image
yet,
but
it's
pretty
close
so
once
that's
available
I'll
pick
up
that
piece
of
the
project.
A
So,
as
I
create
you
know,
ingress
resources
or
that
sort
of
thing
it's
going
to
also
create
a
dns
record
for
them,
also
using
cert
manager
to
make
sure
I
get
real
certs.
It's
so
easy
these
days
with
cert
manager
and,
let's
encrypt,
to
get
real
certs
that
there's,
you
know
kind
of
no
reason
not
to
go
down
that
route.
A
A
So,
what's
next
for
this
project,
so
I
mentioned
cubevip.
I
need
to
finish
that
up
in
order
to
have
you
know,
api
server,
failover
and
have
this
truly
aha,
that's
that's
already
out
and
available.
I
just
I
just
ran
out
of
time
so
I'll
come
back
to
that
and
upgrade
this
update
this
repo.
Once
I
have
that
working
argo
cd,
arm64
support,
I
started
this
project
over
six
months
ago
now,
they're
they're,
very
close
to
to
having
arm64
support
built
into
their
build
process.
That's
coming
in
version
2.2
and
they're
on
version.
A
2.1
now
and
that'll
make
this
a
full.
You
know
github
style
of
management.
I
also
want
to
spend
some
time
looking
at
something
like
tinkerbell
to
bootstrap
over
the
network.
Instead
of
imaging
an
sd
card,
that's
a
fairly
manual
process
of
you
know,
taking
an
sd
card,
plugging
it
into
your
laptop.
You
know
running
that
that
dd
command
to
image
it
and
then
putting
it
back
in
your
raspberry
pi
and
hooking
up
your
raspberry
pi.
A
A
A
I
have
this
arbitrary
version
number,
since
all
I'm
doing
is
a
an
apt
upgrade
over
here.
The
the
server
upgrade
controller
just
needs
to
have
a
version.
Number
that's
changed,
so
it
knows
that
it
needs
to
act
on
this,
so
this
was
the
the
best
way
I
could
think
of
to
solve
that
for
for
now.
But
if
I
was
to
change
that
to
0
1.5,
it
would
say:
hey,
it's.
I've
got
to
apply
this
new
plan
and
it
would
run
this
this.
A
So,
thank
you
appreciate
your
time
and
coming
to
this
session,
I'm
including
a
github
link
here
for
that
repo.
It
should
be
pretty
out
of
the
box.
You
can.
You
can
follow
that
readme
and
you'll
end
up
with
a
three
node
cluster
with
all
these
over
the
top
components
sitting
in
that
manifest
cluster
or
folder
as
well.