►
From YouTube: HTTP/3 With Envoy Explained
Description
Why HTTP/3, how to test HTTP/3 with Envoy, and use Prometheus and Grafana to observe metrics? In this livestream, Baptiste will join Lin to discuss HTTP/3 with Envoy and do a live demo of running Envoy with HTTP/3 and observing Envoy metrics.
#envoy #http3
00:03 welcome + speakers intro
1:20 hoot updates, service mesh, Cilium, eBPF etc news
3:00 general discussion around HTTP/3, what is HTTP/3 and why?
13:00 HTTP/3 and Envoy, config review + does it require any changes to app?
20:32 LIVE demo of HTTP/3 and Envoy
28:49 Key takeaways + wrap up
To learn more about us, please visit https://www.solo.io, we are hiring! https://www.solo.io/company/careers/
Questions? https://solo-io.slack.com
Code Samples: https://github.com/solo-io/hoot
Suggest a topic to cover here: https://github.com/solo-io/hoot/issues/
A
Hello,
everybody
happy
tuesday,
I
learned
recently
at
v3
is
supported
in
envoy,
actually
becomes
the
ga
in
one
of
the
most
recent
envoy.
So
why
http
3?
How
do
you
test
the
http
3
with
envoy
and
maybe
use
permissis
or
grifana
to
observe
metrics
in
this
live
stream?
I
am
so
excited
to
have
batisi
to
join
me
to
discuss
http
3
with
enboy
and
also
show
us
a
live
demo
of
running
envoy
with
http
3
to
observe
envoy
matrix.
I
am
so
excited
to
learn
from
him.
So
matisse.
B
A
A
Github
kong
is
calling
for
paypal.
In
fact,
I've
seen
a
trend
of
many
of
the
day
zero
event
of
kubecon.
It
started
opening
up.
If
you
ever
have
questions,
why
your
interests
day,
zero
event,
are
not
available.
They're
coming
along
just
be
a
little
bit
patient
solo,
I
o,
is
actually
added
to
the
list
of
psyllium
users
and
vendors,
because
celium
is
part
of
glue
application
network
platform.
A
A
B
Well,
so
as
everybody,
everybody
will
understand
this.
Basically,
this
is
a
new
version
of
the
most
frameworks
protocol
today,
so
before
speaking
about
http
3.
What
I
would
like
to
do
is
maybe
take
a
few
minutes
to
go
to
to
make
a
brief
story
of
http
and
how
it
has
evolved
over
the
last
two
decades.
B
So,
as
you
can
see
in
this
small
diagram,
http
came
up
like
in
the
1990s,
with
http
version
actually
0.9,
which
was
really
basic.
There
was
only
one
http
method
which
was
get,
and
then
you
put
some
rearray
and
you
get
that
resource.
That
was
it.
There
was
no
http
headers
hdb
headers
came
with
http
1
in
1996,
and
with
that
you
got
some
metadata
on
on
top
of
your
request
or
response,
so
that
you
can
better
control
how
the
information
about
the
the
request-
and
it
was
still
lacking.
B
The
other
aspect
of
the
other
thing
that
came
up
with
http
2
a
few
years
later
came
from
the
works
of
google
and
a
few
other
companies
on
alpine
and
basically
alpine
is
a
tlx
tls
extension
that
allows
for
protocol
negotiation
during
the
tls
handshake.
So,
basically,
if
your
server
supports
both
http,
1
and
http
2
and
then
during
the
tls
intake,
the
client
and
the
server
can
agree
on
which
protocol
version
they
are
going
to
use
for
the
following
request.
So
this
is
helping.
B
B
So
what
you
see
here
is
our
tcp
connections
with
multiple
streams
over
it.
So
basically
you
can,
you
can
think
of
one
stream
like
the
red
squares
and
yellow
squares
and
blue
squares
as
different
parts
of
an
http
request
or
different
packets
of
it,
okay
of
the
payload,
and
when
you
have
only
one
single
tcp
connections
and
multiple
streams
on
top
of
it
or
multiple
requests
on
top
of
it.
B
A
No
worries
so
I
guess
one
more
question
before
you
move
on
is
I
want
to
ask
you,
you
know
you
talk
about.
You
know
http
3
right
so
sounds
like
it's
useful
when
the
package
gets
chopped,
so
you
don't
have
to
resend
the
whole
thing.
So
why
do
I
need
to
care
about
http
3
from
a
user
perspective?
Is
this
maybe
for
performance
and
improved
network
performance.
B
Yeah,
exactly
that's
a
good
point,
so
there
are
two
main
reasons
so
one
is.
It
works
better
on
lower
quantity,
quality
networks,
especially
when
in
some
countries
we
have
a
good
internet
networks.
It's
not
the
case
everywhere.
So
when
there
are
some
loss
of
packets,
then
with
http
2
on
top
of
tcp,
you
would
have
to
resend
all
the
packets
again,
it's
not
the
case
anymore
with
quick,
so
it
works
best
in
in
lower
quality
networks
and
also
the
one.
One
of
the
reason
is
that
quick
comes
with
tls
and
you
cannot.
A
A
B
Okay,
great
here
we
go
so
yeah.
The
the
difference
between
tcp
and
and
and
quick,
basically,
is
the
number
of
round
trip
you
will
have
between
a
client
and
a
server
so
with
quick.
The
tls
handshake
is
done
at
the
same
time
that
the
udp
or
the
quick
connection.
So
there
is
only
one
or
two
round
trips
and
if
you
are
using
some
tlx
extensions
like
tls
session
resumption,
it
can
go
down
to
only
one
round
trip.
B
B
A
B
So,
basically,
as
you've
said,
http
3
http
a
few
months
ago
with
android
1.22
and
today
it's
ga
for
downstream
connections.
So,
basically,
when
you
deploy
android
at
the
edge
of
your
install
structure
and
like
as
a
gateway,
then
you
can
leverage
or
enable
http
3.
It's
it's
not
yet
not
yet
the
case
for
upstream
connections,
so
between
the
gateway
and
upstream
services.
A
B
B
B
Okay
cool,
so
this
is
part
of
the
demo,
but
let
me
explain
how
what
is
changing
in
the
end
by
configuration.
So
if
we
take
a
look
at
this
envoy,
configuration
that
that
can
look
scary
for
people
not
used
to
envoy,
and
that's
basically,
why
you
don't
do
the
android
configuration
yourself,
but
you
use
a
control
playing
like
istio
or
some
modern
api.
B
So,
but
if
you
want
to
do
it
by
end,
you
will
have
to
declare
those
listeners
so
basically
tcp
or
udp
listeners,
and
what
everyone
do
now
is
adding
this
tcp
listener
with
what
we
call
today,
the
http
connection,
manager
or
hcm,
and
this
is
how
you
configure
your
http
listener
today.
So
in
this
case,
in
this
demo,
I
have
two
listeners.
B
One
is
the
common
one
over
tcp
using
that
http
connection
manager,
and
the
second
listener
is
listening-
is
a
server
listening
port
10000
over
the
udp
protocol,
and
this
is
where
we
will
enable
quick
as
a
transport
layer
and
http
3
options.
Okay,
so
let
me
come
back
to
the
to
the
first
part
with
the
tcp
listener.
Why?
Because,
when
clients
connect
to
your
server,
you
you
you're
not
sure
that
they
will
use
http
3,
two
or
three.
B
So
basically
they
will
start
by
http
2
and
what
the
server
can
do
is
to
return
an
http
header
called
alt
svc,
saying
to
the
client
that
the
same
service
is
available
at
another
endpoint.
So,
basically,
the
same
service
is
available
over
http
3
on
the
same
port
so
and
the
browser
can
cache
this
response
for
like
one
day
and
with
that,
the
browser
can
try
a
new
connection
to
the
server
over
udp
or
over
quick
port
10000,
and
in
this
case
you
will
find
again
the
same
options.
B
You
everybody
knows
everybody
using
android,
no
with
the
http
connection
manager.
So
and
this
time
the
http
connection
manager
will
work
on
the
quick
transport
protocol
and
you
will
find
all
the
same
options
you
are
used
to
to
have
at
this
http
level.
So
what
you
see
here
is
just
let's
say,
a
virtual
host
working
for
all
domains
and
for
all
the
routes,
like
all
paths,
starting
with
slash.
B
A
B
A
My
application,
so
I
can
support
them
concurrently,
yeah.
In
fact,
I
think
I
was
just
finding
you
a
link
this
morning
about
experimental
mode
in
istio,
where
you
can
enable
hgb3
listener
on
it's,
your
ingress
gateway,
which
will
put
you
in
the
show
notes.
So
that
was
pretty
cool
too.
Let's
see
what
else
I
have
on
okay.
So
can
you
talk
about
what
are
the
envoy
metrics?
Do
I
get
all
the
ongoing
metrics
with
http
3
same
similarly
as
http
2?
Yes,.
B
Sure
so
the
matrix
will
be
quite
the
same
that
you
you
already
have
with
http
1
and
http
2,
because,
basically,
a
few
years
ago
when
envoy
was
built,
it
was
designed
with
http,
1
and
2
being
supported
from
from
the
start,
and
so
http
3
would
just
be
some
the
same
kind
of
matrix
with
a
different
name.
So
instead
of
http
2,
you
will
find
http3
and
I
I
can
share
my
my
screen
where
I
have
something
running
with
graphana
and
you
will
see
those
metrics.
A
B
B
A
B
A
A
B
Okay,
we
can
see
it
right
here
and
android
version
122
supports
quick,
so
I
will
run
it
again.
Maybe
I
have
a
shortcut
for
that.
Make
envoy
right,
so
it's
running
again
and
android
is
running
as
a
binary,
but
it's
proxying
request
to
some
dummy
upstream
service
which
is
http
bin
and
since
I'm
hitting
that
path,
slash
headers,
basically,
what's
what
the
backend
is
doing.
It
is
returning
me
my
request,
headers
in
the
response
payload.
B
B
B
Yeah,
if
you're
using
dash
k
yeah,
but
that's
why
I'm
using
this
reserve
option,
because
I'm
connecting
over
https
to
my
envoy
instance
and
in
my
environment
instance,
I
have
I'm
using
some
tls
certificate
with
a
pam
certificate
and
a
key
and
yeah
I
mean
it's
mandatory.
You
cannot
use
http
3
without
https.
A
A
B
B
B
A
B
B
Last
minute,
this
is
just
an
average,
so
yeah
back
to
the
request,
all
right,
so
that's
pretty
much
it.
If
you
are.
If
you
want
to
see
more
metrics
about
envoy
with
http
3,
you
can
have
a
look
at
the
promoters
matrix,
I'm
just
not
sure
which
part
this
was
running
on.
So
let
me
just
try
blindly
with
8081.
B
No,
I
I
I
can
follow
up
for
that
later,
but
yeah.
Basically,
what
you
would
see
is
just
the
same
metrics
that
are
already
existing
with
http
2.,
and
I
think
there
are
a
few
more
details
in
the
links
there
in
in
the
in
the
blog
and
more
information
on
the
metrics.
You
can
consume
and
set
up
alerting
from
them
if
you
want
to
to
be
alerted
on
on
anything
going
wrong
at
the
udp
level.
A
B
A
B
So
basically,
then
those
ones
so
just
as
a
reminder,
so
http
3
runs
on
top
of
quick,
which
is
on
top
of
udp.
So
it's
not
anymore
tcp
connections.
So
beware
take
care
if
you
want
to
enable
http
3
on
your
gateway,
just
think
about
the
firewall
that
you
might
have
configured
up
front.
So
you
want
to
allow
for
udp
traffic
on.
A
B
Of
tcp
traffic
also
tls
1.3
is
mandatory,
so
you
cannot
have
clear
text
traffic,
and
on
top
of
that,
if
you
look
at
the
links
at
the
bottom
of
the
article,
there
is
a
really
excellent
block
theory
from
robyn
marks,
who
explains
in
more
details
how
http
3
works
and
what
you
will
see
there
is
that
there
are
many
more
fields
of
udp
packet
that
are
encrypted
compared
to
the
the
same
kind
of
traffic
with
http,
2
and
tcp.
So
basically,
there
are.
B
A
B
Yeah
and
overall
on
the
internet,
according
to
the
cloudflare
radar,
it's
already
about
25
of
the
internet
traffic
that
is
using
http
3.
Why?
Because
all
the
the
major
actors
of
the
internet
are
using
http
3.,
so
cloudflare,
google,
so
youtube
facebook,
so
yeah.
You
can
imagine
that
it's
a
it's
a
big
part
of
the
traffic.
B
Well,
so,
as
we
have
seen,
http
3
http
3
is
available
since
envoy
122,
but
only
for
downstream
connections.
So
today
you
cannot
enable
it
for
upstream
connections
and
it
means
connections
between
the
envoy,
proxy
and
upstream
services
and
finally,
http
3
makes
a
connection
switching
small,
smooth
yeah.
So
if
you
can
just
remember
some
of
them
that
that
is
nice
and
yeah,
I
think
that
the
the
the
figures
that
I
have
shared
about
the
global
internet
traffic
are
pretty
relevant
as
well.
A
Yeah
definitely
so
25
of
the
internet
traffic
is
already
running
on
http
3.,
that's
significant.
I
I
guess
mostly
for
the
good,
the
gateway
tier,
the
the
downstream
connection,
the
upstream
connection,
we're
not
there
yet
so
that
we
can
potentially
enable
it
for
mesh
traffic
will
always
support
that
that's
really
cool.
Well,
I
want
to
take
a
minute
to
thank
you
faculty.
This
has
been
really
informative
education
for
me
and
I
hope
for
our
audience
too.
A
So
so
folks,
if
you
find
this
is
interesting,
please
let
us
know
give
us
a
thumbs
up
and
subscribe
to
our
channel,
so
you
don't
miss
any
of
our
future
cool
live
episode.
Well,
I
got
educated
and
hopefully
you
get
educated
too,
and
if
you
have
any
topics
you
would
like
to
see.
Also,
please
open
a
github
issue
in
solo
I
o
hoot
repository
or
just
put
a
comment
in
the
live
stream.
Thank
you
so
much
for
joining
us
today.
Everyone.