►
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon North America 2021 in Los Angeles, CA from October 12-15. 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.
Overview and State of Linkerd - William Morgan & Matei David, Buoyant, Inc.
In this talk, maintainers from the Linkerd project will present an overview of the project and an update on upcoming releases. They'll cover what Linkerd is and how it compares to other service meshes; what the latest features and functionality are; what to expect in upcoming releases; and how you can get involved in one of the CNCF's most talked-about projects. This talk will cover Linkerd's modular control plane (2.10) and upcoming policy (2.11) features, as well as the latest on Linkerd's Rust micro-proxy, Linkerd2-proxy.
A
Hi
there
I'm
william
morgan
and
I'm
one
of
the
creators
of
linker
d,
welcome
to
the
kubecon
eu
2021
overview
and
state
of
linker
d
talk
I'll,
be
joined
by
linkery
contributor,
mate
david.
He
will
present
the
second
part
of
the
talk
with
the
current
state
of
the
project
and
I
will
be
providing
the
overview
so.
A
Mesh,
if
you
don't
know
what
a
service
mesh
is
I'll,
give
you
a
very
brief
definition
in
the
next
slide,
but
suffice
it
to
say
that
link
rd
is
a
very
unique
kind
of
service
mesh
for
one.
It
is
very
focused
on
being
as
light
and
as
fast
and
as
simple
as
possible
for
kubernetes
environments.
Lingerie
has
been
in
production
for
over
four
years.
We
have
a
very
healthy
and
active
community
centered
around
the
slack
channel,
and
we
have
lots
and
lots
of
github
stars.
So
thank
you.
A
A
A
So
what
does
lincrdie
do
like
any
service
mesh?
We
categorize
its
features
into
three
buckets:
a
set
of
features
around
observability
things
like
golden
metrics
and
service
topologies
and
distributed
tracing
a
set
of
features
around
reliability,
things
like
load,
balancing
and
traffic
shifting
and
retries,
and
there's
a
set
of
features
around
security,
mostly
built
off
of
mutual
tls,
and
the
interesting
thing
about
link
rd
and
any
service
mesh
really
is
that
we
cannot
be
a
complete
solution
to
any
of
those
categories.
So
linkery
is
not
a
complete
observability
solution.
A
You
still
have
to
instrument
your
application.
It's
not
a
complete
reliability
solution.
Your
application
has
to
handle
all
sorts
of
failures
that
link
rd
cannot
protect
against,
and
it's
certainly
not
a
complete
security
solution.
But
the
set
of
features
that
linker
d
can
give
you
sit
at
the
platform
layer
and
they
belong
as
part
of
the
platform,
and
so
what
the
service
mesh
gives.
You
is
the
ability
to
get
those
features
at
the
platform
layer
without
having
to
rely
on
developers
to
implement
them
in
their
application.
A
So
how
is
lingerie
designed
in
short,
less
is
more
very
powerful
statement.
So
if
you
have
a
functioning
kubernetes
application
and
you
install
linker
d,
the
application
should
continue
functioning
some
minor
asterisks
on
that
statement.
But
we
can
do
that
from
the
vast
majority
of
cases,
so
zero
config
out
of
the
box,
you
should
be
able
to
just
add
linker
d
to
a
system
and
not
break
anything.
A
A
As
possible,
and
by
simple
I
mean
operationally
simple,
which
means
you:
the
operator
should
not
have
to
waste
your
precious
life
energies
worrying
about
the
service
mesh.
You
should
be
able
to
let
it
run
and
understand
it
and
feel
confident
in
it
then.
Finally,
to
the
extent
that
it's
possible,
when
we
have
security
features,
we
try
and
enable
those
features
out
of
the
box
and
not
to
put
them
behind
barriers
involving
configuration.
A
So
lingerie
today
has
a
control
plane,
that's
written
in
go
so
it's
in
a
kubernetes
name,
space,
it's
about
200
banks,
and
then
it
has
a
data
plane
built
out
of
these
rust
micro
proxy.
So
I'll
talk
more
about
that
in
a
few,
more
slides
that
are
extremely
fast
and
extremely
light.
Lingerie
has
a
long
history.
It
was
originally
actually
a
jvm
application
and
I
wrote
a
little
bit
about
that
history
in
this
article.
A
A
So
the
application
is
blissfully
unaware,
but
traffic
is
going
through
the
proxy,
and
that
is
how
the
surface
mesh
does
its
magic
linker
d
2.10,
which
is
the
latest
version,
introduces
this
notion
of
extensions.
So
if
you
want
additional
functionality,
you
can
add
these
opt-in
extensions.
There's
one
called,
which
is
demonstrated
here
called
the
vis
extension,
which
is
a
metrics
pipeline,
includes
things
like
prometheus
and
grafana,
and
a
web
dashboard
that
take
all
of
the
metrics
that
the
proxies
instrument
and
turn
them
into
a
set
of
human
consumable
outputs.
A
A
So
that's
the
control
plane
on
the
data
plane.
We
use
a
proxy
called
simply
linker
d2
dash
proxy
linker
d
is
unique
in
a
lot
of
ways.
One
of
those
ways
is
that
this
proxy's
not
envoy.
I
wrote
a
long
article
about
why
that
is
so.
If
you
want
to
dig
more
into
this,
just
search
for
why
linker
d
doesn't
use
envoy
or
click
on
that
link
in
the
slides
below
the
short
story
is
rust.
A
Rust,
of
course,
compiles
a
native
code,
so
we
can
be
as
fast
as
the
machine
will.
Let
us
be
and
using
rust
gives
us
access
to
a
state-of-the-art
network
stack,
so
libraries
like
tokyo
and
hyper
and
tower
and
the
rest
of
the
modern,
rust
asynchronous
networking
stack.
I
think
this
part
of
lanker
d,
the
linker
d2
proxy,
is
probably
the
most
advanced
technologically
advanced
project
in
the
entire
cmtf
landscape.
A
A
Linkerity
is
very
security
focused
and
we
have
a
very
strict
philosophy
that
starts
with
number
one
making
sure
that
the
foundations
are
secure,
which
is
a
big
part
of
why
linker
d2
proxies
written
in
rust
number
two
building
on
top
of
kubernetes
as
much
as
possible,
so
rather
than
introducing
new
primitives
use
ones
that
are
already
there,
things
like
service
accounts
and
then
removing
the
barriers
as
much
as
possible.
So
you
know
the
moment
you
install
linker
d
and
you
mess
your
application.
A
All
tcp
communication
is
automatically
put
behind
mutual
tls
without
you
having
to
configure
anything
complexity
is
the
enemy
of
security.
That's
our
belief,
and
so
we
want
to
reduce
the
configuration
as
much
as
possible
turn
it
all
on
by
default
and
basically
don't
make
you
have
to
work
for
security.
A
A
Linker
d
has
a
very
different
philosophy,
which
is
we
should
give
you
the
bare
minimum
to
build
a
secure
and
reliable
and
flexible
kubernetes
platform.
So
it's
much
easier
to
understand
and
operate
smaller
lighter
faster,
but
it
is
also
very
kubernetes
specific.
So
if
that
doesn't
work
for
you,
then
linker
d
will
not
be
the
right
service
mesh
for
you
here
at
kubecon
eu
2021.
We
actually
have
a
pretty
amazing
lingerie
turnout.
So
if
you
want
to
learn
more,
I
encourage
you
to
look
at
to
attend
some
of
these
talks.
A
Oliver
gould,
who
is
the
creator?
The
real
creator
of
linkery,
we'll
be
delivering
a
talk.
Why
the
future
of
the
cloud
will
be
built
on
rust
on
may
3rd
on
may
4th
at
service
meshcon
we've
got
a
whole
set
of
end-user
talks.
Around
scheduling,
covered
tests,
doing
experimentation,
adding
fips,
140
compliance
and
doing
chaos.
Testing
may
5th
we've
got
some
debugging.
A
We've
got
some
compliance,
the
easy
way,
talks
that
sounds
scary
and
seamless,
multi-cluster,
communication
and
observability,
and
then,
finally,
if
you
really
enjoy
my
voice
I'll,
be
giving
a
keynote
about
linker
d
versus
covet
19
on
may
6th.
So
I
encourage
you
to
join
those
talks
with
that
said,
I
am
now
going
to
hand
things
over
to
linker
d
contributor,
mate,
david.
B
Thank
you
william
and
hello.
Everyone.
My
name
is
mate
and
today
I'll
be
giving
you
a
brief
overview
on
linker
d
in
2021.,
specifically
I'll,
be
talking
about
some
previous
releases
that
we've
had
I'll
touch
base
on
the
roadmap,
give
you
some
community
updates
and
finally
tell
you
how
you
can
be
involved
so
before
I
start
I'm
going
to
talk
about
myself
for
a
little
bit.
B
I've
been
a
linguity
contributor
for
over
a
year
now
and
like
a
lot
of
people
in
the
community,
I
had
my
first
contribution
completely
by
accident.
I
stumbled
upon
linkerdy
when
I
was
looking
for
some
projects
to
to
contribute
to.
I
attended
my
first
meetup
in
march
2020
after
I
saw
how
inclusive
and
supportive
the
community
is,
I
kind
of
got
over
my
anxiety
of
contributing
to
open
source.
So
in
april
2020
I
had
my
first
merge
pr
and
it's
sort
of
snowballed
from
there.
B
B
B
B
B
We
have
our
graduation
proposal
officially
submitted
it's
still
early
days
to
talk
about
it,
but
I
just
wanted
to
kind
of
echo
this
out
and
let
people
know
that
it's
been
submitted
and
I'm
super
excited
about
it,
huge
round
of
applause
for
for
the
whole
team
and
community
all
right.
Now,
let's
get
technical.
When
I
first
joined
as
a
contributor,
the
team
had
just
released
2.8
multi-cluster
support,
well,
lingard,
multi-cluster
and
also
the
idea
of
add-ons
started
floating
and
that's
important.
B
B
I
won't
be
going
into
details
now,
but
a
lot
of
work
went
into
2.9.
It
was
a
huge
release,
happened
in
november
and
it's
very
close
to
my
heart,
because
the
cncf
mentorship
schemes
projects
were
also
delivered.
As
part
of
this,
we
had
arm
support
which
allows
linkery
to
run
anywhere
on
raspberry
pi's.
I
use
it
on
my
pi
clusters,
for
example.
This
was
a
gsoc
project.
B
We
had
multi-core
proxy
runtimes
to
add
throughput
and
concurrency
service
topologies
my
project
as
part
of
cncf
lfx,
to
introduce
routing
preferences
on
per
node
bases
and
bring
your
own
prometheus
to
make
the
control
plane
lighter.
So
if
in
2.8
we
started
floating
around
the
idea
of
an
add-on
in
2.9,
it
started
taking
shape
and
then
in
2.10
it
came
to
fruition
because
we
delivered
modularized
control
plane
with
extensions.
B
B
So
with
linkrd
2.10,
you
can
pick
and
mix
what
you
want
with
your
link
or
distribution
out
of
the
box.
The
control
plane
comes
with
the
discovery,
service,
identity
and
zero
config
mtls,
and
then
we
have
this
extension
for
the
metric
stack,
so
prometheus,
grafana,
dashboard,
linker
dtap,
which
is
an
amazing
tool,
jager
extension
for
distributed
tracing
and
then
the
multi-cluster
extension
for
those
of
you
that
want
to
do
multi-cluster
and
on
the
topic
of
multi-cluster.
B
In
2.10,
we've
extended
multi-cluster
to
tcp
connections,
so
before
linker
d
was
more
geared
towards
http
with
multi-cluster
and
then
2.10
that
changed.
We've
also
included
opaque
ports
to
proxy
traffic
without
protocol
detection,
so
linker
d
used
protocol
detection
to
determine
if
you're,
running,
grpc
or
http,
and
this
aided
and
load
balancing
decisions,
and
also
in
nltl
in
mtls
but
with
opaque
ports.
We
also
added
support
for
server
speak
first
protocol
we're
doing
mtls
is
a
bit
trickier,
but
yeah
there's
a
great
blog
post
about
this.
B
You
can
make
it
so
that
service
owners
can
require
connections
to
be
mtls,
and
then
service
owners
can
also
limit
which
client
can
connect
to
their
server.
So
to
kind
of
have
a
visual
eight.
For
this.
I
have
this
very
simple
diagram
to
the
left,
where
we
have
three
pods,
all
of
them
running
inside
a
mesh,
and
if
you
have
two
servers
a
and
b,
then
you
can
configure
some
policies
on
the
server
to
say.
Okay,
I
do
not
want
the
client
to
connect,
or
I
do
not
want
the
client
to
connect
without
mtls.
B
B
Finally,
the
get
involved.
My
favorite
part
of
the
presentation,
all
of
our
development,
is
on
github
we're
active
in
the
discussions.
We're
active
in
issues,
pull
requests,
so
please
come
and
have
a
look
if
you're
curious
or
if
you
want
to
contribute,
please
feel
free
to
do
so.
It's
very
easy
to
get
set
up.
B
B
Most
of
all,
I
think
what
I
want
to
say
is
that
to
be
a
contributor
with
linkerd,
you
do
not
really
need
to
contribute
code,
we
accept
contributions
in
all
forms
and
shapes,
and
actually
we
encourage
people
to
do
some
doc
contributions.
They
come
and
help
out.
On
slack,
there
are
a
lot
of
people
with
good
production
experience
that
give
great
advice
on
slack.
B
There
are
a
couple
of
people
that
I
really
look
up
to
that
are
daily
active
and
helping
people
out
so
yeah
we're
a
very
friendly
and
welcoming
community
join
us,
it's
tons
of
fun
and
we're
we're
doing
lots
of
good
work.
So
that's
it
from
me.
I
think
it'll
be
time
for
q
a
yeah,
I
hope
you're
excited
as
I
am
for
linker
day
and
stay
tuned
for
more
updates
to
come
in
2021.