►
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2023 in Amsterdam, The Netherlands from April 17-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.
Closing Remarks - Matt Klein, Software Engineer, Lyft & EnvoyCon Program Chair
A
Okay,
I,
don't
have
much
to
say
at
this
point,
but
thank
you.
Everyone
for
coming
some
great
talks.
I
thought
it
was
a
really
good
mix
of
end
user
talks
and
Technical
talks.
So
hope
you
all.
A
Just
wanted
to
reiterate
that
the
project
continues
to
need
help
and
we
need
help
across
a
large
variety
of
domains.
So
not
just
people
with
you
know
deep
networking
expertise,
but
we're
always
looking
for
maintainers
just
across
all
of
the
different.
A
You
know
filters
and
components
that
Envoy
has
now
so
not
just
core
networking,
but
we
have
so
many
different
protocols
that
we
support
and,
as
people
have
talked
about
during
this
meeting,
we
have
a
lot
of
different
security,
related
filters
like
oauth
and
xdoth
and
jot
and
all
of
these
things
and
there's
actually
a
lot
of
domain-specific
expertise
in
terms
of
knowing
how
all
of
those
things
work
and
frankly,
the
main
containers
don't
always
know
how
all
of
these
things
work,
there's
so
many
standards
involved.
A
So
if
your
organization
is
really
passionate
about
things
like
jot
or
whatever
you
know,
we
would
love
even
maintainers
that
are
specific
to
certain
filters.
So
if
you're,
using
particular
protocols
or
particular
filters-
and
you
want
to
maintain
only
that
thing-
that
is
definitely
possible,
so
feel
free
to
reach
out
on
that
side.
A
We're
always
looking
for
people
who
do
release
tooling
and
backboards
so
feel
free
to
obviously
reach
out.
If
you
would
like
to
do
that,
documentation
is
an
easy
way
to
get
involved
in
terms
of
just
doing
fixes
or
doing
examples.
Ryan
has
done
a
tremendous.
You
know
job
with
all
of
our
sandbox
examples.
I
think
we
have
like.
B
A
A
You
can
always
reach
me
and
I'm
happy
to
route
you
to
other
people
so
and
with
that,
thank
you
again
for
our
Diamond
sponsor
tetrate
and
we've
got
a
bit
of
extra
time.
There's
a
couple
of
maintainers
here.
So
just
just
wanted
to
open
it
up
to
see.
If
anyone
has
any
general
questions
that
were
not
covered
previously
and
either
I
can
try
to
answer
them
or
there
might
be
someone
else
here
who
can.
A
So
the
question
is
with
Envoy
Gateway.
You
know
there
has
not
been
a
a
standardized
controller
for
Coupe
and
grass,
and
will
that
change?
You
know
I.
Think
people
are
going
to
have
different
opinions
on
this.
Obviously,
for
better
or
worse,
there's
been
a
large
vendor
ecosystem
around
Envoy
I
can't
speak
for
others.
I
think
that's
been
fantastic.
It's
been
one
of
the
reasons
that
Envoy
has
grown
a
lot,
so
I'm
I'm,
very
thrilled
for
all
the
vendors
that
have
invested
so
much
with
with
Envoy
I.
A
Think
the
flip
side
of
that
in
terms
of
the
large
vendor
ecosystem,
is
that
it
tends
to
be
confusing
for
certain
end
users
in
terms
of
how
you
know
how
they
want
to
approach
the
project
or
how
they
want
to
use
it.
So
it's
both
good
and
bad
and
again
for
better
or
worse.
If
you
go
online
today
and
you
search
for
kubernetes
Ingress,
you
find
blogs
and
blogs
about
nginx
right
and
I
mean
nginx
is
a
fantastic
project.
It's
been
around
for
a
long
time.
I
don't
have
anything
bad
to
say
about
it.
A
With
different
types
of
capabilities,
so
I
think
from
the
project
perspective,
we're
biased.
We
would
like
people
to
use
Envoy
when
they're
using
kubernetes-
and
you
know,
there's
obviously
Synergy
with
the
cncf
ecosystem.
B
A
You
know
we
think
that
can
be
better.
Whether
that
can
be
achieved
with
the
vendor.
Ecosystem
is
a
is
a
different
question
right,
so
I
think
Envoy
Gateway
has
the
potential
to
provide
a
better
out-of-box
experience
for
running
Envoy
on
kubernetes
and
I.
Think
if
we
do
it
well,
we
can
still
allow
the
vendors
to
provide
value
on
top,
so
I
actually
think
that
we
can
get
the
best
of
both
worlds.
A
So
I
am
hopeful
that
Envoy
Gateway
I'm
hopeful
that
in
two
years,
when
you
Google,
you
know
kubernetes
Ingress,
you
see
Envoy
Gateway
right
and
not
the
nginx
controller
right
and
then
I'm
hopeful
that
all
the
vendors
that
today
have
their
discrete
Solutions
are
providing
value.
On
top.
That's
my
that's
my
personal
hope.
Whether
that
will
happen.
I
don't
know.
A
A
The
the
question
is
about
load,
balancer
extensibility,
and
what
why
are
we
trying
to
move
new
load
balancers
into
extensions
I?
Think
Envoy
is
seven
and
a
half
years
old,
and
so
there's
a
there's
a
lot
of
Legacy
in
terms
of
how
the
project
has
evolved
over
time
and
I
think
that
one
in
general
we're
trying
to
move
as
much
as
possible
into
extensions
to
avoid
forcing
everyone
who
doesn't
want
certain
features
to
have
to
take
that
into
their
main
build.
A
So
that's,
that's
one
I
think
we're
just
trying
to
trying
to
have
that
happen
for
also
for
load.
Balancers.
Specifically,
there
are
non-onvoy
based
XDS
clients
now
right,
namely,
namely
grpc
and
grpc,
does
not
want
to
implement
all
the
load
balancers
that
Envoy
offers.
So
by
making
it
an
extension,
it's
much
more
clear
that
it's
an
optional
implementation.
A
A
Questions
about
the
build
system
and
just
about
how
people
do
extensions,
so
this
is
another
one.
That's
been
talked
about
for
years
and
years
and
years
there's
been
an
issue
open,
I
think
for
seven
years
around
like.
Why
does
envoy
not
support
dynamically
loadable
modules?
A
And
you
know
I
mean
it's
like
we
can
talk
about
this
over
drinks,
but
I
mean
there's.
There's
no,
there's
no
easy
answer
here.
Like
static
compilation,
has
a
lot
of
benefits
being
able
to
load.
Dynamic
modules
has
a
lot
of
benefits
and
I.
Don't
think
the
project
is
opposed
to
dynamically
loaded
modules,
but
no
one's
done
the
work
so
clearly
no
one
has
cared
about
it
enough
to
actually
implement
it
Upstream
and
whoever
does
that
would
have
to
deal
with
the
binary
compatibility
issue.
Even
if
it's
just
matching
up
the
shaw.
A
A
Would
like
to
see
more
rust
within
the
envoy
code
base
itself,
but
you
know
that's
not
really
going
to
solve
the
static
compilation
problem
like
that's
its
own,
that's
its
own
compilation
problem,
so
I'm,
not
sure
right,
I
mean
it's
like
I,
I
I
think
there's
pros
and
cons
in
terms
of
being
able
to
write
a
module
and
host
it
on
GitHub
and
have
it
easy
you
know
be
easy
to
plug
in
and
maybe
share
that
share
that
code,
a
bit
better
and
like
I
I
wish.
A
There
was
an
easy
answer
here,
but
there's
there's
not
really.
You
know
if
people
want
about
in
terms
of
dynamic
compilation
or
other
mechanisms,
you
know
I
think
the
project
is
certainly
amenable
to
that.
A
You
know:
I
I
wrote
that
Echo
a
long
time
ago
and
I
mean
as
far
as
I
know.
It
works
fine
right,
I,
I,
don't
think.
There's
been
much
development.
A
What
one
of
the
this
is
me
just
speaking,
but
one
of
the
areas
that
I
think
is
really
cool,
is
that
I
think
there
could
be
a
mash-up
of
the
transcoding
filter
with
the
tap
filter
to
actually
allow
people
to.
You
know,
look
at
actually
searching
for
requests
that,
for
example,
have
protobufs
or
those
kinds
of
things
in
them.
I
think
that's
technically
possible
and
it
would
be
amazing,
so
I
think
there's
work
there.
That
has
not
been
done,
but
it,
but
it
could
be
done.
A
You
know
that
would
be
pretty
cool
and
when
you
couple
it
with
systems
like
backstage
or
other
stuff
that
allow
you
to
do
more,
Hands-On
development
interaction
or
like
the
folks
at
Lyft
have
done
with
a
bunch
of
their
work
on
the
developer.
Offload
I
think
there's
amazing
potential
for
actually
doing
request
and
response
capture
and
doing
other
types
of
things.
B
Great
Luke,
okay,
yeah,
just
to
comment
on
what
we
have
looked
at
Lyft
we've
looked
at
the
tap
filter
in
particular.
For
that
same
reason,
in
the
last
slide,
I
showed
like
what,
if
you
could
turn
on
debug
just
for
the
duration
of
this
request
and
we
kind
of
looked
into
the
doing
a
similar
thing.
But
what
if
you
could
turn
on
like
tap
just
for
this,
so
like
every
single
request
and
response
flowing
through
the
developer,
will
have
enough
like
insight
to
figure
out
what
was
actually
going
wrong.
B
We
it's
like
one
of
those
things
that
we
kind
of
want
to
do,
but
haven't
gone
around
to
and
in
the
interim
we
use
that
custom
Ingress
proxy
filter
that
we
have
that
it
shows
us
every
request
that
goes
in
and
out
in
the
you
know,
if
you
were
to
offload
to
it.
So
that's
kind
of
how
we're
doing
it
now
but
like
the
tap
filter
is
like
been
on
the
roadmap
docs.