►
From YouTube: Lightning Talk: Who is Envoy - Harvey Tuch, Google
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
Lightning Talk: Who is Envoy - Harvey Tuch, Google
An analysis of Envoy source code, contributors, history and evolution, providing insight into the trust relationships in the community, who is developing, reviewing and approving changes. What the Envoy developer dynamic looks like, a quantitative state-of-the-union.
A
So
good
morning
on
my
car,
I'm
Harvey
I
work
at
Google,
where
I'm
a
contributor,
maintainer
and
today
I'm
gonna,
be
answering
the
question
which
I'm
sure
is
on
a
lot
of
your
lips.
Who
is
Envoy?
Okay,
so
what
do
I
mean
by
who
is
envoy?
Well,
the
question
is
like
who
are
the
constituting
companies,
contributors,
organizations,
individuals
behind
the
Envoy
projects,
and
why
would
you
even
care
about
this
question?
Well,
there's
a
few
reasons.
First
is
understanding
the
business
context
you
know,
like
is
envoy
just
the
work
of
a
single
company.
A
Is
this
a
broad
coalition
of
companies
or
most
developers,
software
professionals,
or
they
probably
asked
until
you
turn
the
one
that
really
got
me
interested-
was
understanding
the
security
dynamic
of
the
omlet
community.
This
idea
and
open
source
that
many
eyes
lead
to
all
bugs
becoming
shallow,
as
we
know
that
isn't
quite
true
from
looking
at
projects
like
open
SSL
and
some
of
the
moral
reason
are
vulnerabilities
there,
which
really
shown
that
if
you
don't
have
a
sufficiently
broad
an
active
review
and
maintain
maintain
our
community,
but
this
can
be
a
problem.
A
Finally,
I
think
it's
kinda
interesting
to
you
understand
what
is
the
governance
model
and
how
is
Envoy
sort
of
continuing
to
evolve
beyond
just
the
core
organizations
not
pointed
out
that
we're
always
on
the
lookout
for
new
contributors
and
maintained,
errs
and
one
of
the
trends
here,
so
we're
gonna
dig
into
this
quantitatively
in
this
presentation,
just
to
start
with
some
logo
confetti.
So
you
can
see
here.
A
Looking
in
the
maintainer
community,
this
is
a
little
more
tight-knit.
This
is
essentially
just
lift
Google
tetra
to
Apple
and
an
independent
used
to
work
it
to
learn,
lab
Steven
and
I.
Think
that
we're
always
in
the
interesting
interested
in
growing
this
community,
but
that's
kind
of
the
state
of
where
it
is
today
so
today
into
this
and
actually
look
at
the
numbers.
I
wrote
it's
a
bunch
of
Python
scripts
which
went
through
the
github
history
to
the
git
graph,
get
some
good
blame
analysis,
some
visualizations
with
med,
matplotlib
and
basically
looks
just
specific.
A
The
sauce
/
tree
and
those
users
who've
made
non-trivial
contributions,
and
this
is
what
it
looks
like.
So
just
looking
at
their
lines
of
code,
which
constitute
envoy
leaders
have
grown
significantly
since
Oh
envoys
open
sourcing
on
github,
which
was
October
2016.
Until
today,
it's
growing
from
roughly
are
over,
maybe
around
25,000
lines
of
code
to
around
a
hundred
and
ten
thousand
lines
of
code,
and
this
rate
of
growth
has
actually
been
accelerating
so
sort
of
like
a
hockey
stick.
A
What
you
can
see
is
interesting
features
in
April
this
year
we
introduced
an
architectural
split
between
the
core
and
extensions,
and
so
you
can
see
that
beige
section
there
starts
to
become
significant,
and
what
this
has
allowed
us
to
do
is
scale
maintain
a
bandwidth
and
review
alongside
the
growth
of
various
parts
of
olive
oil,
particularly
as
a
number
of
extensions.
A
variety
of
extensions
has
increased
and
you
can
see
now
fully
around
a
third
of
the
Envoy
sauce.
A
These
extensions,
which
means
you
could
actually
compile
that
in
and
we
could
have
applied
differentiated
sort
of
levels
of
review
to
these
extensions,
looking
peers
by
own
organization,
I
apologize
for
the
tiny
print
here.
What
you
can
actually
do
is
look
at
these
on
the
schedule
I
also
going
to
zoom
in
on
these,
so
we
can
see
a
little
a
little
more
detail
who
these
organizations
are,
but
just
looking
at
the
shape
of
this.
This
is
the
number
of
PRS
by
organization,
and
what
you
can
see
here
is
a
power
Laura
in
effects.
A
Ok,
so
there's
you
know
Google
and
lyft
by
far
the
most
prolific
in
terms
of
PRS.
There's
a
quite
a
large
longtail
of
other
contributing
organizations.
If
we
zoom
in
and
take
a
look
at
what
these
look
like,
you
can
see.
These
are
some
of
these
ones,
which
I
had
on
that
first
slider
of
companies,
X
square
IBM,
Pinterest,
VMware
and
so
on.
There's
also
a
big
chunk
of
Independence.
A
These
are
folks
who
my
analysis
as
I
was
kind
of
hard
to
find
which
organization
they
belong
to
some
of
them,
weren't,
contributing
officially
on
behalf
of
their
employer.
Okay,
look
at
this
point
lines
of
code
a
similar
kind
of
shape.
What's
interesting,
though,
to
look
at
is
in
that
long
tail,
you
can
see
a
bunch
of
other
organizations
pop
up
folks
like
Alan,
barber
are
data
wire,
solo,
I/o,
together
and
so
on.
These
folks
have
been
making
very
significant
contributions
to
extensions
versus
the
core.
They've,
usually
been
in
a
few
relatively
large
PRS.
A
Looking
at
extensions
in
more
detail,
you
can
actually
see
looking
at
the
long
tail
there.
That
said,
this
is
actually
much
more
prominent
and
you
can
see
in
fact
the
original
shape
where
Google
was
one
of
the
most
significant
contributors.
Actually,
then,
we're
our
only
third
now
and
there's
a
lot
of
folks
in
the
long
tail.
Ok,
so
moving
on
to
just
looking
at
you
know,
what
is
the
actual
composition
of
the
source
tree
looks
like
over
time
and
I.
A
Think
what
you
can
notice
here
is
there's
really
three
phases
in
on
boys
life
to
date
there
is
the
2016
and
before
which
Matt
talked
about,
which
were
the
days
in
which
envoy
was
per
internal
to
lift,
and
it
was
the
early
days
of
it's
open
source,
and
here
it's
just
pink.
That's
there
far
left
there,
then
2017
really
is
the
year
of
sort
of
Google
onboarding
in
the
render
the
initial
growth
of
the
rest
of
the
community.
A
That's
that
big
growth
in
green
there
in
the
middle
and
the
right,
you
can
see
2018,
which
has
been
really
the
year,
the
long
term
and
where
many
other
organizations
have
started
to
make
very
significant
contributions.
And
now
you
know
fully
a
third
of
the
Envoy
sauce
trees
has
been
written
by
or
maintain
a
modified
by
folks
outside
of
Google
and
left
here's
our
sort
of
a
radial
source
map.
So
this
is
just
essentially
like
a
tree
which,
which
is
laid
out
on
a
radial
axis.
A
The
text
is
very
small.
What's
interesting
to
look
at
is
this:
is
it
actually
the
core
the
amount
of
green
and
pink?
It's
mostly
Google
and
left
with
a
few
other
organizations,
and
if
you
zoom
in
you
can
see
some
interesting
things
like,
for
example,
many.
The
oldest
parts
of
envoys,
such
as
like
the
HTTP
connection,
manager
and
codex,
are
really
fully
written
by
left
and
continue
to
be
maintained
by
them.
Other
parts
have
very
significant
Google
contributions.
A
The
statistics
configuration
TLS
handling
and
then
there
are
other
parts,
such
as
the
costs
to
manager
and
upstream
connection
management,
which
had
a
lot
of
contributions
from
other
organizations
working
on
different
load,
balancers
health,
checkers
and
that
kind
of
stuff,
so
extension,
there's
a
lot
more
colorful.
This
is
sort
of
starts
to
move
away
from
that
trend.
You
can
see
this
is
this
big
swath
of
orange
there,
which
is
the
contribution
from
to
show
my
labs
with
a
thrift
proxy.
Another
large
contribution
with
Rob,
Allen,
barbers
and
double
proxy?
A
Is
it
kind
of
interesting
if
you
want
to
make
an
outsize
contribution
to
envoy,
just
upstream
a
RPC
filter
and
you're
guaranteed
a
spot
in
the
hall
of
fame,
because
these
are
actually
very
significant
pieces
of
work?
I
mean
they're,
you
know
in
terms
of
complexity,
they're,
comparable
to
the
HTTP
connection
manager.
Other
parts
have
a
huge
number
of
other
organizations
behind
them,
like
young
staff,
if
liquid
starts
tracing
health
checking
and
so
on.
A
Okay,
so
in
summary,
I
would
say,
there's
a
few
things
are
sorting
you
to
take
away
from
this.
The
first
is,
you
know:
we've
got
to
start
three
phases
of
envoys
history
and
this
accelerating
growth
of
the
actual
size
of
the
codebase
I.
Think
architectural
II.
The
extension
mechanism
is
working
as
intended
and
has
been
great
at
taming.
The
growth
they're,
the
core
continues
to
be
rarely
just
developed
and
maintained
by
those
few
early
organizations
and
the
ones
who
are
most
active
in
the
community.
Extensions
have
a
very
large
diversity.
You
can
think
of
this.
A
A
bit
like
you
do
it's
like,
say
the
Linux
kernel
with
the
core
and
the
driver
trees.
So
most
peers
do
have
eyes
on
them.
From
you
know,
folks,
working
from
this
is
their
day
job
at
these
organizations,
you're
actually
using
on
voice
in
production
and
there's
it's
like
a
long
tail
of
envoys
up
tech
development
up
is
really
I.