►
From YouTube: Contour Community Meeting - July 7, 2020
Description
July 7, 2020
What have we been working on?
CNCF TOC Accepts Contour as Incubating Project!!
https://www.cncf.io/announcement/2020/07/07/toc-accepts-contour-as-incubating-project/
Envoy Security Release: Contour v1.6.1
Envoy v1.15.0
Proposals
External Auth Design
Proxy Status Conditions
Configurable timeouts
A
Hi
everyone
and
welcome
to
the
July
7th
2020
episode
of
the
contour
community
meeting.
Today
we
get
a
few
important
announcements
to
make.
Then
we
have
some
status
updates,
of
course,
but
let's
start
with
sharing
the
screen
here,
so
you
all
can
see
what
we're
talking
about
there.
We
go
alright
I
think
Michael.
You
want
to
say
something
here:
yeah.
B
Absolutely
thank
you
thanks
Janice,
so
the
after
a
six-month
process.
Contour
is
now
part
of
scenes.
Yet
so
we
are
finally
one
of
the
incubating
projects
in
the
scenes
here
with
leapfrog
sandbox.
So
what
kind
of
skip
that
step
and
now
we're
among
the
15
or
so
projects
that
are
incubating
since
EF
with
a
gold
actually
graduate?
This
is
like
kind
of
huge
for
us.
I.
Think
number
one
is
you
know
it's
a
testament
to
all
of
the
work
that
the
community
or
many
internal
team
everybody
has
has
basically
worked.
B
B
Intel
incubation
and
we
look
forward
to
working
with
the
rest
of
the
community
and
the
rest
of
the
scene,
CF
projects,
but
again
a
huge
thumbs
up
huge
clapping
to
a
team.
You
know
this
is
a
great
effort.
I
would
like
to
believe
that
the
inclusion
of
stiff
creased
or
community
is
what
moved
us
path,
move
the
needle
move,
the
bar
and
our
part
of
CN
CF.
C
C
B
And
we're
not
done
yet
right,
so
we
have
a
huge,
a
huge
roadmap
for
contour
we're
gonna
continue
innovating
we're
gonna,
make
sure
that
we
align
very
well
with
service
API,
so
we're
gonna
make
sure
that
we
build
one
of
the
best
increases
for
kubernetes.
So
this
is
a
huge
huge
for
us
and
let's
enjoy
the
let's
enjoy
this
time.
For
now,.
A
A
E
I
can't
so
I
think
James,
you
did
the
release
last
week,
so
this
is
just
this.
Doesn't
change
contour
in
any
way?
It's
just
bumps
yeah
version
of
envoy
from
14
dot
or
1.14
dot,
two
to
one
to
14.3
and
listed
in
the
upgrade
notes
here,
which
is
handy,
are
all
the
cv
ease.
I
got
fixed
in
the
new
release,
so
it's
recommend
that
you
have
create
to
this.
When
everybody
came
to
the
latest
one
dot
14.3
or
if
you're
running
an
older
version
of
contour,
I
guess
you
could
go
to
the
13
to
12.
E
B
It
may
be
worthwhile
asking
them
Steve
is
that
you
know
I'm
sure
they
knew
about
some
of
the
security
releases
beforehand
right
now,
why
don't
they
try
to
patch
them
up
that
way?
They
only
have
one
update,
I
mean
they
have
it
I
mean
they
have
an
embargo
period.
So
it's
not
like
anybody
know
about
it.
So
I
mean
they
could
I,
don't
know
if
it's
worth
raising
it
to
them.
Like
you
know,
they
come
back
some
of
these
security
updates
that
way
that
we
can
go
those
for
now,
there's
another
one.
E
E
F
E
Yeah
added
these-
these
are
sort
of
new
as
of
last
week,
so
I'm,
not
just
sure
of
James.
If
you
want
to
talk
about
the
auth
proposal
or
not,
but
looking
for
feedback
on
this
one
as
well
as
the
second
one,
there's
one
to
call
it
out,
because
it
was
good,
just
gonna
ask
to
ask
you
know
folks,
on
the
call
or
folks
watching
this
later.
G
Yeah,
there's
a
bunch
of
there's
a
bunch
of
reading
in
places
to
give
feedback
on
which
would
be
really
good.
We've
had
some
feedback
on
24:59
and
there's.
You
know
a
lot
of
history
around
four
three
two,
but
yeah
it'd
be
great.
If
people
can
read
this
design
doc,
there's
a
section
at
the
end
which
lists
discussion,
topics
which
are
kind
of
arbitrary
decisions
that
we've
made
made
in
the
dark.
But
that
may
not
be
good
for
everyone,
so
feedback
on
those
would
be.
D
F
B
D
E
I,
so
the
goal
this
was
up
until
up
until
today,
with
ingress
brought
as
well
as
HTTP
HTTP
proxy
contours
had
a
status
condition
in
that
in
those
objects,
so
it
was
basically
is
it
about
or
not,
and
then
like
a
description
if
it
wasn't
badly
kind
of
what
went
wrong
and
it
give
you
like,
give
you
like
a
first
out
kind
of
error.
So
something
was
was,
was
a
doddering
correct,
you
would
say
in
value
to
get
the
first
one.
Potentially
you
could
fix
that
and
get
a
second
thing.
E
That's
wrong
and
fixed
that
and
get
another
one.
It
also
didn't
give
you,
because
it's
just
so
it's
so
basic.
It
doesn't
give
you
a
whole
lot
of
feedback
as
to
what
else
could
be
going
on
either
good
or
bad.
You
know.
So
if
you
have
a
a
child
proxy
in
a
different
namespace,
you
know
what
things
are
included
to
it.
Where
does
it
come
from
this?
You
know
what
sorts
are
delegated
to
it.
That
sort
of
thing.
E
So
the
goal
here
is
to
make
the
status
kind
of
stands
out
a
little
more
robust
and
feature-rich
to
allow
for
more
more
feedback
to
the
user
as
to
what's
going
on
so
this.
This
is
from
Nick
and
and
unfortunately,
not
here
to
talk
about
it,
but
we
got
a
good,
a
good
read
a
good
thing
to
look
through
and
add
some
comments
to,
but
the
high
level
thing
is
having
this:
this
condition
stanza,
and
so
instead
of
having
a
single,
you
know
it's
it's
nowt
or
invalid.
E
You
can
have
a
set
of
conditions
that
make
up.
You
know
hey
it's
an
error
and
here's
the
five
things
that
are
wrong.
That's
sort
of
a
sort
of
idea-
and
this
is
following
closely
along
with
how
upstream
is
kind
of
doing
some
of
their
their
feedback
as
well.
So
this
should
match
into
other
other
option
projects
but
yeah.
So
the
goal
is
to
help
extend
this.
This
function
that
functionality,
so
once
we
have
more
of
this
data,
then
we
can
drive
things
like
octant
plugins.
Maybe
you
work
some
or
some
other.
H
This
is
mine,
I've
been
working
on.
This
was
on
vacation
last
week,
but
anyway,
Nick
had
identified
a
set
of
envoy
timeout
values
that
we
wanted
to
make
configurable
through
the
contour
config
file.
Some
of
these
have
currently
have
contour
defined
defaults,
and
some
of
them
just
rely
on
the
Envoy
default
behavior,
but
we
want
to
expose
all
of
them
as
optional,
optional
configurable
values
through
the
contour
config
file,
so
basically
just
going
through
the
set
of
settings
that
are
in
the
second
bullet
here.
H
In
this
comments,
a
drain
timeout
idle
timeout
request,
timeout
stream,
idle
timeout
and
Max
connection
duration
and
wiring
these
through
so
I'm
just
just
kind
of
doing
them,
1
PR,
/,
first
setting
and
I'll
continue
to
work
through
the
the
rest
of
the
work.
That's
in
this
comment
once
I
get
through
that
initial
set.
B
F
We've
encountered
quite
a
bit
of
issue,
in
particular
around
WebSocket
and
TCP
timeouts,
and
some
of
that
has
been
miss
configuration
and
sort
of
lack
of
clarity,
but
we
do
think
there
are
some
lingering
issues
there
with
is
what
should
be
long-lived
connections
dropping
in
between
sort
of
it's
sort
of
weird
timings?
It's
like
15
minutes,
25
minutes,
40
minutes
like
it's
always
sort
of
some
sort
of
multiple
of
five
minutes,
even
though
people
said
time
announced
that
are
much
longer,
so
we're
still
trying
to
dig
into
and
replicate
some
of
those
the
other.
F
The
other
issue
we've
got
is
that
because
we've
had
issues
with
the
releases
like
something
might
have
another
one
with
one
point:
six
with
the
seg
fault
with
we
just
have
being
able
to
to
get
through
some
of
these
upgrades
to
get
more
current
and
boys
so
yeah.
This
is
something
we're
having
issues
with
and
we
need
to
do
some
more
testing
to
work
out.
What's
what
specifically,
those
issues
are.
B
Yeah
soon,
as
you
guys
have
more
data
on
that,
specifically
which
time
odds
may
be
problematic,
or
once
you
actually
have
enough
evidence,
you
know
you're
saying
that
the
timer's
are
always
multiples
of
5.
Let's
get
that
data
to
Steve
Chris,
so
he
can
at
least
internalize
it
and
see.
This
is
something
that
could
be
solved
by
this.
Pr
is
something
that
you
can
adjust
later
on
after
some
of
that
data,
so
can
get
deeper
into
this
and
see
if
you
can
solve
this
problem,
for
you,
yeah.
F
B
B
D
I
know
when
Nick
was
thinking
about
this
a
number
of
months
ago.
He
did
a
pretty
big,
deep
dive
on
envoy
timeouts,
because
apparently
there
there's
somewhat
complex
and
so
I
think
part
of
this
deliverable
is
also
documenting
them
and
documenting
exactly
how
the
contour
timeout
settings,
map
and
I
know
a
Nick
mentioned
that
too,
when
they
envoy
developers-
and
they
were
really
excited
about
shipping-
the
research
that
Nick
day
you.
H
B
Mean
I,
don't
have
anything
any
wisdom
to
offer
here.
You
know
you
know
for
the
folks
that
keep
joining
us
week
after
week,
nakiya
Michael
and
others
that
maybe
didn't
make
it
today.
Thank
you.
You
know
this
is
huge.
You
know
it's
your
participation,
your
insight,
but
of
testing
contour.
Alongside
with
us,
it's
what's
making
this
possible.
So
thank
you.