►
From YouTube: Envoy Community Meeting - 2018-05-08
Description
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
Join us for KubeCon + CloudNativeCon in San Diego November 18 - 21. Learn more at https://bit.ly/2XTN3ho. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
A
B
C
C
No
okay,
all
right,
let's
see
so
I
guess
tweaking.
C
Stuff
like
this
will
be
pretty
short,
so
you
know
we've
been
trying
to
do
obviously
various
things
to
make
the
the
documentation
better
and
the
problem,
of
course,
that
the
documentation
serves
a
bunch
of
very
different
audiences
there's
people.
You
know
that
are
relatively
comfortable
with
the
concepts
and
and
can
use
it
more
as
a
reference
guide.
There's
people
that
come
to
it
and
you
know
don't
don't
know
where
to
get
started.
So
we
have
funding.
You
know,
there's
CN
CF
to
pay
documentation,
writers
to
go
through
and
and
basically
do
whatever.
C
D
Hey
that's
Nikolas,
so
one
thing
that
I've
noticed
from
being
in
the
back
channel
is
one
of
one
of
the
big
areas.
Is
there
aren't
a
lot
of
example,
use
cases
for
envoy
and
either
in
the
repo
or
published
on
the
docks
that
are
that
have
enough
of
the
feature
set
that
people
could
actually
reference
those
instead
of
asking
in
clocks,
so
that
might
be
one
area
in
which
documentation
could
be
improved.
Do.
C
C
There's
someone
that's
theoretically
working
on
getting
those
over
to
2,
v2
I
guess
do
you
feel
that-
and
this
is
kind
of
my
feeling
too,
is
like
if
we
paid
someone
just
to
basically
go
through
and
like
get
those
documentation,
z'
converted
to
llamo
and
then
maybe
even
comment
the
documentation
or
comment
the
configs
like?
Do
you
think
that
would
help
as
kind
of
like
having
a
more
complete
example
set?
Or
do
you
feel
that
we
need
like
a
mock
management
server
and
like
the
full,
like
the
full
end-to-end
thing.
E
So
this
Dave
Wallace,
so
as
someone
who's
just
recently,
you
know
gotten
up
to
speed
on
envoy
and
gone
through
the
collateral,
I
kind
of
want
to
say
both,
but
I
would
start
by
converting
I.
Think
the
conversion
of
the
examples
to
v2
is
probably
you
know,
low-hanging
fruit,
a
good
place
to
get
started.
The
other
thing
that
I
found
is
that,
like
last
week,
I
spent
a
lot
of
time
just
going
through
the
blog
and
reading
all
the
blog
posts,
and
that
really
did
the
most
outside
of
the
code
to
fill
in.
C
It's
just
like
this
is
this
is
a
super
tough
thing
and
I'm
just
gonna,
be
totally
honest
because,
like
I
at
certain
times
with
the
documentation,
stuff,
I
feel
kind
of
lost
because
I
feel,
like
you
know,
I
would
like
to
find
someone
to
pay
to
basically
work
on
this,
but
every
time
we
try
to
do
that,
I
feel
like
I,
have
to
basically
manage
that
person
almost
full-time
at
which
point
I
can
write
the
documentation
myself
so
much
more
efficiently.
That
I
just
go
off
and
do
that
for
two
weeks.
C
So,
like
part
of
this
is
even
just
me
like
desperately
asking
you
know-
and
you
don't
do
this
now
but
like
if
any
of
you
offline
I,
think
we're
just
looking
for
people
that,
whether
it
be
as
a
hobby
or
they
want
to
make
some
money
or
they,
they
just
want
to
learn
they're
like
technical
enough
that
they
can
understand
all
the
concepts
but
they're.
Also
a
good
writer,
and
the
problem
is
that,
like
that,
is
such
a
small
intersection
of
people
that,
like
trying
to
find
that
person
is
like
so
complicated.
C
So
you
know
I
I
totally
agree.
It's
like
we
need
more
examples
like
we
need
better
cross-linking.
We
need
honestly
someone
just
to
go
through
the
existing
documentation
and
look
for
inconsistencies
and
like
do
more
cross-linking
and
various
things,
and
maybe
that's
a
place
to
start
from
a
contractor
perspective.
Yeah.
E
C
E
Yeah,
it's
it's
it's
well,
and
you
know
the
problem
is:
is
software
developments
at
River
and
so
yeah
the
the
biggest
problem?
You
know
we've
had
the
same
thing
with
with
phyto
and
VPP.
Is
you
know
so
much
of
our
documentation
is
now
two
years
old
and
we're
two
and
a
half
years
into
the
open
sourcing
of
it.
And
you
know
we
constantly
getting
references
to
oh
yeah.
Well,
you
know
sorry,
but
that's
referencing,
really
old
dead
code
yeah.
Some
Arkham
is
a
perennial
problem.
Yeah.
F
I,
haven't
you
about
the
whole
example
part
so,
like
Nicholas
was
saying,
we
have
seen
a
lot
of
questions
come
up
and
dislike
channel.
This
is
more
for
beginners,
where
it's
like.
You
know
how
do
I
set
up
mutual
TLS?
How
do
I
set
up
circuit
breakers?
How
do
I
set
up
all
this
stuff
and
my
idea
there
would
be
if
we
get
a
contractor
for
them
to
comb
through
slack
the
Android
users
Channel
and
get
all
this
scenario
stuff,
like
people
have
been
asking.
F
How
do
I
set
up
ABC
and
then
write
up
guides
like
like
we're
in
for
the
examples
with
a
with
the
front
proxy
and
a
service
service
proxy?
The
other
idea
I
have
there
and
you
know
you're
asking
about
how
do
we
find
someone
that
is
a
technical
enough
and
a
good
writer
and
I
mean
I'm,
not
sure
about
how
this
would
work,
but
with
Brooke
and
the
learn
Android
dot
IO
she
I
mean
she's
written
a
lot
of
very
good
documentation
there
and
I.
Don't
know
how
to
vine.
C
F
C
We've
been
through
that
offline,
so
that's
it's
not
something
that
I
think
would
be
good
to
discuss
here
so,
but
but
yes
like
we
can.
We
can
look
into
that.
The
other
idea
that
I
had,
but
this
would
again
require
work,
is
we
actually
have
a
mountain
of
config
snippets
that
are
in
in
the
tests
and
one
one
thing
that
did
occur?
Jim
is,
and
this
would
be
more
of
a
development
tasks
like
a
development.
C
So
that's
that's
another
area
that
I
thought
of
may
be
trying
to
pursue
just
because
again,
like
across
almost
every
feature.
We
have
lots
of
example.
Configs
that
I
feel
like
would
be
more
helpful
if
they
were
linked
into
a
particular
section.
So
that's
something
else
that
kind
of
occurred
to
me.
I
I
can
I.
C
Can
get
that
going
or
at
least
think
about
that,
but
yeah
so
yeah
I
mean
we
can
talk
to
the
turbine
people
more
but
again,
there's
there's
some
corporate
interest
there
so
that
you
know
a
lot
of
that's
not
gonna
get
contributed
back
so
there's
things
that
are
that
are
at
odds
so
anyway,
I
mean
unless
other
people
have
like
happy
to
keep
the
discussion
going.
If
there's
other
ideas
that
people
had
but
I
mostly
just
wanted
to
put
put
it
out
there
that
we're.
E
E
A
C
A
great
right,
no
I,
think
you're
exactly
right.
Yeah
and
I
I
think
that
we're
gonna
have
to
put
more
effort
in
so
I.
Think
you're
right
that,
like
doing
like
an
outline
or
even
targeting
specific
cases
that
we
know
are,
are
rough
I
feel
like
there's
two
major
points.
There's
that
there's
the
general
introduction
of
concepts.
So
that's
you
know
something
where
it
might
be
difficult
to
actually
get.
C
So
you
know
one
one
thing
would
be
to
like
look
into
having
a
programmer
pay
someone
to
build
a
little
framework
where
again
either
import-export
one
one
way,
the
other
like
tag.
The
ability
to
have
these
snippets
come
in
and
out
of
the
code
and
the
Docs
and
then
print
them
in
such
a
way
that
they're
useful
so
but
yeah
I
think
that
I
or
someone
else
is
probably
gonna-
have
to
sit
down
and
carve
out
several
days
of
time
to
do
like
an
outline
of
what
we
need.
C
B
C
E
So
you
know
iterating
through
well,
so
there's
there's
a
couple:
a
couple
of
high-level
issues.
One
is
I'd
like
to
make
sure
that
we've
got
all
the
requirements
captured
before
I
try
to
do
too
much
moving
forward,
and
so
in
particular
the
EBP
F
I
haven't
seen
any
input
from
the
Sicilian
guys
and
so
I
don't
know
who
would
be
working
on
that
I.
C
E
E
The
use
of
the
of
the
POSIX
socket
calls
our
kind
of
ad
hoc
right
now.
Some
of
them,
you
know,
are
done
directly
by
just
referencing.
You
know
sis
socket
dot,
H
and
making
calls
and
linking
stuff
in
there
there's
a
couple
other
places
where
there's
some
socket
options:
stuff,
that's
not
complete.
There's
some
there's
the
OS
singleton
hat
contains
like
bind
and
getting
set,
saw
copped,
and
so,
as
I
was
looking
at.
You
know
how
to
address
this.
E
It
really
seems
like
the
mo
most
pragmatic
way
to
move
forward
would
be
to
try
to
consolidate
all
that
into
you
know,
really
kind
of
a
network
service
or
network
socket
singleton
that
we
could,
then
you
know
replace
all
of
the
ad-hoc
calls
to
through
SIF
socket
through
that
singleton,
and
then
we
can
look
at
you
know
for
for
VCL
VPP,
we've
modeled
our
PII
after
the
socket
interface.
So
that's
kind
of
trivial
for
us
to
do.
Yeah.
E
C
B
C
B
E
Agree
agree:
it's
just
well,
the
alternative
is
try
to
embed
the
I
mean
we've
got
kind
of
like
transport
socket,
which
is
almost
a
different
layer,
and
then
we've
got
the
socket
class.
That's
used
in
in
the
addressed
instance,
and
so
those
have
some
Sark
X
Akkad
characteristics
in
it,
but
they
don't
provide
a
clean
place
to
put
in
a
factory
we'd
end
up
generating
multiple
factories
for
each
of
the
derivatives
and
that's
kind
of
where
I
got
lost.
E
C
It's
not
I,
you
know,
I'll
be
totally
honest.
It's
not
completely
obvious
to
me
without
getting
there
getting
in
there
and
actually
doing
the
work,
I
I,
what
what
I
would
do,
I
I,
think
just
to
move
forward
and
get
the
conversation
going
is
like
I
would
start
a
branch
and
I
would
just
delete
the
the
FD
function
and
then
and
then
just
like
start
working
backwards
and
like
seeing
how
it
flows
and
then,
if
you
get
stuck
just
like
push
a
branch
and
then
we
can
basically
talk
about
it.
C
Yeah
like
I
I,
don't
I,
don't
I,
guess
I,
don't
see
any
way
forward
other
than
just
doing
that,
lifting
you
know-
and
you
know
it
it'll-
be
scary
in
the
sense
that
you're
gonna
have
to
change
a
bunch
of
stuff,
but
I
actually
don't
think
it's
a
very
scary
change
like
it's
more
factoring
in
code
movement.
So
like
it's,
not
it's
not
your.
G
B
E
E
C
E
I
mean
part
of
it
is
the
socket
API
itself
is.
Is
you
know
so
historical
in
nature
that
it's
a
mess
to
begin
with?
So
you
know
it's
where,
like
I
ran
into
a
case
where,
on
the
client
side
you
know
bind
was
being
called,
we
don't
have
to
bind
on
the
client
side.
I
mean
I'll
I'll
push
a
PR
to
clean
that
up
anyway,
so
you
just
don't
need
to
do.
It
doesn't
hurt
anything,
but
you
know
there's
just
it's
not
clean
anyways,
so
it
it's
highly
understandable.
E
G
C
You
run
it
now.
Are
you
want
people
to
email?
You,
oh
okay.
Anyone
out
there
have
any
coupon
feedback.
F
I
have
general
positive,
positive
feelings,
good
good
conference,
good
conversations,
a
lot
of
community
engagement
I,
particularly
like
to
meet
the
maintainer
section,
because
people
had
the
opportunity
to
come
and
ask
questions
that
they
might
have
not
had
the
opportunity
to
ask
you
know
face
to
face
which
always
helps
so
that's
that's
my
feedback.
I.
C
G
C
I
had
a
couple
of
pieces
of
feedback
I
think
that
for
the
project
deep
dive
sessions,
it
would
be
nice
to
have
longer
sessions.
35
minutes
was
just
too
too
short.
I
just
felt
like
it
was
very
rushed
like
trying
to
have
conversation
so,
like
I,
totally
understand
why
the
main
track
talks
are
3035
minutes,
but
I
feel
like.
We
should
have
a
way
of
either
doing
double
double
blocks,
for
project
sessions
or
or
something
like
that.
C
Just
so,
it's
not
not
so
rushed,
and
then
I
also
felt
like
it
least
from
the
project
session
perspective.
It
would
be
nice
to
be
able
to
do
like
more
variety
of
things.
So,
for
example,
it
was
really
fun
to
do
lightning
talks,
but
I
also
wanted
to
do
like
a
whole
Q&A
session,
so
I
feel
like
making
it
bet.