►
From YouTube: Envoy Community Meeting - 2018-07-31
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
C
C
The
first
part
happens,
but
that's
like
I
just
need
to
like,
but
then
telling
jump
on
stuff.
That's
yeah,
that's
fine,
like
I
know,
that's
no
different
than
I,
don't
know,
but
yeah,
it's
like
sort
of
after
that.
I
feel
like
I
end
up
bugging
you
all
the
time
for
them,
yeah
and
I.
Think
other
folks,
just
kind
of
like
I,
don't
know
anything
about
thrift,
so
I
don't
want
to
look
at
it
or
maybe
it's
not
quite
bad,
but
I
mean.
A
I'm
gonna
be
totally
honest,
like
I
I,
mostly
just
skim,
it
I
mean
just
just
to
you,
know:
I'm
not
like
doing
like
a
deep
code
review,
so
I,
don't
yeah
I,
don't
really
know
what
to
do
just
in
the
sense
that
I
suppose
like
github,
won't
won't.
Let
you
review
it
where
that
other
site
won't,
let
you
submit
it
without
at
least
someone
clicking
the
button.
So
even
if
it's
even
if
it's
a
rubber-stamp,
that's
that's
fine,
I
guess.
A
One
of
the
things
that
we
could
discuss
is
like
a
general
policy
where,
if
one
of
the
maintainer
z'
is
basically
building
the
extension
and
they've
gotten
a
code
review
from
someone
else,
who's
a
domain
expert,
one
of
the
other
maintainer
x',
can
literally
just
give
it
like.
Like
a
three-minute
skim
rubber-stamp,
merge,
I,
don't
I,
don't
really
have
a
problem
with
that,
but
that's
probably
worth
discussing
yeah.
D
E
D
A
You
know
and
that's
something
where
I
think
that
we're
gonna
have
to
evolve
once
that
actually
happens.
We're
not
we're
not
quite
there
yet,
but
yeah
III
think
that
there
has
to
be
some
rubber-stamp
just
in
the
sense
that,
like
one
of
the
nice
things
about
the
extension
policy,
is
that
for
organizations
like
lyft
and
like
Google
and
like
other
people
that
don't
use
thrift
like
one
of
the
beautiful
things
about
this,
is
that
I,
you
know
like
I
know
that
I'm
not
going
to
compile
that
code.
A
So
my
like
my
caring
level,
honestly
of
like
what
happens
within
it
is,
is
less
than
a
change
to
the
core
code,
so
I
think
from
a
rubber-stamp
perspective,
even
just
skimming
through
to
double-check
that,
like
nothing
accidentally
leaked,
you
know
like
from
the
extension
to
the
core
code
and
like
should
that
have
been
in
a
separate
PR
or
something
like
that.
So,
like
I
I,
think
that
makes
sense
so
I
guess
maybe
what
I
would
suggest
is.
A
Could
you
take
a
look
at
the
verbiage
that
I
wrote
in
that
doc
for
the
existing
policy
and
then
maybe
just
propose
some
changes
to
it?
That
would
make
it
easier
for
you
to
go
into
the
current
maintainer,
x'
chat
and
just
say:
hey
can.
Can
someone
like
right
now
today
in
the
next
two
hours,
just
like
skim,
this
and
and
rubber-stamp
yeah,
maybe.
A
Exactly
yeah
sure
guys
does
that
work
like
is
that
oh
yeah,
okay,
all
right
great
yeah
yeah,
because
we're
we're
gonna,
be
you
know
in
similar
situations
soon,
in
the
sense
that
the
the
people
from
the
double
RPC
thing
just
opened
and
opened
an
issue.
I
think
they're
gonna
implement
that
protocol,
so
we'll
have
to
figure
out
how
that
works.
Also,
yeah
I
think
it's
a.
A
That,
like
this
is
code,
that's
going
to
affect
every
so,
let's
code
review
it
to
that
standard
and
then
for
code.
That,
basically,
is
only
in
extensions
and
just
kind
of
like
riffing
on
this
and
thinking
more
for
the
mythical
bots
which
we
don't
have
like.
This
would
be
very
easy
to
actually
detect.
So,
like
you
know
a
like,
when
you
open
the
PR
a
balk
and
look
at
the
files
that
are
changed
and
be
like,
is
it
an
extension
only
PR
and
then
actually
tag
it
or
something
like
that?
So
so.
B
A
B
Cool
so
yeah
we
did
have
a
personnel
change
to
harass
you,
we
noted
a
couple
of
meetings
ago,
so
I
wanted
to
do.
Steven,
Blair
Blair
an
opportunity
to
introduce
himself
you'll,
be
picking
up
that
work,
and
you
know
my
understanding
is
that
the
plan
of
record
is
still
to
first
refactor
on
voice
core
to
your
previous
point
about
hi,
singers
of
good
radio.
So
the
extensions
of
that
sort
of
possible,
in
collaboration
with
both
the
QuickBooks
at
Google
and
the
and
the
cilium
guys
and
then
introduced
a
PvP
extension
based
upon
those
extension
points.
B
B
A
B
E
Have
you
heard
me
I
heard
ow
didn't
hear
that
before?
Let
me
turn
my
volume
up.
Sorry
about
that.
Okay,
I'll
start
again,
I'm
a
distinguished
engineer
at
Cisco,
I
Mic,
Check
IDI.
Am
I
doing
all
right
hearing?
Can
you
hear
me?
Yes,
okay,
okay,
I
just
came
back
to
Cisco
after
being
gone
at
a
start-up
for
over
five
years.
E
My
background
is
has
been
in
OS
and
infrastructure
distributed
OS
with
a
my
specialty
is
pretty
much
in
scalability
and
non-blocking
architectures
I
signed
on
to
this
project
a
little
over
a
week
ago.
It's
completely
new
to
me
I.
Actually,
this
whole
space
is
very
new
to
me.
A
cloud
native
working
in
clouds
in
general
I've
done
very
different
stuff
for
many
different
years.
A
Of
record
I
I
think
is
still
the
same
and
I
think
some
work
has
even
been
done
since
we
last
talked
and-
and
that
basically
boils
down
to
right
now
in
certain
parts
of
the
codebase
were
passing
file
descriptors
around
so
in.
In
some
sense,
the
the
initial
goal
is
quote
simple:
it's
it's
mostly
just
you
know
kind
of
relatively
self-contained,
but
wide-reaching
refactorings,
where
we're
gonna
hide
that
file
descriptor
behind
some
type
of
interface.
A
B
A
Yes
and
that's
it
and
that's
exactly
what
I
would
do
and
and
weekend
once
you
start
to
make
progress,
we
can
you
know
we
can
figure
this
out,
but
in
general,
we'll
ask
for
incremental
code
reviews,
so
what
we'll
probably
have
for
a
while
will
have
the
F
D
method
and
this
new
thing
side-by-side
and
we'll
just
incrementally
pick
away
at
pieces,
but
I
actually
don't
think
it's
it's
it's
that
difficult!
It's
just
somewhat
somewhat!
Yes,
once
that
work
is
done,
it
should
let
us
do
all
this
other
stuff
pretty
easily.
Okay,.