►
From YouTube: Network Service Mesh Meeting - 2019-06-12
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
A
B
So
I
think
that
Frederick
was
wanting
to
talk
at
some
point
about
release,
notes
which
I
think
it's
only
probably
we
should.
We
should
walk
through
at
some
point.
I
know
that
it
was
also
an
action
item
from
yesterday's
meeting
about
looking
at
how
to
take
some
of
the
stuff
in
the
the
technology
tree
and
turn
it
into
a
proper
roadmap.
So
there
was
you
stick
this
in
the
chat
there
was
this
stuff
better,
yet
I'll
put
on
the
agenda.
That
would
be
even
smarter.
C
A
D
B
E
F
B
F
No
I
actually
forgot
that
done
that
we
still
have
to
I.
Don't
want
to
put
the
messaging
that
I
kind
of
skipped
this
meeting,
but
there
were
some
discussions
that
you
were
trying
to
figure
out
the
messaging
about
NSM
in
general
that
should
go
into
the
site
and
probably
into
the
race
notes
to
some
extent,
because
we
hear
Jeff
again,
this
a
reversal
architecture
has
been
built
for
kubernetes.
These
components
include
Paula
and
then
there's
discussions.
If
this
is
the
right
wording
ink,
it
is
what
some
say
so.
D
D
B
D
B
B
B
Also
note
that
there
is
literally,
if
you
scroll
a
little
bit
to
the
right
or
you
you
know,
because
we
can't
see
the
the
full
width
of
it.
But
it
shows
you
this
diagram
for
the
use
case
and
then,
if
you
scroll
a
little
bit
to
the
right,
oh
I'm,
sorry
you're,
maybe
it's
okay
off
its
its
Marshall
below
for
you.
For
me,
it's
left
to
right,
but
basically
it
shows
you
the
diagram
and
then
like
a
little
terminal
window.
B
That
shows
you
what
goes
into
it
and
it
does
this
for
all
the
use
cases,
and
it
strikes
me
that
if
we
did
something
like
this
and
also
had
you
know
it's
set
up
in
such
a
way
that
you
could
actually
run
those
use
cases,
because
you'll
notice
that
you
can
actually
select
the
text
in
the
little
images
that
they
have
of
the
you
know.
So,
basically,
if
we
had
something
that
ran
through
okay,
this
is
how
you
go
and
run
the
VPN
gateway.
Example
right.
F
B
D
B
And
or
I
mean
so,
if
you
had
a
terminal
window
piece
like
here,
you
might
actually,
you
know,
show
okay,
this
is
how
you
go
and
you
run
it.
You're
cute
control,
apply
or
home,
install
blah
right.
Okay,
we
can
do
that
and
you
get
to
see
a
you
know
effectively.
A
very
simple
walkthrough
of
the
whole
thing
sort
of
setup
is
a
really
quick
snapshot
like
that,
so
not
long
and
in
the
ending,
but
but
literally
something.
B
B
Things
like
installation,
helm,
install,
NSM,
helm,
install
VPN,
the
cube
control
to
redirect
V
or
hum,
install
and
ascent
monitoring
the
queue
control
to
redirect
the
sky
dive
that
shows
up
as
a
clickable
link
to
whatever
that
localhost
port
would
be,
and
then
you
show
the
picture
of
what
you
would
something
like
what
you
would
see
in
sky,
guys
right
that
kind
of
thing.
Okay,
it
was
kind
of
what
I
was
thinking.
You've
got
probably
the
best
visual
sense
on
the
call,
so
I
very
much
welcome
your
thoughts.
H
B
On
what
use
case,
each
is
probably
a
really
good
way
to
represent
it.
You
know
it's
a
basic,
you
know
sort
of
a
you
know.
You
know
sort
of
leading
with
you
know
era.
You
want
to
offer
an
assent
to
your
to
your
kubernetes
cluster.
Here's
how
you
do
it
that's
sort
of
use
case
what
use
case
to
might
be.
B
You
want
to
take
advantage
of
the
VPN
gateway
in
every
service
in
point
as
a
developer,
you
know,
and
you
could
show
the
yellow
of
what
you
add
to
your
file
right
and
then
maybe
the
very
last
you
sit
use
cases
your.
You
know
your
network
service.
You
want
to
develop
a
network
service
and
we
could
show,
like
you
know,
the
legal
block
Ness
of
the
SDK
for
that
yeah.
That
makes
one
yet
I.
D
D
D
Okay,
this
is
what
the
operator
gets
out
of
it
so
and
there's
definitely
more
more
personas
that
we
want
to
believe
eventually
wants
to
show
off,
but
I
think
we
should
probably
limited
to
three
on
the
on
the
website
itself.
What
are
the
three
that
we
really
want
to
express
I
think
the
ones
that
we
spoke
about
here,
probably
the
highest
of.
A
It
seems
likely
those
use
cases
for
getting
started
can
be
done
separately
from
this
document.
Singer.
Release
notes,
are
you?
Are
we
using
this
as
a
guide
for
all
the
things
that
want
to
be
they
that
you
want
to
be
done
with
the
release,
or
is
this
literally
the
release,
notes
and
all
of
these
items
have
to
be
part
of
it?.
B
A
Sure,
maybe
then
we
could
say
the
getting
started.
What's
part
of
the
release
nuts
here
and
you
direct
people
to
the
front
page
so
just
going.
F
A
We
didn't
have
yeah
I'm
paid
to
redesign
so
I,
see
this
here
and
specifically
you're
talking
about
how
to
get
started
based
on
you,
skel
someone's
already
putting
it
in
thanks.
A
D
D
Because
we
like
so
once,
you
use
our
zero-one-zero
release,
notes
and
we're
up
to
version
one
or
two,
then
definitely
we
want
them
using
the
newer
version,
but
at
the
same
time
there
is
something
really
nice
about
your
in
the
document
and
it's
like
how
do
you
install
it?
This
is
how
you
install
it,
and
you
know
just
having
like
one
or
two
one
or
two
quick
liners.
It's
like
how
how
something.
C
A
You
could
always
have
a
link
from
this
to
wherever
it
is,
and
ideally
the
getting
started
is
going
to
be
as
you're
saying,
Fred
it'll
be
kept
up
to
date
and
it
doesn't
matter
whatever
release
you're
looking
at.
If
someone
is
looking
at
a
point,
one
release
but
you're
on
you
know,
point
R,
2.0,
then
you're
you
would
I
would
think
you'd
want
to
send
people
to
whatever
the
current
getting
started
is
and
not
have
people
getting
started
on
something
that
was
released
a
year
ago,
yeah
I
think.
B
A
D
A
That
sounds
good,
so
they
have
this
getting
started
which
actually
goes
outside
of
the
main
page.
But
it's
it's
not
those
use
cases
I
don't,
and
nowhere
is
the
I
guess
you
just
happen
to
be.
You
have
to
scroll
down
and
see
this.
A
C
A
C
I
B
D
C
C
C
B
D
That's
what
I'm
getting
at
I
want
I
want
to
show
like
cuz
we're.
This
is
a
huge
release
like
like
our
first
release,
has
had
like
a
year's
worth
of
work,
yep
and
I
I.
Don't
think
we
can
do
justice
to
the
project
by
trying
to
call
out
importing
commits
or
similar,
but
I
do
think
that
we
can
show
high-level
ideas
and
we
started
what
is
network
service
mesh?
D
What
are
the
API
is,
what
is
the
architecture
for
it
and
then
just
drive
down
into
more
details
of
what
we
are,
what
we're
releasing
until
we
get
down
to
the
to
the
concrete
you're.
The
guys
you
can
look
at
here
are
the
here's,
the
reference
company
architecture,
which
has
real
things
that
that
work
today,
yeah.
B
D
A
A
D
B
D
D
So
we'll
add
in
add
into
the
node
that
would
be
would
be
useful.
D
H
You
know
one
thing:
it
might
be
silly
on
my
part,
but
from
the
beginning,
when
we
talked
about
the
RPC
and
network
service
mesh,
it
seemed
to
me
that
the
literal
network
communication
was
going
to
be
over
T,
RPC
and
I.
Guess
that's
that's
not
the
case
right.
It's
through
different
various
cross
connects
and
regular
network
connections.
We
do
get
all
the
normal
stuff,
it's
just
the
API
d
RPC.
So
that
was
to
me
you
actually
was
a
confusing
thing
from
outside
I
thought.
C
D
A
B
A
D
A
D
D
For
the
moment,
this
is
a
good
spot
for
it
and
I
think
we
we
we
could
give
a
link
to
where
they're
at
but
I
also
agree
with
Edie
I.
Think
so.
I
wanted
to
focus
on
those
two,
because,
like
you,
can
you
can
pretty
much
build
an
en
SM
and
get
a
good
understanding
as
to
how
it
works
with
which
business
to?
A
D
D
D
D
D
Like
basically
like
we,
you
know
just
doesn't
account
for
a
in
a
sense
or
how
do
you
do
Roxi
at
proxy
in
a
sentence
and,
and
so
I
think
that.
D
Yeah,
so
with
with
a
brief
preference
of
what
the
arc
of
what
the
reference
architecture
is,
and
then
we
can
go
straight
into
the
into
the
actual
reference
architecture
and
the
one
last
thing
as
well
is
I.
We
need
to
work
out.
Where
do
we
want
with
the
glossary,
because
it
actually
feels
unnatural
as
to
where
it
currently
is,
with
the
to
do
I
immediately
below
the
the
description.
D
So
like?
That's,
probably
the
last
thing
that
we
want
to
note
that
we
definitely
wanna
call
out
as
well
as
like
here's,
a
here's,
a
list
of
all
of
our
terms,
but
but
at
the
same
time,
I
I
think
the
reason
why
it
ended
up
with
the
to
do
there
is
because,
in
order
to
really
understand
this
next
section
you
it
may
help
to
have
the
glossary
available.
D
So
it
so
I'll
see
about
wording
in
such
a
way
that
we
can.
We
can
get
to
that.
Get
to
that
glossary.
The
only
thing
that
bothers
me
in
the
glossary,
though,
is
that
the
glossary
may
change
over
time,
and
then
words
here
may
become
nonsensical
to
a
future
reader.
So
that's
that's
my
only
concern
with
it.
A
If
this
is
for
the
release
notes
in
the
glossary,
if
it's
a
snapshot
in
here,
then
it's
relevant
to
everything
you're
talking
about
so
I
appear
at
the
top
your
when
you're
saying
initial
release
and
going
through
things,
and
there
could
be
atoms
that
you're
talking
about
here,
which
may
change
in
a
future
release.
But
right
now
the
glossary
would
be
relevant.
A
A
A
D
Just
put
a
link
and
delete
everything
else:
yeah,
oh
yeah,
a
link,
a
link
to
I
can
also
just
do
it.
I
could
create
a
PDF.
That's
like
version
zero,
one,
zero
and
say
here's
the
glossary
as
of
this
date
for
release
version,
zero,
one,
zero
and
then
and
then
I
could
just
link
to
that
and
then
not
have
to
worry
about
it
ever
again.
D
Yeah
so
I
think
those
are
the
main
things:
okay,
I,
don't
think
I
have
anything
else.
Do
you
really
go
through
other
than
eventually
we're
gonna
circle
back
and
we'll
go
over
the
the
known
issues
that
we
want
to
call
out,
but
beyond
that,
like
I,
think
I
think
I'm
pretty
happy
with
where
it's
at
at
the
moment.
D
Yeah
and
and
the
known
issues
that
I
could
even
just
be
a
that
Becks.
That
could
also
be
a
link
to
a
lid
to
a
living
document
that
says
like
as
we
as
we
put
it
out.
There
I
expect
the
list
of
known
issues
to
grow,
so
so
we
can
put
that
in
the
link
and
say
for
version
zero.
One
zero
over
here
are
the
known
issues
with
it,
and
then
that
actually
ties
us
into
the
next
version,
which
is
here.
Things
are
fixed.
D
D
B
A
A
B
Okay,
there's
an
incredible
amount
of
value
of
just
warming
people
to
ideas,
so
this
is
an
attempt
to
look
at
some
of
the
stuff
that
we're
looking
at
going
forward
and
and
basically
what
I've
done
is
I've
sort
of
taken.
Some
of
the
functional
boxes
like
we've
got
a
bunch
of
stuff.
We
know
we
have
to
do
about
security
getting
inter-domain
finished.
Probably
it
really
depends
on
that.
We've
got
a
bunch
of
things
that
we
want
to
do
around
being
able
to
get
DNS
support
right.
B
That
probably
depends
on
you
know
various
things
around,
maybe
transit,
possibly
transitioning
in
a
container
sannasi,
monitor
containers
a
sort
of
control,
plane,
side
cars.
You
know,
as
you
sort
of
go
through
this,
you
say
well,
I
want
Hardware
NICs
well
properly
doing.
Hardware
next
is
something
for
which
you're
going
to
want
enter
domain,
that
kind
of
stuff
and
so
building
out
the
tree
of
interdependencies
and
then
trying
to
capture
the
things
and
I
used
some
of
the
the
blue
and
the
green
background.
F
H
F
B
B
I
know
the
data
center
people
I've
dealt
with
like
approximately
zero
data
center
humans
are
ever
going
to
turn
over
control
of
their
tour
switches
to
some
separate
administrative
domain,
that's
being
run
by
their
freakin
kubernetes
people.
It's
just
never
gonna
happen
right.
They'll
they'll
run
away
from
that
because
it
feels
dangerous,
but
if
you
give
them
the
domain
for
those
that
DC
network
stuff
and
you
expose
it
as
network
services,
they
can
then
show
up
in
those
pauses
to
Sarila,
PDFs
or
physical
links.
G
F
B
B
I
think
what
I'm
hearing
here
is
that
the
is
probably
need
to
revisit
those
specs
and
pull
them
together
more
coherently,
yeah
I
recently
did
an
update
to
the
inter
domain.
That
I
would
have.
They
recommend
folks,
look
at
it
takes
the
same
initial
idea,
and
it
makes
it
a
little
bit
more
flexible
and
it
occurred
to
me.
You
know
is
doing
it
that
it
actually
makes
it
actually
starts.
Looking
more
gateway
like
in
some
sense,
revisit
the
discussion
about
the
gateway
spec
as
well.
F
Okay,
but
I
mean
the
the
the
the
bigger
idea
here
is.
Are
we
saying
that,
because,
essentially
the
Gateway
is
kind
of
the
translation
point
between
the
physical
outside
world
and
inside
any
same
world?
If
you
want
to
call
it
like
this
and
then
hear
what
you're
saying
in
this
inter-domain
arrow
to
harbor,
an
accessory
essentially
means
that
hardware,
Nick
and
SIV
are
represented
the
services
that
the
any
same
guys
are
supposed
to
consume.
Like
the
SM
pots,
our
clients
are
supposed
to.
B
Know
when
I'm
actually
suggesting
is
that
S
aureus,
ETFs
and
hardware
necks,
are
actually
met.
Local
mechanisms
by
which
these
things
can
their
local
mechanisms,
by
which
you
can
connect
your
pond
to
a
network
service.
It
happens
to
be
local
mechanisms
where
you
know
they're
coming
via
the
S
REO
of
EDF
and
where
the
thing
that's
actually
providing
the
service
is
a
tour
port,
but
they
are
basically
local
mechanisms.
E
G
A
B
B
A
I
think
we
may
be
there
with
the
use
case
at
this
point,
we're
essentially
putting
we're
trying
to
have
seen
us,
or
that
has
the
mechanisms
to
talk
to
the
physical
interface
and
it
whatever
that
would
be.
You
could
think
that
could
be
SRV
or
or
whatever
type
of
access
that
we're
trying
to
implement
in
my
mind-
and
I
think
that
may
be
what
nick
life
saying
that
portion
in
the
in
the
upper
right
I
think
we're
actually
trying
to
get
this
working
as
part
of
the
latest.