►
From YouTube: CNCF TAG Network and Service Mesh Working Group - Lee Calcote, Ed Warnicke & Ken Owens
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.
CNCF TAG 网络和服务网格工作组 | CNCF TAG Network and Service Mesh Working Group - Lee Calcote, Layer5; Ed Warnicke, Cisco; Ken Owens, Fiserv
随着基于微服务的分布式系统的日益盛行，确实如此：网络作为一门学科，在云原生部署的高效运行中从未如此关键。包括负载均衡、可观察性、认证、授权、策略、速率限制、QoS、网状网络、传统基础设施桥接等在内的网络基元现在正得到整个行业的大量开发和投资，并且是CNCF TAG网络和服务网状工作组的重点关注对象。聆听我们的简介并深入了解工作组内正在管理的服务网状项目。 With the increased prevalence of microservice-based distributed systems, it’s true: networking as a discipline has never been more critical in the efficient operation of cloud native deployments. Networking primitives, including load balancing, observability, authentication, authorization, policy, rate limiting, QoS, mesh networks, legacy infrastructure bridging, and so on are now receiving substantial development and investment throughout the industry and are the subject of focus of the CNCF TAG Network and Service Mesh Working Group.
Join us for an introduction and deep-dive into the service mesh projects being stewarded within the working group.
A
A
B
B
Yeah
so,
as
you
know,
cloud
native
has
been
a
huge
change
in
the
industry
and
a
lot
of
what
we're
trying
to
do
within
the
sig
network
group
is
to
just
make
sure
that
you
know,
as
we
look
at
moving
to
to
the
cloud,
that
some
of
the
components
that
make
up
the
core
of
how
workloads
move
the
the
way
they
communicate.
The
way
they
get.
B
B
A
There's
a
lot
of
interesting
projects
that
ken
and
I
and
and
ed
as
well,
have
had
the
pleasure
of
reviewing
providing
commentary
on
kind
of
you
know,
assessing
and
helping
steward
some
of
these
projects
through
their
well
potential,
either
into
the
cncf
and
kind
of
through
the
these
various
stages
that
the
projects
go
through
and
so
ken.
I
wonder
if
you
might
educate
us
a
bit
on
part
of
this
process,
and
you
know
why
it
is
that
we
have
so.
You
know
as
many
projects
as
we
do.
B
Yeah
yeah,
definitely
so
I
think
it
I
think
it's
it
can
be
overwhelming
when
you
first
think
of
of
an
open
source
community,
and
how
do
you
get
involved
right,
how
you
get
engaged
and
at
the
cncf
it's
been.
You
know,
part
of
our
mantra
from
the
very
beginning
to
be
very
inclusive
of
different
projects
and
different
ideas.
We
had
this
phrase
where
we,
since
the
beginning
that
we
were
not
going
to
be
king
makers
right.
B
Our
goal
was
not
to
kind
of
go
out
and
pick
and
choose
what
technologies
mean
cloud
native
right,
and
so,
as
we
kind
of
went
down
this
path,
we
thought
it
would
be
good
to
kind
of
have
the
ability
to
have.
You
know
sandbox
capabilities
right.
Let's,
let's
have
a
project
that
it.
They
think
it
is
a
you
know
a
cncf
sort
of
project
they
like
to
understand
more
about
the
cncf.
B
So
let
me
mention
we
would
meet
with
you
usually
present,
especially
kind
of
like
the
presentation
to
to
a
tag
meeting,
and
the
presentation
is
really
like.
You'd
expect
any
sort
of
a
product
pitch
right,
you're
kind
of
explaining
what
it
does.
Why
you
designed
it
the
way
you
did
you're,
looking
we're
looking
what
lee
and
I
are
looking
for.
Mostly
is
you
know
what
is
the
value
that
this
is
going
to
bring
to
the
community
and
what
are
the
problems
that
you're
trying
to
solve
in
the
community
right?
B
Those
are
really
the
two
big
things
we're
looking
for.
If
there
are
other
technologies
that
are
similar,
we'll
ask
questions
about
those
technologies.
How
do
you
differ?
You
know,
do
you
differ
and-
and
I
can
mention
you-
don't
have
to
differ,
but
we
do
want
to
kind
of
understand
the
space
make
sure
you
understand
the
space
that
you're
in
how
you
compare
with
other
projects
in
the
space.
B
As
you
can
see
on
this
list,
we
have
quite
a
few
projects
that
do
similar
things
to
each
other,
and
a
lot
of
names
are
the
same
like
service
mesh,
and
you
know
open
service,
mesh
and
service
mesh
interface,
and
you
know
you
know,
service
mesh
performance.
A
lot
of
you
know
mesh
names
out
there
and
a
lot
of
acronyms
that
you
may
look
at
here
and
say.
Well,
you
know
what
does
that?
What
does
bfe
mean?
B
I
thought
that
was
you
know
like
best
friend
type
of
thing
right,
but
no,
it's
not
so
you
know
it's
kind
of
a
lot
of
a
lot
of
you
know
interesting
names
and
interesting
activities
that
really
go
in
to
these
projects,
but
answer
your
question
specifically.
You
can
start
off
in
in
you
know
the
sandbox
area
and
from
there
you
might
move
up
to
the
incubation
area
right
where
you're
kind
of
you've
proven
that
you
have
some
of
the
basic
interest
in
the
space.
B
You
have
some
adoption,
that's
kind
of
how
you
get
from
sandbox
incubation
is
you
have
a
little
bit
of
adoption
and
then
to
graduate
you
have
to
have
you
know
a
little
bit
more
abduction
doc?
I
can't
say
window
adoption,
sorry
and
you
have
to
have
you
know
at
least
two
or
three
other
contributors
from
outside
of
your
group.
Your
main
your
core
group
right.
It's
we!
B
We
don't
want
to
sort
of
support
a
project
in
the
cncf
that
is
only
driven
from
one
single
source
right
that
no
one
else
outside
of
your
group
has
seen
interest
in.
So
you
know
if
you're
a
company
a-
and
you
only
have
company
a
working
on
the
project
and
no
one
else
in
the
industry
sees
value
in
helping
you
with
your
project.
B
Then
it's
really
a
company,
a
project,
not
an
open
source
community
project,
and
so
that's
kind
of
the
key.
The
key
goal
is
to
make
sure
that
it
moves
out
and
the
best
advice
I
can
give
and
I'll
ask
the
leader
give
his
best
advice
next,
but
the
best
advice
I
can
give
to
you
is,
you
know,
go
into
this
with
the
end
in
mind
right.
So,
if
you
want
to
be
a
cncf
project,
that
means
you
want
to
be
open
source.
You
want
to
have
contributions
from
the
industry.
B
You
want
to
solve
values
solve
problems
that
the
industry
sees
is
valuable
to
solve,
and
you
want
to
do
it
with
an
open
license
and
and
open.
You
know
governance
within
you
within
your
github
project,
and
so
you
know
go
into
it
from
the
beginning
with
that
mindset
and
it'll
be
a
lot
easier
as
you
move
through
these
different
phases
within
the
different
cycles
of
the
cncf
to
graduate
it'll,
make
it
a
lot
easier
on
you.
A
Yeah,
you
know
to
add
to
that
to
ken's
point:
it's
you
know
creating
and
stewarding.
Any
one
of
these
projects
is
is
a
significant
undertaking.
It
not
only
does
it
take.
You
know
multiple
people,
but
to
ken's
point
like
a
healthy
project
is
one
that
has
their
various
interests
in
mind
or
there's,
there's
folks
that
get
their
paychecks
from
various
places
and
that,
in
part,
it
helps
with
just
kind
of
the
democracy
or
the
the
meritocracy,
maybe
that
that
occurs
within
the
a
project's
community.
A
If
you
will
some
of
the
initiatives
that
ken
and
I
will
speak
to
that
go
on
inside
the
service,
mesh
working
group
are
like
they're,
really,
you
know
they're
cross-cutting,
they
really
need
a
well.
What's
the
right,
you
know
a
non-part,
a
bipartisan
or
a
non-partisan
perspective,
so
it
isn't
about
it's
about
the
technology
and
kind
of
finding.
You
know
arriving
at
the
best
answer.
You
know
you're,
irrespective
of
other
political
interests
or
other
interests,
it's
really
hard
to
to
avoid
some
of
those.
A
B
Look
at
in
addition
to
shepherding
and
stewarding
and
working
closely
with
projects
we
feel
like.
We
need
to
kind
of
get
more
information
out
and
that's
part
of
why
we
present
at
cube
kind
of
kind
of
get
more
information
out,
but
we
also
look
at
creating
working
groups.
The
service
mesh
working
group
is
is
a
very
important,
a
part
of
what
what
lia-
and
I
both
are
very
you
know
interested
in
supporting.
B
We
have
quite
a
bit
of
information
about
that
below
also
the
universal
data
plane
api.
We
also
are
doing
white
papers,
and
this
is
what
was
kind
of
an
interesting,
because
you
kind
of
have
your
technical
white
papers.
So
that's
sort
of
the
you
know
you
want
to
kind
of
get
a
you
know,
publish
something
around.
B
Back
when
I
was
a
kid,
my
beard
and-
and
I
I
kind
of
mentioned
to
my
my
advisor-
who
I
was
working
with
on
the
paper
and
for
this
article
publication-
that
that
I'm
involved
in
this
you
know
the
cloud-native
computing
foundation
that
you
know
I'm
working
with
lee
and-
and
we
have
some
interesting
work
around
a
newer
type
of
networking
in
the
cloud
space
called
service
meshes
and
we
thought
it
would
be.
I
thought
it'd
be
interesting
to
have
a
paper
on
you
know.
B
You
know,
communication
and
networking
articles
that
they
like
to
publish,
and
so
my
my
next
goal
with
lee
is
to
kind
of
work
with
the
ieee
communication
society,
which
I'm
a
member
of
and
and
try
to
get
some
of
our
more
advanced,
more
technical
publications
into
that
those
are
usually
very
algorithm.
Driven
and
lots
of
you
know
equations,
and
so
we're
going
to
get.
B
You
know
as
technical
as
we
can
with
our
service
mesh
algorithm
work
that
we're
doing,
but
it
does
fit
well
and
and
the
future
paper
we're
working
on
right
now
is
techniques
of
objective
service,
mesh,
optimization
and
it
it
kind
of
goes
with.
You
know
a
good
story
that
I'll
let
lee
tell
you
about
how
we
kind
of
got
to
you
know
why
we
look
at
performances.
B
A
Well,
as
people
adopt
more
and
more
cloud
native
infrastructure
as
they
they
do
so
with
this
kind
of
next
generation
software-defined
networking
with
as
I
do
so
with
service
meshes,
there
are
well,
you
know,
there's
there's,
there's
a
lot
of
things
that
you
can
enable
in
a
mesh
there's
a
lot
of
things
that
a
mesh
brings
to
you
and
you
can
turn
on.
And
there
are.
A
You
know,
performance
considerations
around
that
if
you,
if
you
ask
for
the
service
mesh,
to
provide
a
lot
of
resiliency
to
your
micro
services
and
and
try
to
help
you
overcome
what
we
know
to
be
fallible
networks,
the
more
that
you're
asking
a
service
mesh
to
do.
Maybe
the
more
you're
asking
it
to
retry,
failed
services,
service
requests
between
your
services
or
maybe
you're,
asking
for
it
to
the
traffic
between
your
services
or
do
mutual
authentication
between
them
or
reroute
traffic
or
like
there's
like
there's
a
list.
A
Actually
we're
going
to
look
at
a
list
here
in
a
little
bit.
Well,
that
means
that,
as
an
operator
of
that
infrastructure
and
actually
as
an
owner
like
a
product
owner
or
a
service
owner
of
the
workloads
that
are
running
on
that
infrastructure,
you're
concerned
with
you
have
similar
and
overlapping
concerns,
you
have
from
an
infrastructure-centric
perspective.
You
want
to
know
you
know,
hey
am
I
am
I
doing
it
not
only
am
I
doing
it
right,
but
maybe
am
I
doing
it
well
like?
A
Is
this
a
well-oiled
machine
and
and
how
does
that
compare
to
how
others
are
doing
it?
Part
of
answering
that
question
of
like
excuse
me
am
I
doing
it.
Well
is
yeah,
there's
there's
comparing
to
others,
but
there's
also
just
it's.
It's
a
continual
measurement
that
you'd
want
to
do
and
kind
of,
compare
to
yourself
and
have
a
relative
benchmark
onto
your
own
standards
that
run
to
your
own
historical
ability
onto
your
own
custom,
workloads
and
custom
environment.
B
This
technique
really
helps
you
fine-tune
that
we
get
into
in
a
few
minutes
fine-tune
in
a
I
won't
say
like
immediately,
but
it's
much
quicker
than
the
traditional
way
of
you
know,
trying
to
tune
knobs
and
tweak
knobs
over
time
and
test
and
test
and
test
it.
It
kind
of
does
that
testing
for
you
over
many
iterations
as
quickly
as
you
want
it
to
right.
You
don't
want
to
obviously
break
yourself,
but
you
want
to
kind
of
give
it
some
parameters
and
say
within
these
parameters,
go
figure
out.
A
A
There's
been
an
emergence
of
specifications
and
some
emergent
standards
that
focus
on
interoperability
so
and
actually,
as
it
turns
out
that
there
are
a
couple
listed
here
in
a
potential
third,
both
of
these
two
service
mesh
interface
and
service
mesh
performance.
Are
we
have
the
fortune
of
these
projects,
calling
the
tag
network,
their
their
home
group,
their
home
tag?
The
smi
ends
up
focusing
on
interoperability
from
a
functional
perspective
of
the
various
features
of
a
service
mesh.
A
Can
you
functionally
address
those
features
and
configure
those
features
in
a
universal
way
in
a
com
using
a
common
interface,
a
common
set
of
apis?
That's
that's!
That's
really!
The
focus
of
smi
service
mesh
interface,
if,
if
you're
kind
of
familiar
with
cni
container
network
interface,
there's
a
that's
a
good
analogy
to
draw
mentally
another
one
here
on
service,
mesh
performance
or
smp,
and
it's
it's
about
trying
to
make
it
both
uniform
and
succinct.
A
The
longer
that
the
discussions
around
this
project
have
gone
on
the
more
folks
get
involved
and
the
more
people
push
to
expand
that
that
their
focus
from
service
mesh
to
a
bit
more
of
cloud
native
performance,
and
so
in
order
for
the
project
to
do
that
successfully,
though
there
really,
frankly,
there
just
needs
to
be
more
more
of
you
involved
more
people
involved.
I.
B
Think
a
key,
a
key
component
to
this
is
you
know
lee
kind
of
mentioned
earlier
that
when,
when
you're
trying
to
fine-tune
some
of
your
latency-
or
you
know
some
of
the
authentication
mutual
authentication
aspects
right
as
you're
looking
at
all
these
different
knobs,
it
is
hard
to
sort
of
know.
Well,
what's
the
like,
what's
the
right
tune
right?
How
do
I
tune
it
correctly?
You
know,
and
when
you
have
a
standard
around
the
interface
conformance
and
and
service
mesh
performance,
things
that
you
know
other
you
know.
B
Other
groups
in
the
industry
have
said
these
are
things
that
matter.
These
are
performance
aspects
that
we
want
to
look
at
and
you
can
kind
of
go
back
to
that
spec
and
say
you
know
based
on
snp.
This
is
what
I
want
to
set
these
parameters.
These
are
these.
These
parameters
would
be
important
parameters
for
me
to
look
at
and
then
you
can
kind
of
fine
tune.
B
So
you
know,
I
know
60
seems
like
a
lot,
but
when
we
get
into
them
in
a
little
while
you
see
that
it's
really
classified
into
maybe
eight
or
nine
different
types
of
categories
right,
and
so
you
can
kind
of
put
yourself
into
that
category.
And
then
you
only
have
seven
or
eight
patterns
to
look
at
versus
60
patterns
to
look
at.
A
B
A
Not
only
is
this
initiative
about
cataloging
identifying
and
espousing
best
practices,
best
practices
of
these
patterns,
but
it's
been
also
about
I'm
codifying
those
best
practices
into
a
into
individual
patterns
that
can
be
taken
that
are
expressed
in
yaml
and
can
be
taken
and
realized
against.
Any
number
of
that
same
pattern
can
be
realized
on
a
on
an
istio
mesh
on
a
link.
A
B
B
To
get
the
you
know,
the
fraud
and
other
scores
done
right
and
you're
doing
all
that
at
the
same
time
as
quickly
as
you
can
in
milliseconds
right
and
it
something
like
nighthawk
has
done
a
great
job
of
helping
us
simulate
these
multiple
different
types
of
streams.
We
have
in
different
directions
and
how?
Well
you
know,
it's
helped
us
fine-tune
a
lot
of
little
aspects
along
the
way
that
you
wouldn't
have
thought
about
without
something
like
like
a
little
generator
in
there
to
help
you
find
it.
A
A
If
you
the
thing
that
you
were
just
saying
like
if,
if
each
of
these
microservices
are
secure
and
they
each
you
know
as
they
go
to
receive
a
request,
if
if
they
need
to
authenticate
that
request
in
a
particular
environment,
so
if
you've
got
50
50
microservices
that
each
one
receives
a
request,
they
go
back
to
kind
of
the
central
authentication
system
all
50
times.
I
did
like.
B
And
there's
also
like,
along
those
same
lines,
not
to
take
too
much
time,
but
another
interesting
use
case
that
nighthawk
helps
with
those
I
kind
of
call
them
those
like
big
events
right.
So
so,
if
you
have
a
huge,
you
know
something
big
going
on:
that's
going
to
drive
a
lot
of
traffic
to
your
your
site,
for
instance,
it
helps
you
with
those
sort
of
like
one-off
events
of
kind
of
looking
at.
B
You
know
if,
if
I'm
getting
a
ton
of
information
in
one
place,
how
do
I
optimize
for
that,
but
not
take
away
from
my
other?
You
know
I'm
still
getting
traffic
from
other
places,
so
I
don't
want
to
take
away
from
the
traffic
from
other
places.
But
how
do
I
make
sure
that
the
bulk
of
new
traffic
coming
in
or
the
amount
of
traffic
coming
in
right,
because
the
throughput
is
going
to
grow
way
up
for
this
one
site?
You
know,
but
the
latency
and
the
resiliency
have
to
still
be
low
right.
A
I
guess
is
gosh
there's
this
well,
there
are
these
concepts
in
the
world
of
networking
and
whether
it's
in
in
the
physical
days
or
the
initial
virtual
days,
or
maybe
these
these
these
meshy
days
and
there's
you,
I
think,
you're
talking
about
the
different
types
of
different
types
of
network
traffic
and
maybe
classifying
this
network
traffic
and
trying
to
provide
some
differentiation
around
how
these
are
handled
and
so
yeah.
What
is
what
there's
there's
a
term
for
some
of
this
volume.
B
A
B
A
Request,
like
you
know,
maybe
the
shopping,
cart
request
or
the
the
debit
card
request.
Maybe
it
should
be,
you
know,
guaranteed
to
get
to
its
recipient
and
and
what
happens
if
it
gets
bottlenecked
or
kind
of
choked
to
the
middle,
and
so
it's
been
very
nice
to
share
with
you
all
ken
and
I
might
be
in
the
chat
right
now,
I'm
not
sure
if,
if
if
either
the
two
of
us
will
be
up
that
early,
but
but
I
hope
so
so
we
will.