►
From YouTube: CNCF Network Service Mesh Meeting - 2019-08-06
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
Okay,
so
I
will
go
ahead
and
get
started
on
the
on
the
actual
call
itself
and
if
someone's
able
to
get
around
to
sharing
it,
that's
fantastic.
If
not
also
posting
the
link
would
be
right
here
would
be
good.
So
we
have
three
recurring
meetings
where
the
MSM
document
meeting,
which
looks
like
it's
been
switched
monthly,
do
do
we
have
do
we
have
anyone
from
that
particular
call
I'll
reach
out
to
Rocky
and
and
Prem
to
see
what
they
turn
up.
Now
we
got
two
Jeffrey
see
if
he's
up
to.
A
Running
this
at
the
splitter
time
like
maybe
we
could
switch
the
time
around
to
a
two
time:
that's
more
accommodating,
but
right
now,
I
think
he's
actually
on
a
vacation.
So
we'll
work
out
when
we
want
to
run
that
same
with
the
use
case,
call
so
I'll
reach
out
to
pram
and
and
romkey
get
about
it.
We
have
the
scene
see
if
Telecom
user
group,
which
occurs
every
first
and
third
Monday.
We
just
had
a
call
yesterday
and
there
is
a
cnc
of
networking
working
group
which
occurs
every
two
weeks
on
Tuesday
at
9:00
a.m.
B
More
thing
to
hear
check,
muted,
yeah,
sorry,
so
if
it
we
probably
should
update
our
minute.
So
we
have
the
this
morning
at
least
European
morning
we
hit
the
workgroup
colder
and
it's
a
more
Group
Co,
which
is
in
the
Asia
friendly
timezone,
okay
time
so
I
don't
know.
Maybe
we
should
just
start
it
here
also
in
the
recurring,
but
the
minutes
are
updated
there
just
below
these
new
ones.
So
I
might
give
an
update
later
sorry,
cool.
A
So
we
have
three
major
events
going
on.
We
have
ons
summit
in
Europe,
we
have
four
talks
accepted
a
a
tug
amitabh,
that's
going
on
so
from
user
group,
and
we
have
the
CNF
test
bed
tutorial,
which
which
will
be
going
on
and
so
a
lot
of
activity.
We
have
the
open
source
summit
and
Lian
with
a
with
a
talk
accepted
there
by
Ivana
and
Bratislava,
and
we
have
cube
Khan
and
cloud
native
Khan.
We're
still
waiting
to
see
what
the
results
for
the
talks
are
on
that,
but
it
is
a
huge
announcement.
A
We
have
a
NSM
conference,
co-located
conference
and
a
semcon
which
has
been
announced
and
the
call
for
papers
is
open,
so
yeah
so
have
a
full
day
of
other
some
related
things.
So
definitely
mark
your
calendars.
The
entry
for
it
is
$50
said
those
50
dollars
will
be
donated
to
the
to
the
CMC
F
diversity
scholarship
fund,
so
the
$50
is
primarily
to
prevent
people
from
signing
up
for
a
free
event
and
taking
up
slots
and
preventing
people
who
really
want
to
come
from
from
joining
it.
A
B
A
A
A
B
Okay,
so
today
we
had
our
first,
we
should
have
an
official
name
for
it,
but
let's
say
that
it's
the
be
weekly
morning
call
it's
your
European
morning,
10
a.m.
Central,
European
Time
think
it's
on
the
calendar
already
it
would
it
probably
some
rings.
Given
there,
we
had
quite
good
patterns,
I
think
about
10
people.
B
So
it's
a
thirty
minute
one.
It
was
mostly
about
you,
know,
introducing
the
project
and
talking
about
the
status
we
hit.
A
number
of
questions
from
participants
and
the
intent
is
that
in
the
following,
one,
which
will
be
in
two
weeks
will
give
like
the
purpose
of
this
course
to
mostly
people
to
ask
questions.
B
Give
suggestions
like
what
would
be
what
would
make
sense
and
things
like
that.
So
on
this
call,
it
was
mostly
me
talking
about
where
we
are,
what
we
do,
the
purpose
of
the
college
cetera,
but
on
the
next
course
it
would
be
mostly
the
floor
would
be
for
the
people
that
attend
and
talk
about
it
not
think
I
mean
I'm
excited
that
we
started
it.
We
had
participation,
I,
hope
that
it
will
grow
even
more.
A
A
A
We
are
also
listed
on
the
cube
con
co-located
events
webpage.
So
you
see
if
you
con
2019
program
in
the
day
and
all
the
co-located
events
were
listed
there
as
well,
so
you
can
point
people
there
and
you
can
also
point
them
to
our
website
that
you
never
service
mesh
website
and
we
have
it
listed
under
events
and
so
we'll
put
some
verbage
on
the
front
web
page
soon.
So
that
is
a
2d
that
that
we
have
at
this
point
so
and
will
will
share
more
information
as
as
time
goes
on
and
see.
A
So
we'll
add
that
to
the
to
the
events
page
as
well,
and
so
since
we
don't
have
anything
else,
that's
on
the
agenda
there.
There
is
something
that
I
wanted
to
to
talk
about
a
little
bit
so
and
nikolai
you'll
have
a
lot
more
information
than
I
will
at
this
point.
So
we
were
having
a
bit
of
flakiness
on
the
on
the
bills
and
and
with
bringing
the
NS
Eastview
alright,
do
you
have
any
information
on
that
in
terms
of
like?
What's
going
on
or
what's
happened.
B
B
B
Essentially,
the
fix
is
the
problem
from
our
side
is
that
our
customers
also
finished
us
when
all
the
network
service
endpoints,
that
our
service
managers
and
that
services
themselves,
they
are
all
scoped
to
a
cluster
level
and
we
are
accessing
them
with
a
namespace.
In
the
request
like
when
we
want
to
access,
for
example,
the
list
of
network
services,
we
were
just
ending
call,
so
the
namespace
in
this
fix
specifically
prevents
this
in
this
case.
B
What
we
discussed
in
the
main
in
China
was
essentially
that
it
probably
is
a
better
idea
to
keep
the
IDs
and
just
make
the
sphere
this
name
spaced.
So
this
will
eventually
allow
in
the
future
to
be
able
to
run
to
network
service
managers
in
parallel
and
I
know
that
this
is
maybe
a
little
bit
debatable
and
probably
needs
a
little
bit
more
thinking.
It's
essentially
just
deciding
on
one
or
the
other.
A
A
B
B
A
C
A
D
This
could
give
us
probably
we
need
to
create
different
at
least
one
sanity
test,
where
different
versions
of
kubernetes
and
put
it
into
our
continuous
integration
system
so
just
check
all
the
ocean
check
master
check,
illicit
versions.
It
should
be
pretty
easy
in
current
infrastructure
and
I.
Think
good
idea.
D
B
D
A
B
So
right
now
we
think
this
is
which-
which
versus
because
essentially
in
this
particular
in
this
particular
case,
because
it's
a
CV
I'm
pretty
much
sure
that
everyone
back
ported.
So
there
was
a
question
on
the
chat.
Why
why
AWS
broke
big
I
mean
even
if
they
are
using
one
point,
three
one:
thirteen
seven
but
I,
guess
that
they
just
back
ported
this
specific
part,
because
it's
a
CV
when
the
moment
that
is
disclosed,
you
should
be
patched,
especially
when
you're
a
public.
B
B
It's
a
bit
tricky
also
also
also
given
the
fact
that
that
they
also
are
providing
a
couple
of
versions
from
what
I
know
like
you
have
112
and
113
in
in
Asia,
in
a
degrees
right,
you
are
able
to
switch
back
and
forth
between
two
different
versions:
I
mean
if
we
have
to
be
to
be
to
be
checking
all
the
versions
that
are
out
there
and
that
we
claim
with
support,
or
we
should
just
figure
out
that
subset
then
say
we
support
this
decision.
This
I,
it's
usually
really
a
matter
of
just
small
API
modifications.
B
In
this
case
yeah
there
was
a
security
fix
which
I,
don't
okay,
I
hope
that
there
won't
be
much
of
these
in
the
future.
Like
you
know,
every
week
or
every
month,
I
thought
that
is
mostly
about
just
bumping,
the
API
to
the
next
version
and
changing
things
here,
and
there
like
I'm,
trying
to
do
now
with
the
web
hook,
which
apparently
changed
quite
from
the
time
that
we
we
used
to
go
and
go
code,
but.
A
B
A
Yeah
I
think
something
we
could
do
in
the
meantime
is
like
where
now
it's
better
to
keep
it
simple,
because
we
have
limited
resources,
so
so
it's
the
my
recommendation
would
be
keep
it
simple
with
the
CI
is
doing
what
it
needs
to
do.
So.
The
factor
2
Broke
on
one
on
one
15
2
is
is
excellent,
that
we
caught
that
and
eventually
when,
when
we're
shipping
our
our
first,
they
will
release.
So
we
can
work
out
and
say:
hey.
A
This
thing
runs
on
this
version
of
Kuhn
Eddie's,
as
its
primary
we've
also
tested
it
on
on
these
versions
of
these
clouds,
and
so
we
just
we
just
say
what
our
CI
cuts
it
on
in
the
beginning
and
then
what
we
can
do
is
in
the
long
run
as
we
get
more
resources.
A
best-case
scenario
would
be
to
get
like
someone
in
Google
to
help
maintain
the
testing
with
the
Google
cloud
and
someone
from
from
AWS
to
help
support
and
test
aw
excellent.
A
So
that
would
be
the
best-case
scenario,
but,
barring
that
we
can
say
you
need
other
versions
that
we
test
it
against
and
when
a
CVE
comes
out
we
can.
We
can
make
sure
that
it
continues
to
to
work
with
the
versions
that
we
explicitly
have
stated
and
the
clouds
will
have
to
play
it
by
by
ear,
because
we
may
not
have
the
choice
of
moving
up
to
a
doctor
release
they
may
they
may
force
people
to
move
up
to
a
higher
one
in
depending
on
their
on
their
okay
strategy.
A
But
for
now
my
recommendation
is
Steve
example:
we
we
fix
the
we
fix
the
problem
and
I
think
temporarily.
Well,
people
I
think
doing
a
pinning
to
an
older
version
on
main
and
the
master
I
think
would
be
okay,
it's
just,
but
it's
just
so
we
can
unblock
people
who
are
actively
actively
testing
and
it's
them
for
the
first
for
the
first
time
until
we
until
we
have
that
first
stable
release
and
then
from
then
on
we'll
always
point
people
to
the
a
to
the
stable
release.
A
A
A
B
I
was
I
was
just
saying
that
it's
actually
a
good
good
occasion
to
actually
probably
sit
down
and
think
a
little
bit
more
about.
How
are
we
handling
all
these
different
versions?
Because
okay
testing
is
wanting
it's
fine,
but
then
our
client
client
code,
for
example,
is
somehow
stuck
to
one
point:
14
for
reasons
and
you're
not
really
able
to
move
forward.
It
is
not
that
easy
and
then
I'm
not
sure
what
other
projects
are
doing.
Are
they
following
just
the
latest
East
Branch?
We
also.
B
Essentially,
we
have
three
versions:
released
113,
114
115
in
terms
of
kubernetes,
and
are
we
tracking
all
of
these
such
do?
We
need
to
build
against
different
clients.
Are
they
backward
compatible
for
what
compatible
even
I
know
that
some
of
the
api's
are
but
not
really
sure
how?
What
is
the
proper
way
of
being
able
to
support.
A
Let's
start
doing
a
little
bit
of
research
on
it
and
we
can
manage
with
the
specs
port
and
say
these
are
the
upgrade.
These
are
the
version
strategies
in
each
of
the
crab
runs
the
version
strategy
the
kubernetes
uses,
and
that
way
we
can
have
all
the
information
in
one
place,
because
I'm
Jimmy
is
not
here
with
what
these
companies
are
doing.