►
From YouTube: CNCF Network Service Mesh Meeting - 2019-08-13
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
B
Great,
if
we
can
get
someone
to
share
the
agenda
as
well,
that'd
be
good
and
with
that
I
will
go
ahead
and
get
started
so
welcome
to
the
network
service
mesh
called
so
we
we
have
recalls
that
we
generally
do.
We
have
the
NSM
dock,
which
is
currently
on
hiatus
until
allah
jeffrey
gets
back.
We
have
the
MSM
use
cases
which
the
next
meeting
will
be
on
August
13th
and
we
have
the
CNC
a
commuter
sorry
they
would
start
the
NSM
one
was
today
13
Wow,
I'll
ping.
B
B
So
we
have
a
few
major
events
coming
up.
We
have
ons
Europe,
which
will
be
in
Antwerp
where
we
have
for
accepted
to
talks
the
telecom
user
group
Meetup
and
a
CNC
a
testbed
tutorial.
We
also
have
the
open
source
event
coming
up
in
Lyon,
with
a
talk
accepted
by
Ivana
and
Rostov,
and
we
have
cube
con
plus
I
made
it
fun.
So
for
those
of
you
that
were
not
here
last
week
we
have
a
co-located
and
a
semi
event.
That's
an
assembler.
B
We
have
listed
the
call
for
proposals
and
a
pre-register.
Tweet
is
that's
posted
up,
and
so
we
also
should
be
having
a
few
talks
at
Q
Khan
as
well,
so
we'll
post
the
agenda
when
we
want
to
get
it
for
the
proposals
or
the
NSM
con.
The
submissions
will
close
one
month
from
now
on,
September
13th,
so
get
all
your
friends
to
submit,
and
with
that
do
we
have
one.
C
C
So
this
week,
I'll
continue
announcing
the
ons
EU
intro
and
the
OS
see
you
and
once
the
cupid
NSM
events
are
posted.
I
think
that's
probably
in
a
few
weeks
yet
for
cube
con
talks,
but
it
can
definitely
keep
promoting
the
net
research
master
con
and
the
CFP
call
for
proposals
and
whenever
we're
ready
to
do
0-200
release,
please
let
me
know
and
I
was
really
quick.
It
was
on
a
Friday
when
I
noticed
the
the
V
zero
one
zero
so
put
it
together
pretty
quickly.
C
B
Yeah,
so
with
that
that
actually
brings
us
to
a
short
announcement,
which
was
the
V
zero
one.
Zero
branch
was
was
finally
tagged,
and
so
that
should
mark
the
zero
one,
zero
release
for
people
to
to
start
testing,
and
so
of
course
this
particular
release
is,
is
a
I
want
to
say
between
alpha
and
beta
quality,
so
I'm
not
saying
done
running
your
production,
but
the
would
be.
But
if
you
were
very
brave,
if
you
do
and
but
any
feedback
we
can,
we
can
get.
B
Of
course
we
really
appreciate
and
all
fixes
are
going
to
go
into
master,
so
we're
not
going
zero
one
zero
should
not
it's
not
going
to
be
a
point
release.
It's
not
gonna
have
any
point
releases
like
your
1
0,
1,
2,
and
so
with
with
that
we
should
move
on
to
the
stuff
that
is
currently
in
progress
and
your
your
listed.
So
you
have
a
core
yeah.
A
So
I
apologize,
I'm,
just
getting
back
from
pts
I,
haven't,
had
a
chance
to
go
through
and
groom
the
outstanding
PRS.
But
when
I
was
last
here,
we'd
walk
through
the
stuff
in
progress.
I
wanted
to
get
the
community
a
bit
of
an
update
on
where
we
stand
on
the
the
sort
of
things
that
we
talked
about
that
and
make
sure
that
we
capture
any
new
stuff
in
progress,
and
the
same
is
true
for
specs
and
reviews.
A
A
D
A
And
then
that,
but
that's
actually
very
interesting,
because
what
it
lets
us
do
is,
if
you
have
a
network
service
and
the
network
service
is
part
of
what
it
does
also
provides
DNS,
then
the
pod
can
receive
that
DNS
service,
as
well
as
whatever
DNS
it's
normally
getting
from
kubernetes
and
that
actually
works.
If
your
pot
is
consuming
multiple
network
services
as
well.
So
that's
super
exciting
from
usability
point
of
view.
E
It's
going
fine
next
carries
I
mean
this
up,
he's
radiant.
It
should
be
reviewed.
It's
already
been
reviewed
by
an
acolyte
I.
Think,
okay,.
A
And
that
will
bring
into
a
standard,
spiffy,
spire
kinds
of
security,
plus
some
really
interesting
things
around
Providence,
so
that
you
can
make
sure
that
not
only
do
you
trust
the
guy
asking
for
the
network
service
that
you
trust
the
various
intermediaries
that
have
been
collaborating
on,
providing
it
cool
so
Artem.
How
is
it
or
domain
going
Oh.
A
A
G
Cool
yeah.
H
A
I
A
Yeah,
so
it's
definitely
stuff
folks
are
looking
at.
We,
the,
inter
the
current
internal,
you
know,
think
quick
get
to
where
you
want
to
go,
but
if
you've
got
folks,
if
you
would
be
interested
in
looking
at
that
or
F
folks
interested
looking
at
that,
it's
definitely
well
understood
to
be
a
problem.
We
also
need
to
solve.
J
A
Yeah,
so
the
the
way
network
service
mission
general
does
this
is
that
we
we
have
a
dynamic
negotiation
of
tall
types
between
a
client
and
something
providing
it
with
a
network
service
and
right
now,
the
one
that
we
have
built-in
support
for
SVX,
that
we've
got
folks
working
on
sr
v6
and
the
architecture
is
designed
for
basically
any
tunnel
type.
So
you
know
it
did
to
be
agnostic
as
to
the
tunnel
type
and
so
effectively.
J
A
A
Way
that
becomes
human,
but
if
I
had
say
a
network
service
endpoint
that
was
providing
a
network
service
and
I
wanted
to
be
able
to
have
a
pod
that
wasn't
running
in
the
same
cluster
or
participate
in
that
network
service.
You
could
do
that
and
effectively
think
of
it
as
sort
of
a
hub-and-spoke
approach
to
the
problem,
rather
than
a
point
approach
to
the
problem,
but
it's
not
a
bridge
approach
to
the
problem,
because
between
any
given
client
and
network
service,
you've
got
a
it's
a
point-to-point
connection.
J
So
just
just
one
thing
so
for
this
client
and
I
mean
service
providers
or
NC
endpoint.
So
will
there
be
a
single
tunnel,
so
there
will
be
so
even
for
crossing
the
clusters,
because
some
what
I'm
thinking
is
I'm
I'm
curious
about
the
abilities
for?
Is
it
possible
to
build
a
single
channel
across
the
collector
prostate
cluster
or
to
win
the
alexei
several
segmentations
and
put
them
together
into
form
a
well.
A
But
you
know
what
happens
in
the
intermediate
stage
can
be
very
flexible,
so
logical
level,
Network
service
mesh,
thinks
in
terms
of
workload,
communications,
not
cluster,
cluster
communications.
So
if
you
could
something
like
trunk,
a
bunch
of
stuff
along
a
single
tunnel
between
clusters,
I
mean
you
could
mechanically
make
that
happen,
but
when
it
gets
to
the
network
service
and
points
on
the
other
end,
those
network
service
endpoints
have
to
be
able
to
sync
which
the
traffic
from
each
client
in
an
in
a
straightforward
way.
A
But
this
is
actually
super
powerful
because
you
almost
never
care,
logically
speaking
about
cluster
to
cluster
communication,
but
you
care
about
its
workload
to
workload
communication.
You
know.
Typically,
clusters
have
way
more
stuff
running
in
them
than
you
want,
and
so
then
you
introduce
all
kinds
of
insane
attempts
at
IP
based
policy
between
the
eyepiece
and
the
clusters
and
make
it
super
messy.
J
B
I
think
it's
Taylor,
showing
it
in
the
scene
typing:
okay,.
A
This
is
all
Taylor
cool
yeah.
No,
it's
the
the
the
really
good
shorthand
Jason
is
to
realize
that
a
networked
surface
mesh.
We
think
about
everything
in
terms
of
workloads,
communicating
and
network
services,
not
clusters,
communicating
to
things.
So
we
don't
well
with
the
cluster
mr.
Lee
cool
anything
else
that
folks
wanted
to
talked
about
or
asked
about
with
inter
domain.
Do
we
have
any
good
documentation
for
how
people
can
play
with
the
Internet
main
feature.
A
So
anyone
interested
in
sort
of
poking
out
it
and
writing
down
the
experience,
so
we
can
do
a
demo.
Please
speak
up,
you
know,
go
and
do
so
properly.
Oprs
super
welcome
on
that
front.
It
should
be
great
fun
awesome,
so
we've
also
got
increased
plug
ability.
Do
you
want
to
comment
a
bit
about
this
Victoria
I
know.
You've
got
some
basic
infrastructure
in
place
and
you've
now
yours
now
slowly
making
the
whole
world
more
modular.
A
A
That's
the
mechanism
we
use
to,
for
example,
avoid
colliding
with
the
intra
cluster
or
kubernetes
networking,
and
we
have
in
the
first
pass
we
sort
of
built
that
into
the
network
service
manager
directly,
but
it
makes
all
that,
as
we
get
people
interested
in
doing
an
SM
in
a
broader
array
of
environments,
having
greater
modularity
makes
life
enormously
easier,
so
cool
all
right
artim.
Do
you
want
to
comment
a
little
on
how
SR
v6
is
going.
F
A
Now
I
know
that
we
have
one
or
two
people
who
are
super
interested
in.
That
of
the
people
in
question
are
on
the
call
today.
I,
don't
think
so,
but
they're
definitely
people
who
are
interested
in
that
and
it's
a
really
good
thing,
because
it's
sort
of
our
first
example
of
a
second
remote
mechanism
and
as
your
as
we
all
know
that
every
time
you
do
the
first
example
the
second
second
thing
you
shake
out
bugs
so
cool.
L
H
L
A
A
Then
the
SDK
evolution
stuff,
so
I
still
need
to
go
back
and
read
a
spear
and
get
it
finished
off.
This
is
something
where
I
was
making
the
SDK
a
little
bit
more
modular
and
also
building
into
it
the
ability
to
trés
at
the
sub
G
RPC
Co
level.
So
if
you
could
just
imagine
a
composite
where
you
have
a
list
of
small
little
pieces
of
work
like
connect
the
interface,
the
data
playing,
you
know
configure
this
about
the
data
playing,
etc.
A
So
it
might
be
a
good
approach
to
even
extend
to
how
we
build
network
service
managers
at
some
point,
because
that
would
even
make
it
simpler
for
people
to
build
network
service
managers
for
different
environments
cool.
Is
there
anything
else
that
folks
have
in
progress
that
isn't
listed
here,
that
we
can
highlight
I,
literally
just
cut
and
pasted
this
from
two
weeks
ago,
when
we
met
so
I
want
to
make
sure
we're
highlighting
other
people's
work?
That's
going
on
as
well.
A
Cool
and
then
the
second
thing
is
we
have
a
mechanism
in
network
surface
mesh
to
allow
the
community
to
talk
to
itself
that
we
could
refer
to
as
specs,
and
this
is
not
a
mandatory
thing.
You
don't
have
to
go
write
a
spec
before
you
write
code.
But
if
you
have
a
thing
you
think
you
want
to
do
and
you'd
like
to
go
and
have
that
conversation
with
the
broader
community.
A
A
They'll
they'll
actually
write
down
aspect
that
gets
committed
to
the
repo
that
describes
what
was
really
done,
and
so
the
those
specs
end
up
being
a
good
way
for
the
community
to
talk
to
itself
and
for
people
have
a
sense
of
what's
what
people
are
thinking
and
where
it's
all
going
and
to
bring
in
differing
ideas
on
things
and
then
I
listed
out
a
few
of
possibly
not
all
of
the
the
specs
that
I
think
are
actively
out
there.
So
if
you
want
to
go
back
to
the
list
of
the
day,
the
meeting
minutes.
B
A
B
I
couldn't
note,
while
we're
doing
that,
something
that
we
that
we
could
also
that
we
also
can
do
for
people
is,
if
you
have
something
you
want
to
build.
That's
not
gonna,
be
partly
in
a
summary
flow,
but
is
rally
owned
by
your
organization,
and
you
want
comments
and
are
and
are
comfortable
with
public
comments
on
it,
post
it
on
to
the
spec
port
here
and
we
will.
We
will
help
you
as
on
yeah,.
A
Totally
I
mean,
obviously
you
know
it's
been
for
conversation
more
than
anything
so.
B
G
B
A
Just
a
few
that
are
currently
sort
of
hanging
out
there,
that
would
probably
benefit
from
where
I
balls,
so
we've
got
the
getting
rid
of
device
plugin
that
is
currently
being
discussed.
We
currently
abuse
device
play
in
a
little
bit
and
once
security
lands
we
hope
to
be
a
loop
use
it
a
little
bit
less.
So
there's
a
spec
here
about
switching
more
to
TCP
for
the
communication
between
local
network
service,
endpoints
and
network
service
clients
and
their
their
per
node
network
service
manager,
so
that
that's
sort
of
laid
out
here.
A
A
M
M
A
Alright,
so
then
other
specs,
we
have
this
aspect,
that's
been
out
there
and
I.
Don't
think
we
have
the
gentleman
behind
it
on
the
call
today,
looking
essentially
looking
at
more
sophisticated
selection
of
candidates
right
now,
network
service
mesh
has
a
fairly
sophisticated
label
based
way
of
selecting
a
set
of
candidates
for
connecting
for
what
network
service
in
points
it
connects
a
client
to,
but
once
you've
selected
a
set
of
candidates
we
just
sort
of
round-robin
along
them,
and
so
this
spec
is
sort
of
looking
at.
A
How
could
we
be
more
sophisticated
and
make
smarter
decisions?
My
guess
is.
This
is
likely
gonna
start
interacting
at
some
point
with
some
of
the
stuff
that's
going
on
with
modularizing
the
network
service
manager
and
breaking
things
out
into
plugins,
but
it's
also
cool
and
then
I
think
Matthew.
What
I
don't
have
here
on
the
list
that
we
probably
should
is
the
stuff
you're
doing
on
gateway
work?
Do
you
want
to
say
a
few
words
about
that.
I
I
We're
looking
at
what
we
can
do
and
of
course
we
can
use
some
device
training
stuff,
especially
the
ones
that
is
already
in
the
NS
entry
I'm
looking
at
it.
But
there
are
some
quite
simple
alternatives
that
could
be
interesting,
especially
by
combining
virtuous
with
NSM.
This
is
a
simple
walk
round,
but
it's
not
in
the
scope
of
innocent
for
now.
I
A
That's
actually
super
useful
stuff
and-
and
you
you
there's
been
a
lot
of
interest-
a
lively
conversation
around
some
of
this,
so
I
would
encourage
folks
to
get
involved
and
participate
because
there's
definitely
interesting
stuff.
There
cool
anything
else
that
I'm
missing
from
the
specs
board
that
folks
want
to
sort
of
bring
up
and
make
sure
that
we
discuss.
A
L
Biden,
a
spec
I've
provided
second
power,
and
it's
ready
for
review
the
power
pass
at
all
tests
in
this
pair
I've
provided
solution
for
case
where
inside
car
performs
connection.
Also
in
in
this
part,
I
have
to
write
a
test
that,
in
the
same
coordinates
not
break
default.
Grenades
Denese.
So
please
take
a
look
after
that
I
plan
in
provide
final
part
of
the
nests
for
case
when
an
ass
I
mean
if
container
performs
connection.
That's
it.
A
B
One
more
thing
that
I'm
going
to
soon
add
on
to
the
specs
board,
so
that's
gonna,
be
so
the
the
McLeod
machinery
has
been
quite
useful
to
the
NSM
project
and
I
think
it'll
be
useful
to
others
who
are
outside
the
MSM
project
as
well,
and
so
what
I'm?
What
I'm
going
to
propose
chin?
The
specs
board
is
that
we
we
set
the
makefile
machinery,
so
everything
is
in
a
dot,
M
cave
directory,
with
the
exception
of
the
main
make
file
itself.
B
So
what
I'm
going
to
propose
is
that
we
take
that
down
m'kay,
we
split
it
into
things
that
are
generic
and
things
that
are
and
SM
specific
parametrize
a
few
of
the
things
that
are
that
are
in
SM
specific
and
then
what
people
will
be
able
to
do.
Is
it's
basically
copy
that
get
git
repositories,
we'll
split
the
MK
into
a
into
a
big
repository
that
or
copy
it,
rather,
that
you
can
then
use
to
import
into
into
other
projects.
B
So
if
you
have
a
set
of
micro
services,
you
want
to
to
test
anyone
use
make
in
order
to
drive
it.
You
could
take
make
kubernetes.
That
start
make
kubernetes
your
app
deploy
and
so
on
and
how
everything
work
in
the
same
way
that
it
works
within
the
MSM
system
itself,
and
so
I'll
write
up
some
some
documentation
on
what
my
ideas
are,
so
that
people
can
get
a
sense
of
that
as
well.
I,
don't
have
any
other
thing
on
my
excited
with
that
cool.