►
From YouTube: Contour Community Meeting - April 7, 2020
Description
April 7, 2020
What have we been working on?
Nick as new tech lead
Contour 1.3.0
What’s up for 1.4.0?
Contour Donation to CNCF
Issue discussion
403 - Ingress status
A
Hi
everyone
and
welcome
to
another
episode
of
the
contour
community
meeting
today
is
April,
7th
or
April
8th,
depending
on
where
you
live
and
yeah,
where
we
have
had
a
brief
hiatus
here
of
the
community
meetings.
Now
we're
rebooting
again
here
in
April
and
yeah
I
want
to
talk
about
what
we've
been
working
on.
So
I'm
gonna
share
my
screen
here.
So
you
can
see
the
agenda
throughout
the
session
here
and
then
I'm
gonna.
Kick
it
all
over
to
Mitch
to
start.
B
Hi
everyone
well
I,
guess
we
should
talk
about
first
things,
what
we've
been
working
on,
probably
the
most.
The
first
notable
announcement,
as
you
can
see
in
the
agenda,
is
that,
with
the
departure
of
dead
change
for
the
team,
I
have
taken
up
the
tickly
position,
which
means
that
yeah
I
am
that
I'm,
the
one
who's
responsible
for
making
sure
that
things
are
supportable
and
usable
and
the
release
has
happened
on
time
and
all
that
stuff
from
the
engineering
side
and
so
yeah
I'm.
Looking
forward
to
being
able
to
do
that,
work
and.
C
One
other
thing
to
note
on
that
by
the
way,
folks
is
that
we
have
formalized
there.
Also
everybody
in
the
contour
team,
especially
in
the
development
team.
So
we
have
a
list
of
maintainer
and
the
maintainer
z'
are
are
listed
in
our
website
as
well
were
Jonas
is
furiously
running
too
so
so
Nick
young,
besides
being
the
tech
lead,
he's
also
maintainer
of
contour,
and
so
is
James
Steve
and
myself
and
dave
is
an
emeritus
maintainer
for
all
his
contributions
that
he
has
made
to
contour
so
far
go
ahead.
Nick.
B
Thanks
Michael,
so
yeah
and
I
guess
the
other
big
thing:
that's
happened
since
we,
since
we
lasted
a
meeting,
is
Jonah
said,
is
that
we
released
come
to
a
1.3.
So
this
this
release
was
our
usual
monthly
release.
So
because
it's
about
monthly,
we
don't
do
things
or
anything
like
that,
but
this
one
we
ended
up
with
a
bit
of
a
theme
of
you,
removing
removing
some
deprecated
and
fixing
a
bunch
of
sort
of
real
issues
rather
than
rather
than
delivering
big
new
features.
B
So
it
was
more
of
a
stability
release
and,
as
you
can
see,
the
first
one
is
that
we
remove
the
extensions
v1
v2
ingress.
So
now
you
need
to
remove
that
before
before
use,
try
and
start
contour,
obviously
our,
but
the
the
big
thing
there
is
that
we've
also
removed
extensions
v1
v2
one
API
group
support
for
the
ingress
object.
What
does
that
mean?
Well,
Nikki
universe.
B
Object
has
had
our
history
and
started
out
in
an
API
group
called
extensions
life,
and
the
version
was
women
via
one
and
that
the
English
object
was
moved
to
networking
kto
at
version
v1
beta
1
and
the
API
server.
Now
will,
since
about
I,
think
it
was
113
or
something
like
that
will
transparently
convert
between
those
two
objects
for
you.
So
if
you're
running
a
new
of
any
of
the
supported,
contour
version
communities
versions
with
contour,
then
you
can,
then
it
doesn't
matter
which
one
you
use.
B
119
I
think
is
the
is
when
it
will
finally
be
fully
GA.
So
we'll
start
using
that
object
once
the
once
the
release
that
first
introduced
it
is,
is
the
last
one
that's
in
support,
and
so
at
that
point
you
will
need
to
upgrade
to
a
supported
kubernetes
version
to
be
able
to
use
ingress
at
all
comfortable,
but
you
should
really
be
doing
that
anyway.
So
next
we
renamed
the
TC
proxy
proxy
include
field.
This
was
a.
This
was
just
a
thing
where
it
was
called
includes
because
it
was
the
same
name.
B
B
We've
also
got
a
couple
of
other
things
there,
so
HDB
properties
that
don't
have
at
least
one
service
per
route,
we'll
just
be,
will
be
deemed
invalid
and
won't
be
written
into
contour,
and
the
contour
will
also
now
know
about
a
job
of
gracefully
shutting
down.
When
you
get
a
CBN
or
a
C
term
ISO,
it
will
shut
down
all
the
things
that
has
started
properly
thanks
the
date
range
for
that
one.
B
As
you
can
see,
there's
a
bunch
of
other
minor
improvements,
but
most
of
the
most
of
the
minor
improvements
are
yeah
small
bug
fixes
and
so
on.
I
said
that
sort
of
as
I
said,
1.3
not
a
huge
release,
but
just
all
all
about
stability
and
fixing
problems.
So
I
guess
probably,
unless
anyone
has
any
questions
we
should
I
should
move
on
to
talk
about
some
of
the
stuff
that
might
be
coming
in
1.4,
yeah,
okay,
well,
I'm,
right
now,
right
now,
the
stuff
that
we're
talking
about
41.4
is.
B
The
English
status
is
a
feature
that
contour
head
has
been
missing
for
a
while.
That's
that
when
you
create
an
ingress
object,
most
English
controllers
will
will
update
a
section
of
the
status
of
that
ingress
with
the
IP
address
or
domain
name
of
the
place
that
you
can
connect
to
to
actually
get
that,
as
you
can
see
there
that
that's
the
that's
what
the
status
should
look
like
this.
This
status
stands
at
under
the
expected
column
on
the
ticket.
B
This
has
been
a
bit
of
a
journey
because,
because
we
hadn't
done
a
bunch
of
stuff
that
we
needed
to
do
to
be
able
to
do
this,
but
most
of
that
code,
reorganization,
has
happened
now.
The
support
for
that
is
currently
for
this
feature
in
a
basic
way
is
currently
in
master
in
master.
As
as
we
as
we
stand
right
now,
it
has.
It
has
support
for
the
example
deployment.
Only
pretty
much
I
have
one
more
issue
outstanding.
B
Once
that's
done,
then,
I
consider
this
feature
to
be
done
and
it'll
it'll
make
it
into
one
point
for
that
should
be
done
in
the
next
couple
of
days.
So
what
this?
What
this
means
for
for
users
is
that
you
will
be
able
to
use
any
English
objects,
managed
by
contour
with
things
like
external
DNS
and
anything
else,
and
the
the
draft
English
conformance
tests
and
anything
else
that
requires
this
ingress
status,
load,
balancer
value
to
be
set,
I.
Think
if
Cyril
DNS
is
probably
the
big
one.
B
B
B
So
the
other
stuff
that
we've
got
that
should
land
in
1.4
is
the
support
for
external
client
certificate
validation.
Now
that
one's
that
one
says
them
TLS,
and
it's
important
to
clarify
here
that
this
is
non
empty
letters
in
the
sense
of
a
server.
That's
initially
talking
about
rapidly
frequently
changing
service
to
service
authentication,
either.
B
Tell
us
that's
being
introduced
is
the
ability
for
a
browser
client
to
specify
a
client
certificate
that
will
then
be
used,
be
required
in
order
to
connect
to
a
specific
English
or
HTTP
ingress
or
HTTP
proxy
route,
so
that
when
that
work
has
been
mainly
done
by
two
pero
sunny,
which
we
very
much
appreciate,
he's
been
doing
a
lot
of
great
work
there
to
actually
get
this
happening.
So
this
PR
is
almost
finished.
James
and
Tara
have
been
working
on
this
one.
B
It
should
be
done
soon
when
that,
when
it
happens,
then
the
yes
so
yeah,
basically
and
where
this
obviously
this
issue
covers
the
that's
visible
on
the
screen
now
covers
documenting
the
future,
and
so,
but
the
idea
is
that
if
you
want
to
be
able
to
use
a
client
certificate,
authentication
too
close.
Sorry,
yeah
authentication
is
the
correct
thing
here
that
that
you
can
verify
that
a
client
is
who
they
say
they
are
and
require
that
to
be
oh,
to
connect
to
a
specific
service.
You
will
now
be
able
to
use
contour
to
do
that.
B
It
is
not
currently
able
to
be
used
for
authorization,
because
contour
is
kinda
like
the
front
door
and
authorization
is
what
happens
after
you
get
in
the
front
door.
That's
authentication,
and
so
authorization
really
needs
to
be
delegated
to
your
your
service.
Your
service
should
be
checking
the
sort
of
the
details
about
the
about
things
and
that
is
not
built
yet
so
right
now
right
now.
This
will
give
you
some
basic
authentication,
but
it
does
not
do
otter,
ization
those
two
to
be
done.
B
I
guess
other
things
that
I
can
see
that
we
have
worked
on
so
far,
there's
been
we've
upgraded,
1:14
planning
to
upgrade
to
go
114
and
the
other
one
that
the
one
that
I
will
be
picking
up
after
I
finish.
Setting
addresses
on
in
diverse
resources
is
figuring
out.
If
we
can
do
the
similar
thing
for
HTTP
proxy
resources
as
well.
B
I
think
there's
been
some
that's
what
we
got
in
progress,
Jonas
yeah,
so
we've
got,
we've
got
some
work
happening
as
well
on
separating
if
you
scroll
down
on
the
returns
on
separating
the
health
and
metric
services,
we've
been
careful
here
to
ensure
that
there's
a
backwards
compatibility
so
that
if
you
are
upgrading
your
control
version
by
changing
the
version
in
your
deployment,
then
this
won't
break
you.
But
the
idea
here
is
that
if
you
want
to
be
able
to
have
a
separate
listener
for
metrics
and
health
check,
then
you
you
can
do
that
yeah.
B
C
B
B
Yeah
and
we've
had
a
few
contributions
from
people
too
to
to
get
updates
and
documentation
and
I.
Just
love
like
I.
Don't
hear
it's
perfect.
Yeah!
Yes,
yes
see
ken
has
has
requested
the
change
and
then
also
been
the
change
and
fixed
up
the
fixed
up
the
the
issue
as
well
and
Steve.
You
worked
on
the
so
if
you
could
just
scroll
back
up
a
bit
thanks,
Janice
Steve,
you
worked
on
the
did
you
do
the
duplicate
slushies
in
the
past
things,
dude
yeah.
D
Yeah,
so
so,
if
you
had
a
request
that
was
like
/foo
slash,
slash
bar
icon
tour
wouldn't
route
properly
because
it
didn't
match
the
path.
You
know
it's
like
it's
an
explicit
match.
So
there's
a
flag
and
envoy
that
you
can
say
hey.
If
you
see
the
double
slash,
just
merge
it
out
and
replace
it
with
just
a
single
slash.
Somehow
the
request
comes
in
and
has
duplicate
slashes.
Then
this
will
resolve
that
now
will
actually
route
yeah.
B
C
D
So
before
it
so
that
issue
data
at
$21.99,
so
contour
in
ingress
or
the
generic
ingress
pack,
you
can
define
a
ingress
class
and
what
this
does
is
allows
multiple
controllers
to
exist
in
your
cluster.
So
you
could
have
you
know
like
contour
as
an
ingress
controller
and
nginx
as
one
or
run
multiple
versions
of
contour.
If
you
wanted
to
have
that
for
a
whole
bunch
of
reasons,
the
problem
comes.
D
Is
that
if
you,
even
if
you've
defined
an
ingress
class
on
contour,
so
say,
hey
I'm
only
going
to
process
an
ingress
class
called
you
know,
Steve,
it
still
processed
any
object
that
matched
that
class
as
well
as
any
object
that
didn't
have
a
class
on
it.
So
didn't
have
the
annotation.
So
it's
kind
of
confusing.
So
you
would
have
you
know,
you're
setting
this
explicit
way.
Contour
should
function,
but
it
still
grabs
other
resources
that
don't
have
the
annotation
so
starting
in
1.41
sand
ships.
If
you've
set
an
ingress
class
on
contour
that'll.
D
B
It
should
be
tests
are
through
yeah,
a
bunch
of
tests
on
this.
There
is
an
important
caveat
to
that,
though,
that
in
the
case
that
you
don't
specify
an
English
class,
the
way
contour
currently
behaves.
Is
it
there?
If
you
don't
specify
an
English
class,
there
are
actually
two
valid
options:
either
or
three,
not
specifying
an
English
class
at
all,
specifying
a
blank
English
class
or
specifying
contour
the
word
as
the
English
class,
and
so
for
backwards
compatibility.
We
have
kept
all
three
of
those
options.
B
So
now,
if
you
do,
if,
when
you
run
contour,
there's
a
command
line
flag
that
you
can
pass
to
it
that
specifies
what
English
class
that
instance
of
contour
should
use.
If
you
don't
specify
that,
then
you
have,
then
there
are
three
weight
of
three
ways
that
English
objects
we
link
with.
Can
it
can
be
used
by
a
default
contour
like
that
one,
not
having
an
English
class
annotation
to
having
a
blank
English
class
and
an
annotation
or
three
having
an
English
class
annotation,
or
that
is
the
word
contour?
And
so
then?
E
C
B
B
Yeah,
exactly
yes,
I
think
the
command
line
flags
documentation
is
the
is
the
place
to
put
that.
In
the
first
instance,
I
would
say
for
now
we
can
probably
put
some
reference
to
it.
Any
annotations
page
as
well,
because
the
English
class
and
a
TV
news
documented
in
the
annotation
page
so
I
will
all
take
an
action.
How
to
do
that.
Thanks.
C
Cool
so
quick
update,
so
the
in
the
TV
meeting
today,
Sikh
Network,
we
had
a
discussion
and
from
from
a
sixteen
network
standpoint,
the
due
diligence
is
complete,
they're
essentially
done,
and
they
are
waiting
for
two
things:
they
waiting
for
someone
to
write
it
down
and
there's
some
artifacts
that
need
to
be
produced,
usually
I
produced
them
in
the
past
for
other
six
I,
don't
know
if
they
will
end
up
producing
them
or
me,
and
the
last
thing
is
Matt.
Klein
and
I
had
a
discussion
along
with
Amy
as
well.
C
Some
of
that
discussion
was
offline.
Some
of
it
was
three
males,
but
essentially
we
lost.
We
used
to
have
three
sponsors
when
were
when
we
initially
went
for
donation
to
sin.
Cf
Alex
is
Matt
Klein
in
Joe
Beda.
Two
of
those
people
are
no
longer
in
the
TOC,
so
they
can't
sponsor
us.
So
Red
Hat
was
pushing
that
hey.
You
need
to
go,
find
new
sponsors.
The
answer
is
from
private
thread
between
me,
Matt
and
Joe.
C
Is
that
Noah
don't
leave
us
alone
and
we're
going
directly
to
incubation
that
doesn't
have
any
sponsorship
requirements
so
in
a
roundabout
the
way
the
process
ended
up
working
for
us
a
little
bit
so
much
clients
can
I
do
finish,
is
reviewed
in
the
next
2-3
days
when
Matt
tells
me
I'm
gonna,
do
it
in
the
next
couple
of
days.
This
was
on
Friday.
It
really
means
a
week
we're
gonna
have
plus
minus.
So
when,
when
Matt
is
done,
we
will
submit
up
for
a
vote
so
assume
the
signal
work.
C
A
Right
then,
that's
it
for
today's
meeting,
this
week's
meeting
and
or
usual
now
we're
gonna
rotate
we're
gonna
do
every
first
and
third
week.
It's
gonna,
be
in
the
morning
over
in
Australia
6:30
p.m.
here
on
the
East
Coast
in
the
US
and
3:30
over
on
the
west
coast,
and
then
every
second
and
fourth
Tuesday
we'll
have
it
and
I
think
it's
a
1
p.m.
Eastern
and
10:00
a.m.
Pacific,
and
with
that.