►
From YouTube: CNCF SIG Network 2020-10-15
Description
CNCF SIG Network 2020-10-15
A
B
B
A
C
B
D
B
D
B
B
D
Yeah,
that
is
as
a
side
note.
That
is
one
thing
that
I
have
a
characteristic
of
senior
architects
of
principal
architects
that
that
I've
come
to
not
sure
if
it's
admire
or
just
have
respect
for
their
willingness.
A
few
of
them.
A
select
few
are
willing
to
do
a
filibuster
or
to
just
put
in
the
time
it
takes
to
convince
every
single
last
person
and
yeah.
I
don't
think
my
patience
goes,
that
deep.
B
I
mean
the
successful
ones,
don't
actually
try
and
convince
every
last
person,
the
successful
ones
just
figure
out
who
has
to
be
convinced
and
how
much
energy
it's
gonna
take
to
convince
somebody,
and
sometimes
they
don't
even
convince
all
the
people
who
are
important
because
some
of
them
just
aren't
worth
the
energy
and
not
convincing
them
is
not
going
to
be
a
problem.
It
should
be
an
annoyance.
D
C
C
D
D
D
D
D
D
D
D
So
there's
a
spreadsheet
here
that,
hopefully
all
of
you
can
get
to
that-
has
a
list
of
around
60
patterns
that
are.
I
have
been
identified
as
common
ways
of
either
of
either
configuring
operating,
deploying
and
then
sort
of
on
you
know
doing
things
of
management
around
service
meshes
and
their
workloads,
and
so
you
know
one
of
the
things
that
that
we
do
in
general
in
this
sig
and
others
is
try
to
help
curate
and
promote
cloud
native
technologies
and
some
best
practices
around
them.
D
So
if
you
would
give
it
a
thought,
some
comments
would
be
helpful
at
some
point.
I
don't
know
that.
There's
a
white
paper
here
included
in
this
effort,
but
at
some
point
a
lot
of
details
about
each
of
these
patterns.
Will
be
made
probably
some
illustrations
about
them
and
so
and
also
some
ways
to
like
quickly
deploy
those.
D
I
don't
recall
if
this
had
happened
since
the
la
in
the
last
time
that
we
had
met
but
nginx
service
mesh
or
the
other
nsm,
as
I
like
to
refer
to
it
or
nsm-2,
has
has
been
announced
and
is
out,
and
so
has.
Anyone
is.
Is
that
a
topic
of
interest
that
service
mesh
in
general?
Is
that
a
topic
of
interest
to
anyone?
Nginx
surface
smash.
C
B
Right,
speaking
of
which
does
anybody
actually
know
someone
that
we
could
have
a
friendly
conversation
with
nginx
about,
given
that
they're
about
two
years
late
to
acronym,
stomping
and-
and
I
I'm
not
really
interested
in
getting
into
a
fight
over
it.
But
my
guess,
is
it
never
really
occurred
to
anyone,
but
there's
lots
of
existing
collateral,
including
a
whole
bunch
of
nsm
domains
with
the
acronym
that
are
pointing
to
you
know
the
the
one
true
original
network
service
match
so,
like
I
said
yeah.
If
you
could
just
try
and
connect
me.
D
Yeah,
it
probably
is,
as
a
matter
of
fact
it
might
even
be.
Not
only
will
I
I'll
connect
you,
but,
but
I
might
also
invite
invite
them
to
this
call
if
it's
of
interest
to
folks
in
part
because
well
in
part,
because
it's
just
a
general
interest
to
the
service
mesh
working
group,
but
it's
also
that
their
their
rest,
api
is
based
on
smi
and,
as
such,
you
know,
should
be
smi
conformant
and
so
that
that
relate
they
may
want
to
participate.
D
C
B
D
B
C
B
B
There's,
certainly
a
lot
of
different
approaches
to
all
of
this.
That
folks
are
taking,
and
I
think
it's
probably
in
everyone's
best
interest
to
keep
it
a
little
bit
generic.
Now
that
the
question
of
whether
or
not
you
want
to
write
xds
in
that's
a
different
matter,
because
I
tend
to
see
xds
as
essentially
an
emerging
standard
that
has
come
out
of
envoy.
D
That's
that
that
very
thing
has
flustered
me
actually
specifically
with
envoy
in
part,
because
it's
not
just
the
golang
based
chinese
project,
of
which
there
are
a
couple
they've,
the
one
that
you're
mentioning
that
was
kind
of
primarily
backed
by
ant
financial
there's
a
a
couple
of
other
times.
I
think
four
other
times
that
have
been
demonstrated
that
you
could
like
istio
specifically,
could
be
run
as
a
control
plane
over
different
proxies
and
so
yeah.
B
I
mean
the
other
one
that
I'm
always
mindful
of
things
like
this
and
I'm
sure
folks
have
been
on
the
receiving
end
of
this.
Before
too,
is
I've
occasionally
had
been
involved
with
situations
where
you're
responding
to
some
rfp,
where
someone
has
to
meet
a
standard
and
the
standard
got
written
with
a
technology.
That
was
a
good
idea
at
the
time
and
it
is
now
required.
B
It
is
also
known
to
be
a
gaping
security
hole
and
a
performance
pig,
and
so
you
literally
have
to
go
write
things
that
suck
just
to
be
able
to
address
the
rfp,
and
I
don't
ever
think
we're
going
to
get
to
specifically
that
scenario
with
with
envoy
I
mean
it's
a
pretty
healthy
community,
it's
a
pretty
cool
platform,
but
it
just
sort
of
drives
home.
Why
you
don't
want
to
do
silly
things
like.
D
D
On
the
topic
of
of
smi,
so
so
and
smi
conformance
there,
I'm
not
sure
how
many
service
meshes
are
smi,
conformant
or
smi
compliant,
but
there's
a
number
of
them
and,
and
so
we've
discussed
the
conformance
tests
that
that
are
to
run
to
assert.
You
know
to
to
prove
that
that
is
the
case,
nikolai
specifically
as
it
pertains
to
like,
where
that
set
of
work,
kind
of
falls
in
the
priority
order
of
sort
of
the
bucket
list,
so
to
speak
for
kuma.
D
Specifically,
I
I
wanted
to
make
sure
I
delivered
on
my
my
promise
and-
and
it
was
there-
was
a
contributor
in
the
well
actually
that's
kind
of
gone
across
a
lot
of
the
service
mesh
communities.
Tyrone
is
his
first
name.
I
had
touched
base
with
him
and
he
had
been
quite
interested
to
assist
in
context
of
kuma
and
smi
conformance.
C
C
D
Yeah
speaking
of
abstractions
and
and
xds
the
the
working
group
there,
the
universe
was
it
the
universal
data
plane,
api
working
group,
yeah
d.
Has
anyone
and
it's
unfortunate
that
matt
isn't
on,
but
is
anyone
familiar
with
other
implementations
of
that
api,
and
I
this
is
probably,
if
I
think
about
it
for
a
moment,
it's
probably
an
ignorant
question
because,
like
kuma,
for
example,
nikolai,
like
the.
C
C
B
C
I
saw
it
in
in
the
patterns.
That's
that's
definitely
something
really
interesting.
I
mean
the
fact
is
that
the
very
first
pitches
of
the
service
mesh
a
concept
was
were
about.
Okay,
you
need
this
proxy
because
otherwise
you
have
to
implement
this
over
and
over
again
in
various
languages,
in
your
microservices
yeah
and
now
yeah.
B
C
I
mean
being
a
networking
engineer
for
so
many
years.
The
fact
that
I
have
to
use
ip
tables
to
just
get
my
packets
through
the
proxy.
It's
driving
me
crazy.
I
mean,
like
you,
have
two
containers
sitting
side
by
side
and
instead
of
having
some
same
like
packet
passing
between
them,
they
go
to
the
kernel
and
back
just
to.
B
B
D
B
But
it
opens
up
a
whole
lot
of
possible
ways
to
to
do
this
sort
of
thing,
because
you
could
then,
as
you
said
you
should,
you
could
sort
of
do
things
in
a
direct
fashion,
shared
memory
to
shared
memory,
so
you're
doing
networking
at
the
speed
of
the
pci
boss.
The
memory
bus,
rather
rather
than
having
to
sys
call
through
the
kernel,
which
could
be
huge
advantages,
and
this
could
also
be
super
interesting
in
in
conjunction
with
another
thing.
B
I've
been
playing
with
recently,
which
is
I've,
actually
got
a
library
that
will,
if
you're,
using
grpc
over
unix
file
descriptors.
Are
you
starting
unix
file?
Sockets?
I
have
a
library
now
that
will
let
you
pass
files
over
those
with
grpc
so
that
you
could
say:
okay,
I'm
going
to
create
a
shared
memory
region
over
here
in
envoy,
which
is
just
specifically
where
I'm
going
to
have
data
written
for
connections
coming
from
this
thing,
and
you
could
set
that
up
with
grpc,
using
a
unix
file
socket
and
just
do
memory
to
memory.
Behaviors.
D
B
There's
a
lot
of
interesting
possibilities
once
you
get
to
that
stage
where
you
actually
have
a
structured
way
to
dynamically
set
up
shared
memory
between
a
pod
that
didn't
exist
before
and
an
envoy
that
might
not
even
have
existed
when
the
pod
started.
You
know,
so
you
don't
have
to
to
bind
the
life
cycles
together
and
you
can
in
the
same
way
set
up
controlled
memory
sharing
and
by
control
memory
sharing.
What
I
literally
mean
is.
B
B
B
B
D
A
Those
things
oh
yeah,
it
definitely
is
a
thing
and
we
have
a
couple
of
different
efforts
underway
mostly
around
like
security
and
policy
type
of
aspects
of
it,
and
so
not
all
that
I
can
really
go
into
in
detail
there.
But
we
are
definitely
involved
in
in
a
couple
of
different
aspects
of
service
discovery
and
tying
it
back
into
security
policies
that
we're
defining
across
the.
A
D
Trying
to
think
I'm
trying
to
formulate
a
follow-up
question
that
isn't
too
inquisitive
yeah.
I
got
it
god
I
got
it
well.
Let
me
ask
of
the
do
you
know
of
the
investigations
that
are
going
on
there
is
that
on.
Has
the
the
service
mesh
of
choice
been
been
made,
or
is
part
of
that
proof
of
concepts
across
different
ones?.
D
D
A
Case
without
you
know
giving
too
much
detail
it's
you
know.
I
think
it's
probably
pretty
obvious,
but
you
know
we
are.
You
know
we,
we
kind
of
connect
the
merchants
to
the
banks,
sort
of
our
business
model
and
so
a
lot
of
what
we're
doing
to
do
with
you
know.
How
do
we
connect?
You
know:
secure
transactions
across
different
regions
of
the
water,
we're
sitting
in
and
connect
them
securely
back
to
the
banks.
D
E
From
from
my
side,
so
we've
been
working
a
lot
on
the
network
service,
mesh
effort
on
deployment
of
using
it
inside
of
our
network
for
some
of
our
network
characteristics
or
network
behaviors.
We
made
good
progress,
so
we
might
update.
Actually,
I
did
updates
of
this
a
while
ago
on
on
light
reading
or
something
so
I
can
go
with
this.
I
can.
I
could
follow
up,
I'm
really
interested
in
the
udpa
effort
trying
to
normalize
the
way
enough.
E
One
thing
we're
really
also
interesting-
and
this
is
where
the
proxy
or
proxy
last
functions
comes
in
is
we
are
doing
a
lot
of
effort
of
trying
to
get
better
behavior
network
patterns
out
of
the
applications
and
vice
versa.
How
can
an
application
make
requests
or
define
its
requirements
from
the
network
perspective
in
a
seamless
way,
and
vice
versa,
and
it's
there
and
there
does
it
where
we're
actually
looking
at?
E
B
E
But
no
that
some
people
you
just
can't
reach
so,
but
so
going
back.
So
I
we
do
have
a
lot
of
work
on
going
with
network
service
mesh,
trying
also
to
look
at
augmenting
like
adding
more
capabilities
of
the
application
awareness
so
that
we
can
create
those
patterns.
That's
something
which
there's
a
working
group
in
itf,
which
is
called
application.
Aware
networking
and
it's
a
lot
of
fun
to
think
about
protocols
and
new
extensions
to
standards.
E
E
B
B
Yeah,
I
I
once
pissed
a
solution,
pitched
a
solution
to
a
problem
at
somebody
where
they
I
went
into
a
meeting
and
everybody
savaged.
My
idea-
and
I
I
said
look
this
is
all
true
and
you
missed
the
five
things
that
suck
worst
about
this
idea,
but
it
is
literally
the
only
idea
on
the
table
that
can
be
deployed
in
under
five
years.
E
Yes,
so
that's
where
we're
at
on
the
various
versions
of,
if
you
don't
think
about
service
mesh,
the
other
various
versions
of
service
meshes
that
we
we
have
looked
at
or
we
have
well.
We
have
a
lot
of
deployments
using
istio,
not
necessarily
because
this
two
is
the
right.
One
is
because,
most
of
the
time,
the
one
that
comes,
pre-packaged
and
managed
in
a
like
in
the
cloud
platform
is
the
one.
Is
this
one?
E
E
So
there's
a
lot
of
angles:
there's
a
if
you
go
from
the
itf
perspective.
Most
of
it
is
around.
Can
we
do
like
something
with
an
ip
packet
or
a
header
that
gives
us
gives
the
intent
of
what
needs
to
be
happening
for
an
application,
and
then
the
network
behaves
based
on
this.
That's
the
traditional
protocol
view
of
something,
but
if
you
start
to
look
more
like
annotations
or
labels
or
whatever
we
have
selectors
we
have
in
in
cloud,
I
think
there's
a
way
of
doing
it
without
having
to
add
another
protocol.
E
I
think
there's
ways
of
doing
it
from
like
a
more
metadata
type
information.
So
that's
my
end
goal
to
it,
but
the
application
networking
right
now
is
mostly
focused
on.
How
do
we
do
the
extensions
as
a
protocol
layer,
for
example,
having
a
pod
that
injects
something
into
a
not
buy
up
at
an
ipv6,
so
that
then
gets
tied
back
and
remapped
into
into
the
network
behavior.
So
that's
the
standard
way
of
thinking
things
me,
I'm
kind
of
more
the
proponent
of
a
well
f5
something
I
can
do
like
nsm.
E
E
D
How
dare
he,
I
think,
I
think
we
have.
We
have
availability
on
the
schedule,
for
you
know
the
one
two
weeks
from
now
and
okay,
so
the
29
didn't
this?
Is
you
please
anyone
else?
Some
comment
here,
just
you
know
from
for
my
part
like
in
some
respects
the
the
short
version
of
of
this
talk
is
kind
of,
especially
if
it's
a
10
minute
talk
like
this
is
you
know,
and
the
ability
to
sort
of
ask
him
in
and
around
where
that's
headed
and.
D
So
daniel
to
follow
on
that
last
conversation
about
application,
aware
networking
the
part
of
the
I
don't
know
part
of
the
perspective
from
which
I've
been
considering.
These
types
of
capabilities
have
been
well
envoy,
filter,
well,
web
assembly,
centric
in
nature
and
sort
of
envoy
filter
or
in
context
of
onward
filters.
D
They
don't
have
to
be
envoy
actually
filters
actually,
but
the
the
the
link
to
this
image
hub
is
it's
a
sample
application
that
was
presented
at
dockercon
and
is
just
a
actually.
We
delivered
some
advanced
istio
training
through
o'reilly
yesterday
and
used
this
sample
app
to
help
enlighten
students
of
the
course
about
possibilities,
application
centric
possibilities
about
about
the
intelligence
of
the
data
plane
and
maybe
some
application
infrastructure.
D
If
I
can
use
if
I
can
use
that
term
application
level,
infrastructure
that
can
be
handed
off
to
intelligent
filters
and
I'll
clarify
and
differentiate
between
sort
of
the
the
distributed
systems,
infrastructure
concerns
that
melt
off
melt
off
of
application
code
when
deployed
on
a
service
mesh.
I
think
that
there's
a
lot
of
value
and
promise
in
a
service
mesh
in
that
regard.
D
If
you
take
that
one
step
further
and
say
not
only
can
you
hand
off
can
developers,
in
the
application
code,
hand
off
retries
and
some
circuit
breaking
and
yada
yada
and
so
on
to
the
infrastructure
to
the
service
mesh
layer.
But
so
too
can
they
potentially
hand
off
some
other
application
infrastructure.
D
D
D
D
B
Yeah,
I
I
did
this
this
pre-recorded
months
ahead
of
time
is
really
getting
to
me
as
well.
I
mean
I
we've
got
a
little
bit
more
time
than
that
for
for
kubecon
a
little
bit
more
lead
time,
but
it's
it's
brutal
plus.
You
know,
admittedly,
that's
partially
because
of
personal
habits
like
the
fact
that
the
vast
majority
of
my
conference
talks
serving
at
three
and
the
day
of,
but
still
so.
C
I
was
recording
for
open
source
summit
this
last
weekend
and
that's
what
I
thought
to
the
person
that
was
there
for,
for
the
video
recording,
like
you
know,
in
the
end
going
live,
is
so
much
easier.
I
mean
I
don't.
I
don't
know
why.
But
at
least
for
me
it
was.
It
was
easy,
you
just
prepare,
you
go
and
talk,
and
then
you
meet
people.
B
Yeah,
I
I
I
think
I
I'm
100
with
you
there.
I
I
just
I
I
I
I
do
actually
miss
live
events.
I
don't
miss
the
travel
involved
with
them.
I'm
not
a
happy
traveler,
but
I
do
this
seeing
people
I
do
miss
giving
live
talks
all
the
sort
of
stuff
that's
attendant
to
live
events
that
doesn't
involve
an
airplane.