►
From YouTube: Envoy Community Meeting - 2018-08-14
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
Let's
see
Oh
a
porky
okay,
oh
wow.
We
have
lots
of
lots
of
agenda.
B
A
B
A
B
Mostly
I
would
like
for
whatever
things
which
are
not
covered
and
interesting,
having
fuzzes
written.
Oh
there
are
other
paths
done
well.
Data
plane
related
whether
we
can
get
a
high
payoff
from
fuzzing.
Please
do
reach
out
to
me
and
I'm
happy
to
consider
adding
such
buzzers
and
or
at
least
getting
over,
learn
about
for
fuzzing.
So
we
know
where
we
can
best
focus
our
efforts
there
going
forward.
That's
that's
just
a
quick
advertisement
there.
A
Sir
sorry,
just
on
that
on
the
fuzzing
thing,
just
just
for
our
offline
conversation,
just
for
everyone's
benefit,
I
I
mean
I
I,
think
you've
done
an
awesome
job
on
getting
all
this
working,
but
I
think
we're
all
on
the
same
page
that
it's
worth
it
at
this
point
just
to
burn
down
the
existing
blogs.
Basically,
is
that
that's
the
plan.
C
B
Weathers
themselves
or
they
eat
integration
or
the
like
intubation
test
flakes
and
that
kind
of
thing
so
Wow.
Hopefully
they
all
just
provide
a
general
improvement.
Just
stability
as
we
address
them,
there's
been
some
interesting
ones
just
pop
up
in
the
last
few
days,
just
movies
I've
had
a
positive
ones
have
come
up.
So
what
we
can.
B
E
B
Yeah,
that's
kind
of
the
plan
is
to
actually
burn
those
down
and
also
understanding
father,
efficacy.
There's
a
lot
of
metrics.
We
can
look
at.
You
include
things
like
you
know
how
there's
no
stability,
metrics,
there's
coverage,
metrics
and
there's
indication
rate
matrix
which
can
be
used
to
guide.
You
know
how
you
want
to
know
a
posit.
You
actually
do
a
better
job
and
actually
making
use
of
some
of
those.
A
B
B
B
A
I
mean
like
we
should.
We
should
definitely
do
that.
I
think
again,
from
from
our
offline
conversations,
you
and
I
are
in
the
same
page
that
Coverity
is
generally
a
sea
of
false
positives,
which,
which
is
a
waste
of
time,
but
I
see
no
reason
not
to
turn
it
back
on
since
I
think
it's
pretty
trivial
to
do
so,
even.
B
That
can
be
used
instead
of
defaults.
You
know
whether
we
want
to
turn
all
these
are
in
the
default,
build
or
not,
maybe
well,
but
who
made
it
may
even
make
sense
to
have
a
hardened
version
of
Envoy.
Where
folks,
you
are,
you
know
using
this,
for
example,
in
edge
applications
versus
internal
applications
where
traffic's
largely
trusted
it.
No
overtime
that
make
sense,
is
else
or
other
things
that
I
could
be
using
to
explore,
for
example,
cutting
out
of
Envoy
things
which
aren't
necessary.
B
Could
you,
you
know,
make
codecs
optional
or
to
support
most
of
the
interesting
ones,
I
think
they're
places
where
we
can
reduce
dependencies
and
party
software
and
data
plane,
because
you
know
when
you're
looking
legitimate
security
analysis
of
envoy
homeboy,
just
one
part
of
the
picture
and
in
terms
of
trust,
actually
think
we
have
a
very
healthy
relationship
in
you
know
boy
I
think
most
of
the
contributors
are,
but
most
contributions
have
are
systematically
reviewed
by
people
who
I
think
most
of
the
people.
Novel
community
vulture
would
trust
other
projects
I.
B
Don't
the
same
understanding
I
know
some
of
these
products,
most
of
other
pendants
ease
by
the
good
rule,
originated
or
using
many
other
places,
but
beyond
that,
actually
understanding
the
nature
of
the
communities
and
how
easy
would
be
for
exports
just
sneaking
to
them.
I
don't
have
as
good
a
feel
for
yep.
B
Very
easy
to
give
in
their
locker
examples,
I
actually
plan
on
writing
up
my
medium
post
on
fuzzing
in
the
know,
in
the
coming
few
weeks,
and
now,
let's
sort
of
explain
the
basics
and
how
to
add
these.
So
if
you
own
an
extension
or
what
I
had
fuzzy
that
will
be
the
place,
that's
what
it
may
be
tickets
to
start
from,
but
it
doesn't.
It's.
A
B
About
an
hour
and
a
half-
and
you
know,
exercises
all
the
Rafflecopter
hands,
you
know
path
matching
stuff
and
that
Deb
L
is
a
pretty
big
waiting
for
a
very
good
C.
So
I
would
generally
encourage
people
who
are
extensions
to
do
that.
I
mean
and
also
people
hit
me
right.
Non-Trivial
data
structures,
so
good
example
might
be
at
the
LC
tried.
I
would
be
a
good
thing
to
France
yeah.
A
A
A
Think
that's
a
good
segue
into
talking
about
compiler
stuff,
because
you
have
talked
about
turning
on
stack.
You
know
stack
cards
and
stuff
like
that,
so
yeah,
so
I
think
Peter
opened
a
PR
just
to
change
the
default
compiler
to
clang.
I
think
this
is
something
that
I've
been
thinking
about
for
a
while.
In
terms
of
do
we
want
to
switch
over
to
clang.
It
seems
like
that's
where
the
industry
is
going
so
I'm
like
I'm,
for
it
I
just
think
it
might
need
a
little
more
thinking
and
diligence
than
just
making
the
change
so.
A
Curious
what
people
think,
but
the
the
three
things
you
know
giving
magical
resources
that
we
might
not
have
that
I've
been
thinking
about,
is
I,
think
we
should
move
from
clang
5
to
clang
6,
so
that
includes
clang
6,
since
it's
now
released,
clang,
6
format
and
so
essentially
upgrading
clang
playing
8
like
should
we
begin
playing
7?
Is
it
clang?
7?
A
Is
the
current
development
version
as
far
as
I
know
so,
clang
6
is
the
last
like
release
version,
I
I
think
it's
what
I
still
playing
8
the
other
day
when
I
wasn't
meeting
some
documentation,
then
maybe
they
just
released
clang
7,
I'm
I'm,
not
I'm,
not
sure,
but
I
know
that
in
a
bunch
of
repos
claim,
six
is
definitely
the
one
that
they
have
and
then
it's
mainline
I
mean
I'm
guessing.
What
you
saw
is
they're,
probably
about
to
release
Clank
seven
and
that's
and
that's
why
it's
switched
to
clang.
B
A
But
we
should,
since
we're
I,
guess
clearly
very
far
behind.
We
should
at
least
switch
to
claim
six,
particularly
because
now
that
they
build
those
Debian
packages
for
a
bun
to
like
it's
super
easy
to
actually
upgrade
so
I
think
we
should
do
that
on
the
other
thing
that
I
saw
then
so
I
guess
they're
switched
to
Clank
six
or
Clank
seven
there's
whether
we
want
to
switch
the
default
builds.
A
A
Well,
we
can't
ride
in
the
FLT.
Oh
so
you
don't
so
there's
there's
two
separate
things
so
FLT
o
is
just
whole
program,
optimization
without
without
any
training
and
then
there's
the
there's,
the
PG,
oh,
the
profile,
guided,
optimization,
so
I'm,
just
proposing
turning
on
FLT
Oh
or
at
least
experimenting
with
it.
The
reason
just
just
for
historical
context.
The
reason
that
envoy
has
not
historically
used
F
LTO,
as
that
at
least
adds
up
about
three
years
ago.
A
Gcc
has
historically
had
problems
with
debug
symbols
when
FLT
o
is
on
so
life,
the
code
might
be
faster,
but
then,
if
you
look
at
a
core
dump
like
symbols
and
call
stacks
are
all
messed
up.
I'm
guessing
that's
been
fixed
now,
but
I
honestly
haven't
looked
at
this
in
several
years,
so
you
know
it
would
be
worth
just
looking
into
like
what
does
f
LTO
do
for
like
a
standard
performance
run
a
beast
for
some
for
some
real-world
use
cases.
Does
the
core
dump
look
correct
like?
Can
you
debug
it?
A
Basically,
so
those
are
the
three
things
that
I've
been
thinking
about.
Are
there
things
that
other
folk
have
been
thinking
about.
B
B
What
is
do
and
by
implication
envoy,
isn't
scaling
practically
and
so
Peter
and
Lisa
and
so
on,
are
engaged
right
now
and
a
bunch
of
work
on
kinda
gets
the
root
of
this,
and
one
of
the
things
did
end
up
being
an
Elsi
try
and
it
was
sort
of
solved
by
switching
to
clang
but
yeah.
That
thought
that
is
just
some
background
context
in
terms
of
the
actual
things
to
actually
consider
tuning
on
yeah
I
think
these
are
all
interesting.
Well,
one
thing
we
really
would
benefit
from,
and
this
is
a
lot
of
work.
B
So
I
don't
think
this
is
going
to
happen
overnight
and
maybe
not
at
all.
It's
a
way
to
systematically
make
these
decisions
by
having
an
open
source
performance
framework
for
envoy
and
I.
Agree
like
these
are
the
tests
we're
on.
We
saw
this
regression
of
five
percent
or
improve
above
10
percent
angry.
So
that's
like
the
rational
thing
to
do.
Building
that
out
is
a.
A
Lot
of
work,
yeah
and
and
and
that's
something
I
would
I,
would
love
to
work
on,
and
maybe
sometime
in
the
future,
I
will
do
that,
actually,
ironically,
getting
musical
machine
resources
to
do.
That
is
actually
not
a
problem,
because
CN
CF
has
a
test
cluster
so
like
we,
we
we
have
computers
and
a
network
that
we
could
use
to
actually
do
such
a
thing.
Obviously,
building
the
thing
with
like
how
you
deploy
and
like
actually
monitor
and
do
all
those
things.
That's
like
a
multi-month
effort.
A
Community
cares
about
like
this
is
a
yeah
right,
so
the
best
that
we
can
do
currently
to
be
honest,
is
you
know,
I
think
when
we
make
some
of
these
changes
like
lift,
we
can
do
some
basic
performance,
anity
checks.
It
seems
like
the
folks
over
a
Pinterest
generally
do
perform
like
they
can
test
some
things
like
once,
Google
is
using
it
more
production
like
you'll,
be
able
to
run
run,
run
some
benchmarks.
We.
B
A
A
The
other
high-level
comment
that
I
would
say,
which
is
probably
obvious
to
people,
is
that,
like
with
with
regard
to
sto
and
people
using
thousands
of
listeners,
you
know
I
would
say
that
sometimes
some
of
the
use
cases
I
would
not
consider
reasonable
so
like
on
Boas
not
being
used
in
a
reasonable
way.
So
there's
there's
like
there's,
there's
performance,
fixes
that
we
should
investigate,
but
that
doesn't
mean
that,
like
every
benchmark
that
people
say
is
slow
means
that
we
have
to
change
the
world.
Like
that's
my
that's.
B
A
Like
all
the
services
to
all
exactly
I
told
them
this
many
times
like
they
cannot
do
what
they're
doing,
but
but
they
do
it
anyway,
so
I'm
just
I'm
just
making
the
point
that
I'm
not
opposed
to
performance
fixes.
We
should
absolutely
do
that.
I.
Just
think
that
we
have
to
look
at
the
big
picture,
which
is
that,
like
we,
you
know
in
in
helping
people
use
on,
but
we
have
to
also
help
them
use
it
in
a
reasonable
way.
That's
my
only
point
yeah.
A
That's
so
like
I,
don't
I
feel
like
with
Peters
PR
I,
don't
I,
just
don't
feel
like
enough.
Diligence
has
been
done
so
I
would
still
propose
that
we
close
it
and
open.
Another
tracking
issue
on
like
upgrade
clang
try
to
get
some
input
on
people
testing
clang
in
in
some
production
environment,
to
look
for
like
obvious
regressions
and
then
maybe
at
some
point.
A
I
are
someone
else,
can
do
some
investigation
on
FLT
go
and
determine
whether
we
want
to
turn
that
on
or
not
those
are
and
then
I
think
in
there
too,
we
can
talk
about.
Do
we
want
to
turn
on
the
stack
guards?
Maybe
look
at
the
perf
Delta
for
that,
like
there's
a
couple
other
things
I
see
no
reason
personally,
like
I,
feel
like
the
docker
image
that
we
export
from
the
project
should
be
a
security
hardened
as
possible
at
the
expense
of
perf.
A
B
A
A
F
A
Baked
in
like
we,
we
download
from
the
Debian
repo
and
we're
using
clang
five
now
so
I
think
just
like
switching
declined.
Six
is
a
total,
no-brainer
and
I.
Think
I
think
Peter
has
a
PR
for
that
somewhere.
So
we
should
just
do
that
like
that
that
one
is
just
easy.
So
let's
just
do
that
and
then
I
think
whether
we
switch
the
release,
docker
image
to
clang
I
think
that's
an
open
discussion
and
then
obviously,
these
other
compile
flags
like
FLT,
oh
and
stack
guards
and
whatever
I
feel
like.
D
A
D
A
C
G
A
G
G
A
I
mean
if
there's
some
RFC,
let's
that
sounds
good.
Let's
definitely
look
at
that.
I
do
think.
We
have
to
consider
some
existing
places
like
X
FCC,
where
we
are
doing
this
and
I
mean
it's
fine
like
we
can
just
call
that
header
legacy
or
something
and
we're
gonna
do
this
new
version
or
we
can
have
a
option
that
does
old-style
and
then
the
and
then
the
standard
or
something
yeah,
okay,
I
guess,
can
we
Luke
pewter
and
into
that
issue.
A
I
think
I
think
for
Mike
Shores
case
yeah,
it's
it's
problematic,
because
what
he
wants
to
do
is
going
to
require
changes
and
lifts,
client,
apps
and
obviously,
once
we
roll
that
out.
That's
a
giant
pain
to
change.
E
A
G
F
F
A
F
A
A
Like
while
we're
while
we're
on
this
topic,
one
thing
that
I
would
love
to
we're
kind
of
out
of
time,
but
like
one
thing
that
I'd
love
to
figure
out,
maybe
we
can
do
it
over
email
or
something
is
I
feel
like
with
the
integration
tests.
In
particular,
we
need
to
have
some
like.
We
should
have
some
guide
around
like
how
to
test
it
before
submitting
it
just
because
that
likes,
but
anyway,
we
could
talk
about
that.
Next
time,
yeah.