►
From YouTube: Keynote: Pushing the Boundaries of Open Source for a Brand New Edge - Saad Malik, Spectro Cloud
Description
Keynote: Pushing the Boundaries of Open Source for a Brand New Edge - Saad Malik, Spectro Cloud
Modern applications deployed at the edge are revolutionizing industries, turning “Kubernetes at the edge” one of the most compelling use cases for the ecosystem. While edge can be challenging to deploy and manage, the significant progress across many community projects is providing the building blocks of a brand new redefined edge that will unlock its true potential. This short keynote will cover the “now” for edge now, what’s required and the future ahead.
A
All
right
welcome
everyone
to
to
kubernetes
edge
date.
It's
really
great
to
finally
see
everyone
out
and
about
enjoying
themselves
interacting
with
our
peers
with
our
community.
It's
been
a
very
long
two
years
now
edge
is
one
of
the
hottest
topics
in
the
kubernetes
ecosystem,
and
presumably,
why
we're
all
here
to
talk
about.
A
So
why
are
we
really
here
well
beyond
the
great
content
that
we'll
be
going
through
today
and
talking
about
right?
We
think
that
edge
is
in
a
really
important
event
over
here.
It's
an
opportunity
for
all
of
us
to
evaluate
and
re-architect
what
a
new
solution
could
look
like
with
modern
requirements
of
a
modern
kubernetes
management
platform.
A
A
We
see
it
every
day
when
we
talk
to
our
customers,
just
like
you
that
edge
kubernetes
enables
compelling
real
use
cases
powerful
enough
to
unlock
new
business
models
and
edge
is
not
just
about
an
itu
location.
It's
about
enabling
innovation
wherever
the
customers
are.
It's
about
providing
experiences
that
were
never
thought
possible
before
edge
is
really
transforming
industries,
and,
if
you
really
think
about
it,
we've
been
talking
about
it
for
quite
some
time.
A
So
the
real
question
is:
what
do
we
want
the
next
era
of
our
edge
kubernetes,
to
really
be
talking
to
people
like
you
and
you'll,
hear
from
others
like
ge
today,
we
think
that
edge
kubernetes
needs
a
few
different
attributes.
It
needs
to
be
lightweight
right.
In
order
for
the
economics
to
really
work,
we
need
to
have
not
only
a
single
n,
but
n
plus
one
configurations
are
just
too
costly.
A
It
needs
to
be
cost
efficient
in
the
terms
of
being
able
to
work
on
a
single
on
a
single
commodity
hardware,
and
it
needs
to
be
even
for
small
form
factors
being
able
to
support
it
end
to
end.
We
need
to
be
able
to
scale
it
from
not
only
hundreds
but
thousands
of
clusters
under
management,
not
only
the
actual
kubernetes
systems,
but
the
management
planes
have
to
be
able
to
support
that
end-to-end.
A
We
need
to
be
open
and
flexible
to
all
the
technologies
and
tooling
in
and
around
of
kubernetes,
whether
whether
these
are
open
source
technologies
or
even
commercials
technologies,
and
these
should
be
driven
not
by
the
actual
requirements
of
the
of
the
underlying
hardware,
but
by
the
application
requirements,
and
it
needs
to
be
autonomous
right.
We
think
about
running
kubernetes
at
the
edge
in
most
disparate
locations
that
are
very
challenging
for
us
to
be
able
to
support
edge
reliably.
A
It
needs
to
be
able
to
work
not
only
for
environments
that
have
limited
connectivity,
but
even
potentially
no
connectivity
and,
of
course
it
needs
to
be
easy.
If
you
think
about
the
skill
set
required
to
actually
manage
kubernetes
at
skill,
it's
very
difficult.
Do
we
really
want
to
hire
an
army
of
kubernetes
experts
who
are
there
to
manage
and
troubleshoot
the
entire
kubernetes
management
platform
at
your
retail
restaurants
at
your
coffee
shops
at
each
of
your
different
hospitals?
The
answer
should
be
obvious.
A
It's
no
and
by
the
way,
when
we
think
about
all
the
various
integrations
that
go
into
kubernetes
there's
a
plethora
of
options
to
choose
from.
We
are
big
believers
in
not
having
to
sacrifice
the
freedom
of
choice,
to
get
the
control
that
you
need
to
run
kubernetes
at
scale,
and
the
edge
is
no
exception.
A
A
However,
when
it
comes
to
edge
resiliency
and
consistency
is
equally
important
and
we
need
to
build
immutable
operating
systems
that
can
be
provided
using
something
like
ubuntu,
core
or
flat
car
os
linux.
When
it
comes
to
the
kubernetes
distribution,
the
edge's
hardware
requirements
may
dictate
what
are
the
actual
requirements
of
the
distro
right.
Great
examples
of
purpose-built
edge
distributions
include
like
canonical
micro
kubernetes,
which
has
goes
the
extra
mile
for
supporting
extra
performance
as
well
as
security,
or
we
are
looking
at
other
solutions
like
rancher
k3s.
A
One
thing
to
also
note
regarding
the
cube
red
is
distrib
regarding
the
kubernetes
distribution.
It's
just
one
piece
of
the
puzzle
for
kubernetes
to
really
scale.
In
effect,
there
are
many
other
layers
that
you
have
to
bring
in
on
the
networking
side.
Observability
is
key,
so
calico
is
a
safe
option
that
everybody
uses,
but
I
surveillance
psyllium
provides
out-of-the-box
performance
network
policies
along
with
observability
across
all
the
layers,
from
layers
3
to
layer
7.
A
A
As
you
can
imagine,
there
are
many
other
awesome
integrations
and
toolings
available
that
fit
into
a
modern
kubernetes
management
platform,
whether
it
is
for
an
actual
general
clusters
or
whether
it's
for
the
edge
other
areas
to
consider
tooling,
would
include
securing
your
applications
at
the
edge
right
using
potentially
technologies
like
opa
and
caverno.
We
have
technologies
that
provide
rich
metrics
and
observability
using
service
meshes
or
even
managing
the
state
of
all
your
applications
at
scale
with
something
like
get
ops
through
argo,
cd
or
flux.
A
We
really
hope
that
you
enjoy
the
day
and
what
would
love
to
hear
you
see
later
today
at
the
new
stack
tapas
event,
where
we'll
be
talking
about
some
kubernetes
edge
requirements
in
detail,
we'll
also
be
having
free
fruit
and
drinks.
Please
also
stop
by
our
booth
at
s57
to
see
our
kubernetes
management
platform
in
action
both
for
enterprise
kubernetes,
as
well
as
for
edge
kubernetes
on
behalf
of
spectrocloud
and
cncf,
have
a
wonderful
event,
and
thank
you.