►
From YouTube: Panel: The State Of Service Mesh - I. Levine, M. Palladino, L. Ryan, L. Sun, W. Morgan, N. Jackson
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.
Panel: The State Of Service Mesh - William Morgan, Buoyant, Idit Levine, Solo.io, Nic Jackson, Harshicorp, Marco Palladino, Kong Inc & Louis Ryan, Google, Moderated by: Lin Sun, Solo.io
Do you need a service mesh? Is service mesh getting easier? What is the current state of the service mesh ecosystem? Join us for a live interactive session where our panel of service mesh experts from various service mesh projects (Istio, Linkerd, Consul Connect and Kuma) are eager to discuss with you the latest service mesh technology improvements, best practices for adopting service mesh, challenges that lie ahead for these projects, and what’s next for service mesh in the coming year.
A
A
A
D
A
E
A
B
Yeah,
so
like
everything
in
life,
this
is
a
trade-off
right.
I
mean
there
is
a
lot
of
advantage
that
service
meshes
bring
you
to
the
table.
Specifically,
I
think
all
of
the
service
mesh
is
focusing
on
observability
security
as
well
as
routing
traffic
and
policy.
So
that's
bringing
a
lot
of
benefit,
though,
if
what
you
have
is
one
application
with
two
microservices.
Maybe
it's
an
overkill.
D
But
perhaps
it
is
an
opportunity
for
us
to
stop
doing
the
hundreds
of
things
that
the
application
teams
are
doing
every
time
when
they
want
to
make
a
request
over
the
network
or
receive
a
request
for
the
network.
The
things
that
service
mesh
solves
are
not
things
that
we
don't
need
without
a
service
mesh.
We
still
need
them
the
security,
the
observability.
F
I'll,
just
chime
in
and
say
from
you
know,
we
help
a
lot
of
organizations
adopt
linker
d
and
typically
you
know
the
there's.
The
value
prop
of
the
service
mentioned.
Are
you
set
up
for
this
and
they
are
you
set
up
for
this
component?
Is
you
know,
are
you
already
operating
basically
in
kind
of
a
cloud
native
way
like?
Do
you
have
a
platform
team
that
owns
the
underlying
platform
that
can
take
on
the
service
mesh
as
part
of
their
responsibility?
If
you're?
F
Not,
if
you
don't
have
that,
then,
like
you
know
that
all
the
technology
in
the
world
is
not
going
to
help,
you
are
you
operating
in
a
world
where
the
developers
you
know
are
able
to
own
their
services.
You
know
and
build
on
top
of
the
platform
without
having
to
understand
every
detail
of
the
platform.
If
you
don't
have
that,
then,
like
the
technology
is
not
going
to
help
you,
so
there
are
some
organizational
prerequisites,
which
is
what
we
typically
look
for.
F
C
I
mean
I
much
agree
with
marco.
I
think
it's
a
trade-off
between
platform
running
a
platform
and
and
actually
having
to
write
code,
but
I
I
do
think
that
the
the
problem
of
writing
the
code
isn't
necessarily
going
to
go
away,
but
the
the
problem
around
managing
the
platform
will
get
easier
as
tight.
Good
time
goes
on
and
sort
of
the
various
vendors
come
to
the
market
which
provide
you
with
a
managed
service
mesh.
E
Yeah-
and
I
think
you
know
talking
about
platform
and
platform
management-
I
think
william
and
nick
and
marco
covered
that
pretty
well.
There's
there's
also
the
top-down
constraint
right
if
you're
in
a
regulated
industry
right
and-
and
you
have
to
do-
zero
trust
networking.
Like
things
you
know,
your
options
are
moderately
limited
right
and
they
range
from
the
open
source
to
the
eye
watering,
the
expensive
commercial
solution.
So
yeah
I
mean
those.
Those
are
the
things
that
often
drive
these
decisions
outside
the
kind
of
core.
Like.
E
F
It's
getting
easier,
I
guess
you
know
it's,
it's
not
getting
harder.
I
think
you
know
for
enterprises,
especially
there's,
like
you
know,
kind
of
a
new
swath
of
vendors,
and
so
like
some
of
the
landscape
becomes
more
complicated
and
now
your
your
feature,
matrix,
you
know,
has
like
100
rows
in
it,
whereas
last
year
might
have
had
50
rows.
So
I
think
in
some
ways
it
gets
a
lot
it's
getting
more
complicated,
but
you
know
the
tooling
is
being
built
up
so
yeah.
B
Yeah,
so
I
think
that
it's
definitely
getting
easier,
but
I
think
we're
just
scarfing
the
the
surface
of
how
can
we
make
it
even
easier-
and
I
think
right
now,
starting
to
get
to
the
point
that
servicemen
is
becoming
getting
to
a
maturity
that
is
actually
can
can
be
adopted
easier.
Let's
say,
but,
as
I
said,
I
think
that
there
is
way
more
stuff
that
we
can
do
in
order
to
make
it.
You
know,
build
the
tools
easier,
the
user
experience
easier.
B
D
And
I'm
a
big
believer
of
simplicity,
I
think
simplicity
is
a
feature.
Good
documentation
is
a
feature
you
know
easier
to
adopt.
Is
it
easier
for
the
platform
teams
to
deploy
it
to
the
application
teams?
It
is
it
easier
for
the
application
teams
to
write
their
software,
knowing
that
there
is
a
service
mesh?
So
I
think
there
is
two
angles
to
this
question
and
service
mesh
is
certainly
getting
easier
to
use
easier
to
deploy.
E
So
I
you
know,
I
think
that
you
know
the
service
mesh
products
that
are
out
there.
You
know
have
gotten
collectively,
better
at
kind
of
day,
zero
and
day
one
right.
So
what
you
see
now
in
enterprise
is
you
know
that
day,
two
operation
stuff
really
starting
to
dominate
conversations
at
least
certainly
the
ones
that
I
have
you
know
if
you
ship
four
releases
a
year
and
the
the
company
has,
you
know
the
manpower
to
absorb
one
update
a
year.
E
You
know
how
are
they
supposed
to
engage
with
the
product?
You
know
what
are
their
costs
to
perform?
Upgrade
you
get
lots
of
like
you're,
seeing
growth
in
the
number
of
managed
service
mesh
offerings
right,
not
just
installed
offerings.
In
response
to
that,
I
think
so
that
you
know
the
conversation
has
shifted.
E
As
you
know,
the
early
adopters
are
now
into
a
little
bit
later
in
their
maturity
cycle
and
are
dealing
with
those
day.
Two
issues
and
those
are
becoming
known
to
you-
know
the
the
buying
side
of
the
market
and
so
they're
asking
the
same
questions
in
rfcs
and
things
like
that
are
these.
So
I
think,
that's
you
know,
there's
still
plenty
of
room
for
growth.
C
C
That
makes
a
massive
advancement
in
successful
use
of
the
tool
and
the
adoption
of
the
tool,
and
I
think,
as
time
goes
forward
and
more
and
more
people
are
creating
tutorials
and
videos
and
blog
posts,
and
things
like
that,
then
that
kind
of
community
contribution
of
knowledge
really
really
helps
adoption
of
of
service
mesh.
I
think
it
can
always
get
better
and
I
think
it
will,
but
I
think
right
now,
it's
you
know
it's
really
good.
It's
definitely
not
something
that
you
question
whether
it's
a
production,
ready
technology
anymore.
D
D
I
really
cannot
see
how
that
could
be
possibly
successful
and
lots
of
enterprise
organizations
right
now
and
practitioners
are
seeing
that,
and
so,
as
the
adoption
of
service
mesh
increases,
which
is
increasing
service,
mesh
products,
will
get
more
mature
and
we're
going
to
hear
more
and
more
success
stories
from
them
on
how
they
enabled
these
transformations
with
service
mesh.
So
it's
a
very
interesting,
very
interesting
times
ahead
of
ahead
of
us.
B
Yeah,
so
I
think
that
when
we're
looking
about
the
current
state,
I
think
that
I
think
that
if
you're
looking
at
the
roadmap,
it's
most
of
those
meshes
basically
today
everybody's
talking
about
make
it
boring
right,
I
mean
it's
done.
The
future
are
there
and
now
it's
relatively
boring.
So
I
think
this
is
a
very
interesting
time,
because
that
shows
a
huge
maturity
in
the
market
and
definitely
there
is
a
market
fit
right.
I
mean
that's
why
we
have
this
conference.
This
is
why
we
are
here
talking
about
it.
B
Obviously,
service
mesh
has
a
market
fee.
I
think
that
the
interesting
thing
that
will
come
after
it,
which
I'm
personally
extremely
excited
about
it,
is
how
we
can
even
put
push
the
boundary
okay.
So
now
we
have
this
great
platform
that
we
all
agree
that
should
be
there,
and
I
think
everybody
will
agree
in
the
organization.
As
marco
said
in
like
a
fibrous
thing,
it's
just
going
to
become
part
of
this
platform.
B
I
think
that
what's
interesting
is
what
can
you
do
with
this
right
now?
You
have
a
platform.
How
can
you
extend
it?
How
can
you
make
it
more
interesting
and
customized
to
your
own
use
case,
so
I
think
that
will
be
right
now,
probably
what
we
as
a
ecosystem.
All
of
us
is
going
to
do
right,
try
to
push
the
boundaries
and
which
is
pretty
exciting,
so.
E
William,
so
I
think
there's
a
couple
of
things
you
know,
along
with
the
boring
that
we
did
it
just
referred
to.
It
is
also
kind
of
the
platformization
right
that
service
meshes
will
become
a
little
bit
less
about
the
features
that
they
ship
and
more
about
how
easy
it
is
to
enable
that
last
mile
of
integration
that
you
know,
customers
need,
you
know,
that's
a
transformation
that
takes
time
as
it
will
take
as
long
as
it
took
to
build
service
meshes,
I
think.
Actually,
so
that's
one
trend.
E
The
other
trend,
I
think
you
see,
is
the
platforms
on
which
people
are
deploying
service
meshes
are
starting
to
now
incorporate
service
mesh
features
into
those
platforms
themselves
right.
So
there's
the
there's,
the
bottom
up-
market
validation
right.
You
know
you
see
some
of
that,
even
in
kubernetes
right
where
kubernetes
has
like
multi-cluster
services
now
right,
there's
that
value
proposition
is
starting
to
kind
of
sink
down
into
the
infrastructure,
which
just
makes
it
even
more
boring,
which,
in
my
opinion,
is
just
good.
F
You
know,
even
at
this
conference
we
have,
you
know,
end
users,
talking
about
using
linker
d
for
scheduling,
coven
19
tests
for
their
students,
you
know
or
for
doing,
rapid
experimentation
at
these
big
financial
institutions
or
for
doing
chaos,
engineering
or
adding
fips
140
compliance
and,
like
it's
just
it's
stuff
that
I
never
imagined
lingerie
would
be
used
for
and
so
that
you
know
feels
awesome.
You
know
we're
up
for
cncf.
F
Graduation,
there's
like
a
whole
bunch
of
cool
stuff
going
on,
but
the
thing
that
we
keep
coming
back
to,
I
think
maybe
to
louie's
point-
is
that,
ultimately
you
know
service
mesh
is
going
to
kind
of
be
absorbed.
You
know.
Maybe
this
is
what
become
boring
means
it's
going
to
just
be.
You
know,
part
of
the
ecosystem,
whether
we
call
it
a
special
name
or
not,
and
so
the
things
that
are
exciting.
F
You
know,
especially
as
we
think,
towards
the
future,
or
what
can
we
build
on
top
of
this,
because
we
know
that
building
a
big
cloud
native
application,
you
know,
subject
to
all
the
demands
that
we
place
on
software
today
is
a
hard
thing
to
do,
and
service
mesh
can
solve
one.
You
know
critical
part
of
that,
there's
a
lot
more.
That
has
to
be
done.
So
to
me,
that's
the
that's
the
kind
of
most
exciting
bit
is
you
know?
Where
do
we
go
from
here?
What
are
we
building
on
top
of
the
service
mesh.
A
F
Us
actually,
it
is
going
to
sound,
pretty
boring
because
you
know,
with
the
kind
of
concrete
wrote
an
eye
for
linkeries,
largely
around
policy
features.
So
over
the
next
couple
of
releases
you
know.
Well,
I
should
say
the
releases
leading
up
to
the
most
recent
one
2.10
have
been
heavily
focused
on
mtls
and
getting
identity.
F
You
know
wired
all
the
way
through
and
then
that's
all
that
has
been
in
service
of
setting
us
up
to
do
policy
and
and
tackle
some
of
the
like
difficult
challenges
that
we
know
that
people
have,
especially
in
multi-tenant
environments,
so
that
is
kind
of
like
the
concrete
answer
I
think
more
generally.
What's
next
for
linkery
is
we
want
to
make
it?
We
have
a
sense
as
a
project
that
you
know
it
has
to
be
this
platform
on
top
of
which
people
build
things.
F
So
we
recently
introduced
this
idea
of
extensions,
which
are
very,
very
easy
ways
of
plugging
into
linker
d.
We've
already,
you
know,
got
some
interesting
extensions
built
on
top
of
that
and
to
me
I
think
that
solves
kind
of
lingerie's,
core
vision
here,
which
is
we
want
the
service
mesh
itself
to
be
really
small
and
tightly
contained,
but
we
want
people
to
build
on
top
of
it
and
you
know
have
kind
of
a
modular
approach.
D
So
kuma
comes
out
of
the
work
and
the
efforts
that
cong
is
doing
with
our
enterprise
customers.
So
it's
the
fruit
of
that
work
and
you
know
service
mesh.
It
is
an
important
piece
of
the
broader
connectivity
puzzle
of
how
enterprise
architects
are
going
to
be
providing
connectivity
to
their
application
teams
and
when
we
built
cuba,
we
started
with
that
starting
point.
D
D
C
Yeah,
I
mean
so
predominantly,
I
suppose
operational
aspect.
Making
it
easier
to
operate
is
is
one
of
the
key
things
we're
going
to
continue
to
with
hashicorp
cloud
into
different
sort
of
clouds.
So
you'll
you'll
have
managed
console
in
in
across
more
of
the
cloud
vendors
in
the
coming
coming
year,
the
the
kind
of
the
operational
aspect
of
configuring
multi-cluster
capabilities,
or
for
connecting
sort
of
a
kubernetes
workload
of
virtual
machine.
C
The
operational
elements
of
that
is
going
to
be
simpler,
easier
to
kind
of
to
manage
the
the
sort
of
security
and
the
actual
elements
of
configuration,
and
predominantly
it's
around
the
sort
of
the
kubernetes
story
as
well
and
delivering
a
really
great
experience
to
a
kubernetes
practitioner.
So
you
know
treating
things
like
the
the
sort
of
it
should
feel
native
that
you're
you're
just
using
an
extension
of
kubernetes
and
not
a
sort
of
a
different
product.
Those
are
those
are
some
of
the
sort
of
the
goals
that
we.
E
You
know,
probably
with
a
focus
on
compliance
and
security
things,
and
with
my
google
hat
on
right,
it's
it's.
You
know
enabling
how
google's
customers
to
you
know
easily
adopt
and
absorb
service
mesh.
You
know
we
recently
launched
a
fully
managed
istio
based
solution
for
customers,
so
they
they
don't
manage
the
control
plane
aspects
of
istu
anymore.
We
do
that
for
them
and
yeah
that's
aligned
with
the
goals
around
day
two
operations
as
well
right
just
to
try
and
lighten
the
load
for
people
as
much
as
we
can
so
yeah
and.
B
Of
course
yeah,
so
I
mean
we
I'm
a
little
bit
different
because
each
of
the
people
who's
talking
here
is
basically
very
associated
to
one
project
and
you
read
solo,
we're
working
mainly
with
seo
today,
but
we
started
our
journey
a
little
bit
different.
We
started
basically
with
envoy.
That
was
the
thing
that
we
based
on
and
therefore
the
first
thing
that
we
built
was
api
gateway.
The
second
thing,
and
basically
we
built
the
building
platform
right,
the
building
blocks
to
create
those
this
platform.
B
So
basically
what
what
we
we
have
is
basically
hey
is
an
api
gateway
that
build
on
top
of
android
sec
and
now
is
going
to
shift
on
top
of
sto.
The
second
thing
that
we
have
is
glue
mesh
is
basically
helping
to
manage
and
basically
focus
on
the
data
operation,
as
well
as
very
big
focus
on
multi-cluster
and
basically
managing
a
lot
of
instances
of
seo,
and
you
know,
fall
over
between
them
and
so
on.
Then.
The
third
thing
that
we're
focusing
about
is
extending
the
mesh
with
web
assembly.
B
So
this
is
something
that
we
worked
very
very
hard
and
brought
web
assembly
hub
to
the
community
and
to
our
product
and
the
last
one
was
developer
portal,
which
is
basically
you
know
the
next.
In
my
opinion,
you
know,
you
know,
make
sense
approach
to
basically
manage
all
of
this
kind
of
like
bring
it
to
the
developer,
be
able
to
expose
all
the
api
that's
running.
B
So
this
is
the
building
block
that
we
have,
and
I
think
that
now,
when
we
have
this
platform
right,
that
it's
all
kind
of
like
working
specifically
on
sto
and
envoy,
and
we
have
the
knowledge
of
doing
sp
on
and
why
again,
we
are
pushing
the
boundaries.
So
the
next
thing
that
we're
going
to
do
is
working
on
building
on
top
of
it
and
we're
going
to
have
some
very
crazy
and
awesome
announcement
very
soon.
So
yeah
stay
tuned.