►
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.
CNCF - SIG Network Intro and Deep Dive - Lee Calcote, Layer5 & Ken Owens, Fiserv
“It’s the network!” is the cry of every system administrator, every developer. 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 Network SIG.
A
B
A
Yeah
yeah,
I
keep
interrupting
ken,
but
he's
he's
used
to
that
apology.
So
we
are
here
to
take
you
all
through
some
of
the
initiatives
within
the
special
interest
group.
Sig
network
sig
network
has
a
couple
of
working
groups,
one
of
which
will
be
our
focus
today
and
that
one
is
the
service
mesh
working
group,
hot
topic,
and
so
we'll
do
a
bit
of
an
intro
and
a
deep
dive
and
we'll
see.
If,
if
ken
will
take
us
through
what
is
sig
network.
B
Yeah
thanks
thanks
lee,
so
you
know
our
mission
statement
and
sig
network
is,
with
an
ever
steady
eye
to
the
needs
of
workloads
and
developers
who
create
them
and
operators
who
run
them.
Sig
network's
mission
is
to
enable
widespread
and
successful
development
deployment
and
operation
of
resilient
and
intelligent
network
systems
and
cloud-native
environments.
B
It's
really
important
and
in
our
minds
in
our
view
of
this
sig,
is
that
we
want
to
represent.
You
know
the
network
develop
the
network
guys,
but
also
the
developers,
both
in
the
application
teams
in
the
business
teams
and
also
in
the
network,
and
you
know,
software-defined
networking
areas
and
so
we're
we're
really
looking
at
a
broad
scope
within
the
sig.
B
B
We
want
to
assist
and
attract
projects
as
we
go
within
a
few
minutes.
We
brought
in
really
interesting
projects
and
we're
really
excited
about
how
how
much
we've
grown
in
the
last
couple
of
years-
and
we
also
want
to
you-
know
basically
have
as
as
part
of
the
cncf
charter.
We
want
to
be
impartial
of
the
different
projects.
B
B
So
just
a
little
bit
about
what
we've
we've
done
over
the
last
several
years.
As
of
you
know,
kubecon
north
america,
in
2019,
you
know
we
had
you
know
you
know
kind
of
the
beginning
projects
right.
Cni
was
really
the
first
thing
that
we
worked
on
as
as
a
group
before
we
were
a
sig
which
is
kind
of
a
networking
work
group
at
the
time
and
and
and
we
probably
had
some
fun
memories
of
the
the
work
group
times
together,
the
the
six
of
us
right.
B
You
know,
but
you
know,
since
cni
we've
worked
with
core
dns
envoy,
gprc,
lincoln
d,
nats
friends
of
cisco
brought
in
you
know
some
network
service
mesh
discussions
that
open
source
project
they
have
going
on
that
then
really
helped
kind
of
kick
us
off
in
the
beginning
of
2020
at
kubecon.
Europe,
with
you
know
some
additional
projects
like
gni,
genie
and
contour,
and
you
know
the
service
mesh
interface
you
hear
more
about
today,
and
then
we
ended
the
year.
B
You
know
working
with
chaos,
smash
and
open
service
mesh,
and
you
know
today
we're
excited
that
we're.
You
know
looking
at
an
ambassador
project
in
mastery
ingress,
we're
looking
at
you
know,
kgb
we're
working
with
mastery
and
with
service
mesh
performance
which
we'll
get
into
more
a
little
bit
later
in
the
presentation
and
on
the
horizon.
We
have
a
couple
of
things
with
submarine.
B
Submariner
is
sort
of
the
main
thing
we
want
to
look
at
on
the
horizon,
so
we
have
a
couple
working
groups
that
you
kind
of
you
know
lee
mentioned
earlier,
the
biggest
one
that
we're
working
on
right
now
is
the
service
mesh
working
group,
but
we
also
have
a
very
interesting
working
group.
The
universal
data
plane
api.
B
Both
of
these
working
groups
are
active
and
you
know
we
invite
your
your
participation
and
you'll
hear
more
about
that.
As
we
go
through
the
presentation
today,
we
do
have
a
couple
white
papers
out
there
and
we
have
several
presentations.
But
the
main
one
wanted
to
point
you
to
is
moving
beyond
ectp
surveying
the
state
of
latest
seven
protocols
in
the
cloud-native
ecosystem,
and
so
there's
you
know
a
lot
to
get
involved
in
and
a
lot
to
do.
B
And
hopefully
what
you
see
today
as
we
go
into
the
deep
dive-
and
I
turn
this
over
to
lee
you'll-
see
that
there's
a
lot
of
interesting
topics,
a
lot
of
interesting
conversations
we
want
to
have
and
in
the
community-
and
you
know
that
you
want
to
get
engaged
and
we'll
make
sure
you
know
how
to
do
that.
So
with
that
I'll
turn
it
over
to
lee.
A
You
know
ken
actually
that
the
last
presentation
that
you
were
just
highlighting
like
while
we
have
you
know,
while
the
the
group
is
large
and
networking
is,
is
vast
that
that
presentation
might
be
familiar
to
some
as
it
was
subsequently
presented
as
a
keynote
at
last
last
cubecon
as
well.
So
I
was
just
recalling
that
you
know,
speaking
of
recalling
things
like
late
breaking
news
earlier,
just
a
few
hours
earlier
today
was
that
ambassador,
the
emissary
ingress.
A
Can
we
that
project
has
been
under
review
in
the
sig
for
maybe
longer
than
maybe?
Let's
not,
let's
not
talk
about
how
long
it's
been
there
a
while
it's
been
under
diligence
and
underwent
a
name
change,
but
it's
it's
in
it's
so
yeah.
You
know
congrats
to
that.
That
team,
so,
like
ken
was
saying
the
service
mesh
working
group
has
a
few
different
initiatives
going
on
the
initiatives
are
interrelated.
A
They
are
well.
The
focus
is
on
service
matches.
There's
a
lot
that
that
a
service
mesh
provides
a
lot
of
ways
that
the
that
you
can
use
them
and
that's
part
of
the
focus
of
the
the
group
is
to
identify
patterns
in
the
way
in
which
users
are
using
service
meshes
trying
to
to
curate
a
collection
of
those
at
the
same
time
we're
also
taking
advantage
of
the
cncf's
labs
there.
A
It's
not
an
infrequent
question
that
people
will
ask,
is
you
know
inquire
about
the
overhead
of
a
mesh
or
the
some
of
its
performance
characteristics
and,
and
they
you
know,
I
don't
know
that
you
know.
One
of
the
initiatives
that's
within
the
the
group
here
is
well
is
to
leverage
the
labs
to
help
answer
some
of
those
questions.
Some
of
those
those
answers
are
point
in
time.
Answers
about
a
particular
mesh
or
a
particular
type
of
workload.
A
One
of
the
the
collection
of
participants
recently
have
been
from
from
intel,
and
you
know
historically
that
that
organization
has
a
long-standing
focus
on
performance
and
so
they're
bringing
some
of
their
their
skills
to
practice
here,
which
is
nice,
so,
hopefully
we'll
see.
As
a
matter
of
fact,
I
think
they
have
a
talk
as
well
at
kubecon
and
we'll
see
some
of
the
we'll
have
to
point
out
where
you
can
find
some
of
those
results.
A
A
Those
are
also
there's
also
tooling,
that's
being
worked
on
in
context
of
the
service
mesh
working
group.
We're
going
to
talk
about
some
of
the
tooling,
but
some
of
that
tooling
helps
people
run
those
patterns.
So,
if
you're,
if
you're
reading,
through
the
pattern
and
saying
hey,
hey,
that's
of
interest
and
you're
wanting
to
use
a
tool
to
test
it
out,
we'll
talk
we'll
talk
about
that
tool
here
in
just
a
bit.
A
The
part
of
what
makes
the
working
group
fairly
interesting
is
that
there's
a
number
of
projects,
the
ones
that
ken
had
listed
off
that
are
well,
some
of
them
are
service
meshes
themselves.
Some
of
them
are
emergent
standards
or
specifications
that
help
all
of
us
interface
with
service
meshes
in
a
in
a
standard
way,
and
so
the
first
specification
here
is
service.
Mesh
interfaces
smi.
A
Some
of
that
is
just
to
be
able
to
articulate
that
performance
in
a
concise
way
to
do
it
in
a
uniform
way
in
which
each
of
the
service
mesh
projects
are
are
beginning
to
engage
with
the
specification
and-
and
it's
our
hope-
that
through
well
through
the
assistance
of
the
service
mesh
working
group,
that
each
of
the
service
meshes
will
be
able
to
report
on
their
performance
with
each
release
under
a
set
of
different
scenarios
and
use
the
same
standard
to
do
that.
So
there's
there's
a
little
bit
in
there.
A
The
this
third
specification
is
well
also
just
looking
at
this
like
and
reflecting
over
the
last.
Like
two
weeks
now,
there's
been,
I
guess.
Let
me
first
explain
hamlet
and
explain
some
some
recent
news,
and
so
hamlet
is
generated
and
put
forth
largely
by
on
vmware,
but
in
collaboration
with
hashicorp
and
google
and
begins
to
define
really
like
to
put
it
in
my
own.
A
That,
inevitably
you're
going
to
want
those
workloads
to
be
able
to
interact
between
the
different
service
measures,
so
you're
going
to
want
to
be
able
to
federate
them,
and
so
that's
the
the
crux
of
the
focus
of
of
this
specification
here
recently,
there's
been
well
there's
about
three
areas
that
that
multi-cluster
kind
of
federation
discussions
are
happening.
There's
some
of
that
going
on
within
the
kubernetes.
A
Well,
I
forget
the
name
of
the
sig,
but
there's
multi-cluster
being
discussed
there
as
a
new
api,
a
little
bit
of
that
being
discussed
in
service
mesh
interface
and
a
little
bit
here
in
hamlet
and
and
ken
will.
You
know
quickly
tell
you
that
that's
a
great
example
of
what
this
sig
network
is
about
and
yeah
it's
from
this
vantage
point
that
we
would
be
able
to
identify
some
of
those.
A
You
know.
I
don't
know
that
duplicities
is
the
right,
the
correct
word
exactly,
but
to
be
able
to
make
sure
that
individual
efforts
are
at
least
aware
of
one
another
and
can
and
can
collaborate
and,
and
so
so,
if
you're,
so,
if
you're
listening
right
now,
this
is
a
good
place
to
come
and
work.
Those
through.
A
One
of
the
so
based
on
the
fact
that
there
are
many
meshes
out
there
and
a
number,
a
number
of
them
in
the
cncf
that
and
and
whether
they're
in
the
cncf
or
not.
There
is
those
that
have
chosen
to
implement
service
mesh
interface
and
just
like
any
specification,
you
need
some
tooling
to
be
able
to
verify
the
compliance
of
that
spec
and
so,
in
this
case,
you'll
need
tooling
to
oh.
A
That
works
with
each
of
those
eight
different
service
meshes
that
implement
smi
and
for
the
it
to
flex
each
of
the
four
specifications
that
smi
currently
has
there's
a
fifth
that's
being
discussed
now,
and
so,
if
you're
familiar
with
sona
boy
of
the
well,
I
shouldn't
say
of
the
kubernetes
project
but
sona
boy
to
what
sonoboy
is
to
kubernetes.
This
smi
conformance
initiative
is
that
to
smi,
and
so
there's
some
early
reports.
Actually
this
will
be
the
first
time.
A
I
think
that
these
reports
are
being
shown
reports
of
it's
about.
Is
it
about
five
yeah
about
five
different
service
meshes
and
their
where
their
their
compliance
falls?
With
respect
to
these
different
right
now,
it's
just
three
different
of
the
smi
specs
we're
seeing
a
lot
of
red
and
there's
good
reason
for
that.
That's
because
the
smi
spec,
a
new
version
was
just
released
about
a
week
ago,
and
so
there
was
a
breaking
change.
A
So
so
we
it's
our
hope
to
get
a
few
more
of
the
implementations
up
here,
get
get
them
participating
in
the
tests
even
more
directly.
The
tool
that's
being
used
is
is
measuring,
and
it
is
one
of
the
the
tools
that
that
kenan
mentioned
a
moment
ago.
It's
up
for
up
for
adoption
into
the
cncf
it
can.
If
you
oblige
me,
if
you
were
to
click
on
that
message,
logo
there
is
mescheri
implements
the
these
smi
conformance
tests.
A
It
also
implements
the
service
mesh
service,
mesh
performance
specification
and
it
kind
of
does
so
across
any
number
of
service
meshes
and
so
on
that
service
mesh
performance
specification,
though,
on
on
the
next
slide,
we'll
describe
that
a
little
bit
more.
This
specification
is
also
up
for
review
and
donation
to
the
cncf.
A
I
had
articulated
it
earlier
as
a
way
of
a
standard
way
of
capturing
and
describing
your
infrastructure
characterizing
your
service
mesh
performance.
It
does
that
the
spec
directly
does
that
it
also
facilitates
some
other
interesting
things.
It
facilitates
maybe
benchmarking
of
a
given
mesh
over
time
and
how
well
it's
doing
from
release
to
release.
A
Apples
to
oranges,
to
the
extent
that
that's
those
are
comparable.
It
also
facilitates
well
potentially
a
new
performance
index.
Maybe
a
new,
concise
way
of
articulating
the
you
know
how
well
how
fast
or
efficient
your
service
mesh
is
running,
and
I
think
it's
this
next
slide
that
talks
about
a
mesh
mark
which
is
an
emergent.
Well,
it's
an
emergent
ruler
or
yardstick
for
it's.
A
A
I
don't
know
that
that's
the
intention
for
the
maintainers
that
are
working
on
get
nighthawk,
but
it
becomes
this.
This
particular
initiative
becomes
necessary
to
the
extent
that
well,
that
nighthawk
is
quite
a
capable
piece
of
software
and,
if
you're
saying
night,
what
then
I'll
quickly
tell
you
that
that
nighthawk
is
well
more
or
less
a
subproject
of
envoy,
and
maybe
at
some,
maybe
at
some
point
it
won't
be
a
sub
project,
it'll
be.
But
anyway
it's
it's
a
performance
characteristic
tool.
A
This
project
get
nighthawk
is
bringing
together
is
making
it
easier
for
people
to
get
to
get
nighthawk
into
the
hands
of
of
the
masses.
So
to
speak,
the
integration
with
meshary
and
nighthawk
will
well.
It
will
advance
that
even
more,
but
it
will
also
hopefully
advance
a
little
bit
of
the
state
of
the
art
around
some
of
the
the
research
that's
being
done
within
the
working
group.
We've
got
there's
a
couple
of
universities
that
have
participated
in
these
discussions.
A
B
Yeah
thanks
lee,
that
was
a
awesome
job
of
describing
so
much
of
the
the
great
efforts
we
have
going
on
in
the
in
the
pride
and
the
sick.
So
thank
you
for
that.
We
we
kind
of
wanted
to
end
the
presentation
asking
for
engagement
and
ensuring
that
you,
you
know,
were
asked
to
be
engaged
that
we
always
hear
that
you
know
if,
if
we
just
have
asked
for
them
to
you
know
people
for
they
engage
with
us.
We'd
have
more
engagement,
so
so
we're
going
to
have
a
call
for
engagement.
You
know
golfer
participation.
B
We
have
meetings
twice
a
month,
they're
on
the
first
and
third
thursdays
of
every
month
at
11
a.m.
Pacific
time
we
have
meeting
minutes
that
we
we
keep
track
of
you're
welcome
to
kind
of
catch
up
on
some
of
the
things
that
we
we've
talked
about
and
everything
that
lee
mentioned.
There's
you
know
links
in
this
deck
and
there's
also
links
in
the
media
minutes
to
some
of
the
the
projects
directly.
B
We
definitely
would
love
you
to
connect
with
us.
On
slack.
We
have
a
you
know.
Sig
network
is
a
slack
channel
and
if
you
you
know,
couldn't
want
to
join
our
seg
network,
we
our
signa
service,
mesh
work
group.
We
have
you
know
melanie
misabella
list.cncf.io,
and
with
that
I
you
know.
I
thank
you
very
much
for
your
time
and
and
thank
you
lee
for
for
co-presenting
with
me.
I
think
this
has
been
a
really
useful
and
helpful.
A
That's
a
lot
while,
while
ken
and
I
are
sitting
here
fielding
questions
in
chat,
I've
got
a
question
ken
you
were
just
saying:
there's
a
call
for
participation.
People
can
jump
into
the
meeting
minutes
jump
into
the
meeting.
Question
do
do
those
that
show
up.
Did
they
need
to
belong
to
a
cncf
member
company
or
do
they
need
to
be
a
platinum
sponsor,
as
you
know
like?