►
From YouTube: Welcome and Project Update - Matt Klein, Software Engineer, Lyft & EnvoyCon Program Chair
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.
Welcome and Project Update - Matt Klein, Software Engineer, Lyft & EnvoyCon Program Chair
A
Welcome
everyone.
Thank
you
for
coming.
This
is
particularly
strange
for
me,
as
I
have
not
seen
almost
anyone
in
three
years.
I
have
not
spoken
at
a
conference
in
three
years,
so
definitely
a
Time
Warp
back
to
when
I
used
to
speak
at
a
lot
more
conferences,
so
I'm
just
gonna
do
a
quick
recap
just
in
terms
of
where
we've
been
over
I
guess
now.
The
last
couple
of
years
I
just
wanted
to
highlight
a
bunch
of
the
work
that's
been
going
on
within
the
project.
A
That's
pretty
cool
first
thing,
of
course,
is
now
we
have
quick
and
HTTP
3,
that's
generally
available,
so
that's
been
a
ton
of
work
by
a
lot
of
people
and
very
excited
to
see
this
now
being
used
a
lot
more
widely.
Obviously,
there's
still
a
lot
of
server
support.
That's
going
to
be
needed,
so
it'll
be
very
interesting
just
to
see.
You
know
how
this
rolls
out
within
different
cloud
infrastructures
and
all
those
kinds
of
things,
but
I
would
expect
to
see
much
wider
deployments
of
this
technology
over
the
next
couple
of
years.
A
That's
very
exciting,
very
excited
for
people
to
try
it
out
and
give
feedback.
A
The
project
obviously
continues
to
spend
a
tremendous
amount
of
time
on
security
and
fuzzing.
We
still
have
lots
of
people
that
are
updating
our
fuzzers
finding
bugs
the
folks
at
Google
have
been
fantastic
and
sponsoring
a
third
party
firm
to
actually
go
through
our
fuzzing
backlogs
because,
as
you
might
imagine,
there's
lots
of
false
positives
in
the
fuzzing
framework,
so
getting
through.
All
of
that
noise
is
fantastic,
so
we're
burning
through
that
backlog.
A
This
is
an
area
of
the
project
where
actually,
if
you're
interested
in
helping,
we
always
have
a
large
number
of
fuzz
bugs
that
aren't
real,
bugs
they're
just
bugs
in
the
fuzzing
framework,
but
we're
always
looking
for
people
to
come
in
and
actually
help
fix
those.
So
if
that's
something
that
you're
interested
interested
in,
please
come
and
speak
up,
and
we
would
love
to
rely
on
you,
Linux.
Okay,
sorry,
it
was
working,
no
is
it
is
it
is
it
showing
at
all?
No,
let
me
see
hold
on.
A
Let
me
see
here
is
that
working
no
I'm
not
really
sure
what
to
do.
Let
me
see,
let
me
try
it
I'll
try
re-plugging,
if
not
I'm,
just
gonna
wing
it
is
it.
What.
A
Sorry
there
were
slides.
Okay.
Thank
you.
Thank
you
very
much,
all
right
so
back
on
the
security
and
fuzzing,
so
this
also
comes
back
into
software
supply
chain.
So
you
know
I
I,
think
a
lot
of
the
things
that
the
project
deals
with
at
this
point,
which
will
be
the
theme
of
my
next
slide,
is
you
know,
they're,
not
super,
exciting
things,
but
they're,
very
critical
things
and,
as
you
all
know,
within
the
industry.
At
this
point,
software
supply
chain
is
getting
a
lot
more
scrutiny.
A
A
You
know
that
are
not
up
to
the
standards
of
our
own
project,
and
you
know
this
means
auditing,
obviously
to
make
sure
that
we
don't
have
duplicate
dependencies
looking
at
the
dependencies
that
we
are
using
and
actually
making
sure
you
know
that
they
themselves
take
security
seriously
and
one
of
the
big
efforts
here
is
that
again
thanks
the
folks
at
Google,
we
are
replacing
our
all
of
our
HTTP
codecs
with
Google
provided
codecs.
A
We've
used
the
HTTP
one
parser
for
a
long
time.
That
code
base
is
deprecated,
so
we
can't
use
that
anymore
and
then,
for
a
very
long
time,
we've
relied
on
NGA,
HTTP,
2
library
and
long
story
which
I
won't
go
into
on
video,
but
the
maintainer
of
that
project
has
not
been
very
amenable.
You
know
to
working
with
us
on
a
security
perspective,
so
a
lot
of
effort
has
been
going
into.
You
know,
making
sure
that
the
supply
chain
for
those
critical
components
is
up
to
our
standards
and
that
we
can
rely
on
that.
A
So
that
is
work.
That's
ongoing.
It's
been
ongoing
for
quite
some
time
and
we'll
continue
over
the
next
few
months.
One
byproduct
of
that
which
again
is
a
boring
but
very
very,
very
critical
issue.
That's
been
open
for
a
long
time
is
that
historically
for
HTTP,
header
validation,
we've
had
different
code
for
each
of
the
codecs,
and
this
has
been
a
known
issue
for
a
long
time.
A
A
A
You
know
it's
just
it's
a
continual
thing
that
always
needs
fixing
and
updating,
but
we
have
a
bunch
of
people
led
by
Ryan
northlink,
who
have
been
doing
a
tremendous
amount
of
work
on
our
tooling
around
build
and
release,
and
we
are
very
close,
finally
to
being
able
to
ship
sign,
binaries
and
sign
packages
for
various
different
operating
systems,
which
has
been
a
long
time
request
of
the
project.
A
People
have
long
been
unhappy,
they
always
ship
or
Docker
images,
so
very
excited
to
finally
have
that
be
built
into
the
project
and
I
think
that'll
be
coming,
hopefully.
Finally,
in
the
next
couple
of
months,
but
again
this
is
another
area
of
the
project
which
has
something
to
do
with
the
low
level
C
plus
plus
code.
But
if
you
like
python,
if
you're
interested
in
this
type
of
tooling
there's
just
Perpetual
work
that
is
needed,
so
lots
of
work
happening
there.
A
Obviously
people
continue
to
work
on
webassembly
and
I.
Think
in
general
you
know.
Frankly,
this
has
gone
a
bit
slower
than
I
would
have
thought.
I
think
there's
been
more
performance
issues
than
people
realized.
It's
a
very
complicated
piece
of
technology,
but
it
is
becoming
stable
and
I.
A
Think
they're
fixing
performance
issues
over
time,
so
I'm
excited
for
all
the
work
that's
been
done
here
and
all
the
work
that
will
continue
next
up
is
probably
you've
all
heard
of
envoy
Gateway
and
you're
going
to
hear
more
about
that
today
and
the
just
the
brief
story
there
is.
We
would
like
to
make
it
easier
for
Envoy
to
run
on
kubernetes
Envoy
itself,
as
many
of
you
know
is
a
Swiss
army
knife
technology,
but
is
very
complicated.
A
The
barrier
to
entry
is
high,
so
we
would
like
to
make
it
easier
to
run
for
certain
common
use
cases,
so
I'm
very
excited
about
this
project
in
terms
of
making
it
easier
for
folks
to
get
started
with
Envoy.
So
we'll
hear
more
about
that
today
and
lots
of
work
happening
with
Envoy
mobile,
we,
you
know,
have
it
shipped
out
to
almost
100
of
users
at
Lyft.
Folks
at
Google
are
starting
to
look
at
it
pretty
heavily.
A
We
have
various
other
companies
that
are
starting
to
onboard
so
pretty
excited
about
the
future
of
this
project.
Also-
and
we'll
hear
more
about
that
today
and
you
know
the
reality-
is
that
so
much
work
happens
on
the
project
at
this
point
that
I
honestly
can't
even
keep
track.
I
mean
there's
just
so
much
happening
all
the
time
and
I'm
sure
I've
missed
many
important
things,
but
just
want
to
give
a
big
thank
you
to
all
of
the
people
that
do
so
much
work.
A
And
if
you
look
at
the
release
notes
every
three
months,
you'll
see,
there's
just
so
much
going
on.
So
just
a
quick
thing
in
terms
of
the
state
of
XDS
I
just
wanted
to
point
out.
You
know
that
at
this
point
things
are
becoming
a
lot
more
stable,
we're
obviously
focusing
on
General
API
stability,
interoperability
between
things
like
Envoy
and
grpc.
A
Because
of
that
we're
seeing
a
Slowdown.
You
know
in
the
number
of
new
apis,
which
is
a
good
thing,
we're
also
trying
to
push
everyone
towards
ads
for
all
new
things.
A
A
Is
we
don't
deprecate
anywhere
near
as
many
things
as
we
used
to,
which
is
great,
so
so
things
are
slowing
down
and
becoming
a
lot
more
stable,
and
on
that
note
you
will
hear
it
here
first,
although
I'm
going
to
do
a
policy
update
at
some
point
soon
is
we've
basically
decided
at
this
point
that
there
will
never
be
a
V4
API
and
we're
never
actually
going
to
deprecate
anything
so
any
any
apis
that
you
use.
They
will
be
there
forever.
A
We
we've
had
this
discussion
with
the
API
Shepherds
and
it's
just
becoming
clear
that
the
API
is
so
widely
used
at
this
point
that
you
know
trying
to
remove
code
at
this
point
or
remove
features.
Is
it
just
causes
so
much
pain
so
and
because
the
rate
of
deprecations
is
going
down
I
think
we
feel
that
this
is
an
okay
posture
to
have
so.
Hopefully
this
will
make
people
have
less
pain
in
the
future.
A
When
it
comes
to
API
updates,
we
will
still
deprecate
fields
and
you
know,
push
people
to
doing
the
new
things,
but
in
terms
of
actually
removing
the
code,
you
know
the
there's
no
plans
in
the
future
to
do
a
V4
API
at
least
not
right
now,
or
at
least
not
while
I'm
still
around,
and
my
final
call
to
action
is
you
know
one
of
the
things
that
I
like
to
think
about
is
is
Envoy
boring
now
you
know,
and
we
started
Envoy,
seven
and
a
half
years
ago
almost
been
open
source
for
six
and
in
some
ways
I
think
Envoy
is
boring.
A
Now
you
know
it's
not
it's
not
as
exciting
as
it
used
to
be.
There
aren't
as
many
Venture
capitalists
out
there
hounding
us
all
the
time
and
which
is
good
right.
I
I
think
we've
had
so
much
success
and
it's
been
so
fantastic
to
see.
Envoy
deployed
it
deployed
in
so
many
different
ways
that
it
is
a
bit
boring
now,
but
it's
boring,
obviously
because
of
all
of
your
hard
work.
So,
thank
you
all
and
my
pitch,
though,
is
that
boring
software
still
requires
a
lot
of
work
right.
A
So
it's
my
continuous
pitch
to
all
of
you
that
we
still
need
help.
You
know
around
lots
of
different
areas
within
the
project.
We
need
new
maintainers.
We
have
maintainers
that
work
very
hard,
but
people
get
busy
and
they
move
on
to
new
things.
So
having
new
maintainers
is
fantastic,
we
need
people
to
handle
releases,
so
that's
actually
cutting
releases,
doing
security
back
ports
all
of
those
things.
A
A
We
need
people
to
work
on
documentation,
just
doing
fixes
and
examples
and
all
of
those
things-
and
you
know
blogs
and
all
those
other
things.
So
just
my
general
pitch
again
is
that
I
think
there's
this
perception.
That
Envoy
is,
you
know
very
low
level
software,
and
you
have
to
be
a
networking
expert
to
actually
help
out.
That's
not
true,
in
fact,
there's
so
much
work
that
has
nothing
to
do
with
networking.
A
So
again,
my
annual
pitch
to
all
of
you
is
that
we're
always
looking
for
help
I
want
to
thank
tetrate
for
being
our
Diamond
sponsor
for
today,
and
thank
you
very
much
so
we're
gonna
have
a
lot
of
great
talks
and
there'll
be
time
for
people
to
chat
and
please
come
find
us.
So
thank
you
very
much.