►
From YouTube: Contour Community Meeting - Sept 24, 2019
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hi
everyone
and
welcome
to
the
monthly
contour
community
meeting
I
am
Jonas.
Rosalind
I'll
be
your
host.
Today
with
us,
we
have
the
contour
team
and
the
contour
community
and
we're
gonna
talk
about
a
bunch
of
really
cool
upcoming
stuff.
So
I'm
gonna
share
my
screen
here
with
the
community
meeting
agenda.
So
Dave
and
team
can
talk
around
it
and
if
you
have
any
questions,
please
just
post
them
in
the
chat
or
if
you
would
rather
speak
up.
A
B
B
Let's
start
with
some
housekeeping
stuff:
are
there
I
intimated
last
time
we
spoke
that
there's
just
a
kind
of
bunch
of
procedural
things
that
we
have
to
do
me,
the
empty
our
brains
going
away.
That
is
how
a
lot
of
not
not
gonna
fix,
but
what
we've,
what
we've
been
doing
out
of
there,
is
making
pain,
centralizing
and
consolidating
branding
and
mastered
chipping
around
this
idea
of
project
contour.
So
project
contour
is
the
project.
Ontario
is
the
domain
for
the
project.
B
We've
also,
we've
moved
the
repository
to
project
contour
just
to
rather
than
just
well,
we
have
to.
We
have
to
rename
the
thing
anyway,
let's
try
and
make
it
make
it
useful
so
that
some,
if
you
have
you,
know,
get
hubs
pretty
good
at
the
redirections
and
there's
a
businessman
in
our
blog
post,
honestly
I,
don't
think
anyone's
really
gonna
know
really
going
to
notice,
but
it
was
part
of
the
part
of
the
housekeeping
we
needed
to
do
to
continue
to
move
away
from
the
appear
brand
equal
to
that.
B
This
has
some
impact
we'll
continue
to
publish
what
we
consider
to
be
the
stable
release,
which
is
0
or
15
to
both
G
cRIO
and
the
docker
hub,
but
the
QuickStart
images
and
our
image
hosting,
and
what
we
consider
to
be
the
the
master
tag
that
comes
out
of
comes
out
of
CI
is
all
happening
on
the
docker
hub.
So
even
if
you're,
not
even
if
you're
not
going
to
follow
us
on
the
control
and
better
been
a
journey
for
a
moment,
you
want
to
sit
and
wait
for
the
stable
release.
B
It's
still
be
a
good
idea
to
update
we're,
pulling
the
images
from
because
eventually
I
don't
know
when
I
mean
me
tomorrow,
but
it
will
be
eventually
that
the
building
account
that
holds
up
these
TCR
heavy
images
makeup
might
go
away
or
if
I
change
the
private
or
something
like
that.
So
this
is
a
good
opportunity
to
to
make
that
transition.
That's
most
of
the
house
being
things
I'll
pause
here
for
a
second
mr.
case,
and
it
was
like
you
move
my
stuff.
Where
is
it
you,
you
cool
good?
B
That's
all
the
housekeeping
out
of
the
way.
So
the
main
event
today
is
talking
about
the
first
Peter
of
contour
1.1,
we'll
talk
a
little
bit
later
and
the
kind
of
general
east/west
gains
what's
going
to
happen
over
the
next
couple
of
months,
but
this
is
the
this
is
the
big,
the
big
enchilada.
This
is
what
we've
been
working
for
towards
for
a
couple
of
months.
You've
seen
us
you've
seen
us
putting
a
lot
of
effort
into
finalizing
feature
set
in
0
to
14
or
15,
and
now
we're
very
deeply
into
polishing
up
this.
B
This
has
this,
has
a
bunch
of
OC
mutant
evolution
so
for
any
creatures,
Deebo
fix
the
blob
we
can
talk
about
that
later,
but
the
probably
the
thing
to
take
to
use
the
time
we
have
today
is
to
talk
about
what
calling
contour
wanderer
means
for
our
other
projects,
namely
ingress
wrap,
which
has
been
in
beta
for
a
long
time.
The
short,
the
short
answer
that
is
ingress
route
is
deprecated.
We
are
not
going
to
be
adding
any
new
features
to
it.
B
After
wonder,
though,
no
wonder
one
frame
or
whatever,
like
that,
we
haven't
really
good,
put
a
straight
timeline
in
that,
but
really
ingress
route
is
is
deprecated
now
that
sounds
like
that
sounds
like
a
really
big
kind
of
cool
you
just
you've,
just
like
turned
off
the
whole
reason
for
having
contour
but
actually
turns
out.
That's
that's
not
true.
We
have.
B
We
also
took
the
opportunity
to
think
about
the
just
what
the
name
ingress
router
gests,
suggested
to
users
coming
in
off
the
street
to
people
who
are
comparing
comment
against
other
solutions
who
are
trying
to
figure
out
where
it
fits
in
the
miasma
of
all
the
kubernetes
networking
solutions
and
the
very
strong
statement
we're
making
is
by
calling
it
our
replacement,
HTTP
proxy.
This
is
what
contour
is
remember.
What's
our
catchphrase,
contour
is
not
a
service
mesh.
If
it's
not
a
service
mesh,
then
what
is
it?
And
it's
quite
literally
I
hate
to
be
proxy.
B
Our
space
is
layer
7
we
wanna.
We
are
the
middleware
between
remote
clients
and
your
kubernetes
web
applications
running
in
your
cluster,
so
calling
to
take
the
opportunity
to
not
just
change
the
group
name
from
condo
contour,
like
VMware
comm,
to
project
contour,
but
actually
looking
at
how
we
met
message.
The
name
of
the
key
feature
to
make
it
very
very
clear
what
space
ring
is.
B
These
part
of
is
part
of
preparing
for
in
framing
for
contour
window,
so
that
that's
my
long
soapbox
about
why
I
decided
to
change
the
name
and
how
I
to
to
come
along
with
me.
But
what
I
want
to
do
now
is
pause
for
a
little
bit.
Stop
talking
and
free
you
from
listen
to
the
drilling
in
the
background.
I
want
to
hand
it
over
to
the
Indian
who's
been
leaving
the
design
on
this
Steve.
B
Who
probably
is
just
read
that
I've
said
demo
time
here
and
I'm
really
hoping
that
he
could
demo
some
stuff
and
especially
point
out
that,
even
though
we've
renamed
it
and
moved
it,
but
it
actually
isn't
that
much
difference
between
HTTP
between
ingress,
right
and
HTTP
proxy
and
the
differences
are
hopefully
positive
ones
which,
which
will
come
too
so
I'm
gonna
hand
it
over
to
Steve.
That's
okay,
I
haven't
I,
haven't
talked
to
steel
about
this
before,
and
so
this
is
my
classic
thing.
You
drop
any
minute.
The
last
minute,
yeah.
C
It's
all
good
thanks,
Dave
yeah
I
saw
that
and
I
started
to
build
ups
and
done
many
things.
So
thank
you.
Jonas
I'm,
gonna
go
and
share
share
my
screen
here.
Let's
make
this
one
easy
to
see:
okay,
cool
so
where
to
start
so
real,
quick,
we'll
just
go
ahead
and
do
a
food
control,
get
Sierra,
DS
right
and
we'll
see
now,
there's
a
new
CRT
that
got
created.
So
this
is
HD.
Http
proxies
right
so
much
similar
to
how
we
had
ingress
routes.
C
You
can
see
now
we've
moved
the
API
spec
from
hep
Gyo
to
project
contour,
so
it
would
use
we'll
go
ahead
and
let's
walk
through
a
couple,
little
demos
of
how
this
looks
and
feels
now
and
again,
if
you're
familiar
with
ingress
route.
This
will
feel
much
the
same
with
a
couple,
little
caveats
and
twists
of
how
this
looks.
So
here's
a
very
simple
proxy
we
have
here
and
you
notice
that
this
looks
similar,
for
we
have
a
virtual
host.
C
C
This
was
just
prefix
when
you
define
the
the
path
prefix
for
the
routes,
but
now
they're
called
conditions,
and
this
is
because
we
can
do
more
than
just
path
prefix
routing
now
we
can
also
do
things
with
header
routing,
which
is
kind
of
cool
and
we'll
look
at
that
here
in
a
second,
but
just
for
fun.
Let's
go
ahead
and
run
this
one.
So
if
we
go
ahead
and
get
our
proxies,
you
can
see.
I
have
no
no
proxies
at
all.
C
So
let's
go
ahead
and
apply
this
so
I
will
control,
apply,
delegation
cool
so
now,
if
we
go
ahead
and
get
our
proxies,
you'll
see
I've
got
another
one
here.
This
is
a
valid
proxy.
It
looks
very
similar
if
I
go
ahead
and
curl
and
you
kind
up
local.
What
you'll
see
here
is
that
it
works,
which
is
which
is
pretty
cool
right.
So
I
have
my
service,
which
is
called
the
echo
service,
and
it
goes
back.
This
is
the
route.
C
This
is
telling
me
that
this
is
the
route
proxy
here
in
my
example,
but
what
I
can
do
now
is
I
can
expand
on
this,
so
I'll
go
ahead
and
and
pull
the
cake
out
of
the
oven
and
we'll
bring
this
up,
and
what
we
can
do
now
is
I
can
add
some
different
conditions,
so
let's
go
ahead
and
add
some
headers.
So
in
addition
to
routing
this
on
slash,
what
we'll
do
is
we'll
make
this
in
my
ml
right.
C
So
now
what
we
can
do
is
we
can
route
on
slash,
as
well
as
having
the
header
X
header,
exactly
matching
ABC
in
the
request,
so
both
of
these
have
to
exist
for
this
request
to
route.
Now,
if
I
apply
this
one,
could
we
apply
that?
So
if
I
do
the
same
curl,
I
get
a
404
right
and
that's
because
we
told
envoy,
hey,
our
conditions
must
meet.
All
of
these
requests
has
to
meet
all
of
these
conditions,
which,
in
this
example,
is
slash
as
well
as
X
header,
meaning
exactly
ABC.
C
If
we
go
ahead
and
do
the
request
and
add
that
header,
then
we
should
work.
X
header
PVC
right
and
there
you
go
now
I'm
gonna
work.
My
request
got
routed
through
correctly,
just
because
you
know
I
have
the
proper,
proper
pieces
on
there
to
make
this
a
little
a
little
better.
Let's
go
ahead
and
solve
all
requests
that
don't
match
that
header.
So
we
want
to
match
a
request
with
the
header
ABC
and
then
have
everything
else
default
to
another
service.
C
So
if
I
go
ahead
and
look
at
my
services,
let's
go
ahead
and
we'll
do
Cordy.
That's
a
good
example
there.
So
we'll
come
to
here
and
we'll
just
add
another
route.
Right
and
we'll
say
this
is
going
to
be
an
actually
if
I
wanted.
I
could
leave
off
conditions,
because
that's
assumed
that
if
not
it's
assumed
slash
so
we'll
go
ahead
and
make
this
yeah
Courtney
and
then
support
thee.
C
So
now
this
is
going
to
do.
Is
I
have
two
different
routes
in
my
in
my
proxy
here
I've
got
one
that
says:
hey
slash
with
the
header
browse
to
the
echo
service,
and
then
everything
else
was
just
slash,
is
going
to
route
to
the
Cordy
service,
so
go
ahead
and
apply
that
one
okay.
So
now,
if
I
do
my
curl
with
the
header
I
should
get
the
route
1
and
then
hopefully,
if
I
take
out
the
header,
I
should
get
Cordy,
which
this
is
Cordy.
C
So
this
might
be
good
for,
like
a
user
agents,
they
don't
want
to
say,
like
user
agents
oops
sorry,
my
name
is
user-agent.
Maybe
this
one
contains
crumb
one
like
that:
I
want
to
match
on
different
browsers.
We
want
to
match
on
like
iOS
versus
Android
or
something
so
those
are
all
total
possibilities
now
and
these
these
can,
you
know,
go
on
forever
as
long
as
you
understand
that
these
all
these
requests
have
to
match
for
it
to
route
to
this
proper
place.
C
Okay,
so
let's
make
this
a
little
more
interesting,
let's
introduce
a
new
thing
so
before
an
ingress
route
we
had.
This
idea
of
delegation
and
delegation
said
I:
have
this
ingress
route
and
I'm
gonna
delegate
a
path
off
to
another
resource?
This
is
helpful
for
teams
right,
so
now,
teams
could
manage
their
ingress
resources
safely
within
a
cluster
and
not
have
to
worry
about
conflicting
paths
and
stomping
over
each
other
and
breaking
things.
C
So
we
kind
of
took
that
idea
and
flipped
it
around
and
instead
of
using
this
idea
of
delegation
reusing
this
idea
of
includes
and
what
an
include
does
this
follows
kind
of
how
you
would
might
include
a
file
in
a
coding
language
right,
so
I
can
say
you
know.
My
seed
bus
plus
program
includes
the
other
file
and
then
when
this
gets
processed
we
take
that
include
and
we'd
stick
it
in
into
that
request
and
then
smash
that
together
and
then
come
up
with
that
result
right.
C
So
we
can
include
all
these
different
attributes
and
and
get
them
passed
off
to
different
different
resources.
Now,
so
let's
go
ahead
and
add
this
down
here.
So
what
I
can
say
now
is
I
can
say:
I
have
these
set
of
includes
and
now
we're
gonna
do
some.
You
know
delegation
like
we
did
an
ingress
route,
so
I'm
gonna
say
hey
this
resource
dub-dub-dub
site
in
the
namespace
Team
A
and
I'm
gonna
give
them
some.
C
Some
includes
I'm,
gonna,
say:
hey,
you
get
slash
blog
and
let's
just
take
the
header
off
for
now
and
make
this
simple
for
now
right,
so
we're
gonna,
we're
gonna,
add
this
resource
and
say
hey!
This
resource
includes
this.
This
include
right
and
then
we'll
go
down
here
and
we'll
create
that
other
resource
as
well.
So
then
you
go
ahead
and
add
this
cool
and
then,
let's
make
this
a
little
more
simpler.
C
Okay,
sorry,
this
is
my
last
minute
demo
setups
this
one
means
you're,
jumping
around
I'm
cool.
So
what
I
have
now
is
I'm
gonna,
say
dub,
dub,
dub
site
in
Tignes
and
here's
the
resource
for
that
right
and
we're
just
gonna
say:
let's
just
take
this
out
as
well.
We're
just
gonna
say
that
this
routes
to
the
echo
service,
okay,
so
let's
go
ahead
and
create
these
two
things
cool.
C
C
Why
did
not
do
I'm
missing
a
dots
or
something
like
that?
Yeah?
Okay,
sorry,
yeah
Mille!
You
need
three
dots
to
separate
them.
Alright,
let's
go
ahead
and
apply
that
now.
Okay,
now
I
have
two.
So
now,
if
we
go
ahead
and
get
these
okay
good
now,
I
have
okay,
we're
good
now
so
now,
I
have
two
proxies
right
and
I
have
the
root,
which
is
kind
of
local
and
I
have
the
second
one
now
for
this
team
again,
what
I
did
was
I
said
this
proxy
here
now.
C
Has
it
include
of
/blog,
so
any
requests
to
slash
blog
is
going
to
go
to
the
echo
service
in
the
team,
a
namespace.
So
if
we
go
ahead
and
do
a
request
to
slash
blog
we'll
see
now,
this
is
the
green
one.
So
green
green
greens,
so
that's
in
the
team,
a
namespace
right,
but
all
I,
all
as
a
user.
All
I
see
in
this
spec
is
that
I
have
just.
This
is
my
proxy
now
right
so
because
of
the
includes
I
now
have
that
passed
off
to
them.
C
Similarly,
but
what's
neat
is
now
I
can
add
other
things
like
I?
Can
make
require
headers
so
if
I
need
to
maybe
an
auth
header
on
every
request,
so
my
back-end
services
are
back
in
proxies.
I
could
do
this
now
so
now
we're
gonna
pass
off
two
conditions
to
this
team.
We're
gonna
include
a
prefix
of
slash
blog
as
well
as
a
prefix
of
this
X
header
ABC,
all
right.
Let's
do
this
contains
just
for
fun.
C
C
Which
I
got
green
before
he
didn't
I
yeah?
You
did
Dave's
killing
me
here
with
this
last
minute.
Demos
I
apologize
for
that.
This
is
fun
though
right
we
can.
We
can
work
on
this
together
and
that's
why
we're
still
in
alpha
because
we're
getting
through
that,
but
you
can
get
the
idea
right,
so
this
headers
gonna
get
passed
off
as
well.
C
C
C
Let's
try
it
again
so
now,
I
should
require
the
header
and
there's
the
green
one.
Okay
I
think
there's
an
issue
there.
We'll
have
to
mark
that
down
too,
if
I
had
conflicting,
basically
routes
where
I
had
two
prefixes
with
the
same
same
request
pattern
so
good,
that's
that's
good!
We
found
something,
but
you
can
see
here
just
to
make
my
demo
make
sense.
Now
what
I'm
saying
is
I
have
basically
I'm
taking
these
includes.
So
these
conditions
are
gonna,
be
passed
off
to
this
other
ingress
or
Arab
HTTP
HTTP
proxy.
C
That
makes
sense,
and
we
can
go
on
for
it.
If
we'd
like
to
you,
we
could
do
the
same
thing
so
now
that
I
have
these
conditions.
I
can
have
more
includes
that
this
one
passes
off
again
right
and
then
again
it
becomes
the
sum
of
all
the
includes
that
happen.
So
if
I
had
more
more
includes
here
yeah,
this
would
get
passed
off
as
well.
C
C
C
Not
seeing
it
oh,
this
is
too
far.
Okay
cool.
So
now
we
have
to
make
this
whole
thing
makes
sense.
What's
just
kill
this
for
him?
So
now
we
have
slash,
goes
to
the
echo
service.
We're
gonna,
say:
slash
blog
with
this
header
ABC
is
included
to
this
proxy,
and
now
this
proxy
is
saying:
I'm
gonna,
take
that
and
I'm
gonna
add
more
conditions
and
pass
that
off
to
this
other
proxy
here
and
it's
dub-dub-dub
one
which
does
this
one
down
here,
so
resulting
one
should
be
slash.
C
Blog
/,
foo
should
match
to
this
proxy
and
I
was
also
with
the
header
that
makes
sense
right.
So
we
applied
it.
Let's
go
ahead
and
get
our
proxies
to
make
sure
they're
all
there
there.
We
only
have
all
three
of
them
and
they're
all
valid.
So
now,
if
I
do
a
get
request
for
blog,
this
should
still
be
Greene's
right
now,
if
I
do
/
blog
/
foo,
this
should
be
the
Blues.
It's
not.
What
did
I
do.
I
blog
/.
C
I'm
not
sure
anyway,
we'll
work
through
it,
but
this
this
is
the
idea
of
how
it
should
work.
I,
don't
want
to
kill
time
to
see
you
debug
this,
because
I've
been
smashing
to
see
them
all
around
on
the
screen,
as
you
can
see,
but
the
idea
is
that
this
file,
this
final
proxy
again
I'm
just
trying
to
demonstrate
that
the
all
the
includes
will
get
chained
together.
What
gets
will
get
included
all
together.
C
The
ugly
when
it's
shown
up,
oh
there,
it
is
that's
interesting,
so
it
is
blues,
so
I'm
not
sure
if
I'm
not
sure,
what's
up
with
that,
but
that
updated.
So
you
can
see
that
right.
So
such
blog
/foo
is
that
one,
if
we
add,
take
/foo
off,
we
should
get
green.
Now.
If
we
take
this
off,
we
should
get
the
root.
Yeah
and
I
can
go
on
forever.
You
know,
I
can
add
more
conditions
if
I
wanted
to,
but
adding
more
headers
and
stuff.
C
C
Get
to
the
blues
again:
I'm,
not
sure
why
we
have
this,
this
funky
thing,
but
that's
dead,
yeah,
so
I'll
work
out
this
demo
make
this
better
for
next
time.
It
will
have
some
better
examples
that
I
can
I
can
walk
through
with
you,
but
I
think
I
cover
everything,
Dave
I
think
I'm
pretty
sure,
without
describing
it
more
in
detail
with
the
docs
that
we
wrote.
B
Yeah,
maybe
do
okay
first
thing.
Thank
you
very
much
for
doing
that.
Demo.
Sorry
for
putting
putting
you
on
the
spot,
Oh
God,
the
the
big
picture
is
that,
like
we've
been
working
very
hard
on
this
for
well,
I
was
gonna,
say
since
since
that,
since
0:15,
but
it's
it's
been
it's
been
months
that
we've
been
workshopping.
These
are
using
these
designs.
B
B
There
are
two
new
ideas:
there
is
inclusion
which
replaces
delegation
and
Society
of
conditions,
which
is
a
more
generalized
form
of
the
straight-up
match,
keyword
that
we
used
to
have
before,
but
for
foreign
English
right
users,
we've
we've
written
a
basically
an
upgrading
guy.
So
basically,
if
you
had
this
before
users
before
and
if
you
scroll
down
a
bit,
you
can
see
that
both
basically
very
very
few
things
have
changed.
There
are
some
stuff
to
call
out
for
the
name
of
objects.
B
Tls
certificate
delegation
is
obviously
changed
as
well,
and
there
are
changes
to
rallying,
but
most
of
the
other
ones
say
no
change,
because
they
are
just
straight
straight
one
to
one
transition.
If
you
you'll
be
able
to
change
your
Gamal
and
you'll
be
up
up
and
going
again,
you
can
see
the
actual
Delta
is
pretty
pretty
small
between
it
in
terms
of
a
chile
proxy
fee
to
step
back
a
little
bit.
The
idea
of
inclusion
is
these
delegation
we
and
we
kind
of,
say
the
two
term
kind
of
interchangeably.
B
B
That's
that's
still
still.
The
same
model
conditions
are
a
way
of
saying.
If
I
delegate
over
to
you
I
want
to
potentially
restrict
some
of
the
things
you
can
do.
Sleeps
do
this
example:
a
scene
I
want
to
make
sure
that
there
is
a
you
know,
excellent
indication
header
on
every
request
that
is
handled
by
that
application.
B
Here's
a
kind
of
policy
decision,
an
administrator
administrator
mode
might
make,
and
so
the
way,
the
way
that
we
can
sexualize
the
way
that
inclusionary
condition
works
together
is
you're,
including
your
including
parts
of
other
fragments
configuration
and
combining
the
conditions
that
they
have
like
their
matching
conditions
of
any
this
header
and
in
this
prefix
or
the
suffix
or
whatever,
with
your
own
conditions,
and
so
that
we
feel
retains
the
I
beat
the
idea
of
delegation.
I
only
want
to
delegate
a
part
of
this.
B
You
saw
an
example
that
Steve
had
where
he
delegated
he
included
from
the
green
application
from
another
namespace,
but
also
included,
but
also
he
met
inclusion
added
the
condition
that
said
everything
starts
with
slash
blog.
So
that's
the
that's
the
way
that
in
the
old
ingress
rat
world,
you
were
delegated
slash.
What
else.
B
B
We
are
working
very
hard
to
get.
These
are
all
draft
up
in
the
moment,
working
very
hard
to
get
them
polished
up
by
the
week.
Then
the
information
that
we
want
to
transmit
will
be
will
be
in
them.
The
last
one.
If
you
can
just
go
back
to
the
proof
screen,
is
we
have
a
bunch?
We
also
have
an
upgrade
guide
for
just
straight
upgrade
tasks
in
the
background.
Nick
Young
who's
been
doing
a
lot
of
work
on.
B
Really
should
go,
we
talked
about
last
last
time.
We
met
leadership.
Leadership
involving
we've,
moved
away
from
the
restrictions
of
them
to
have
a
single
single
master.
Now
behaves
the
way
Nick
likes,
describe
it
as
proper
keeping
Eddie's
leadership,
which
is
they
do
they
choose
a
leader,
but
all
of
them
all
of
them
are
read-only
slaves
and
where
that
will
manifest
itself
by
the
time
we
get
to
100
is
there'll,
be
one
contour
which
won't
elect
itself
the
leader
and
it
will,
it
will
be
responsible
for
writing.
B
Status
back
status
remains
one
of
one
of
our
longest
longest
reign
issues
and
the
last
the
last
bullet
point
there
is
contour
0.15
remains
our
latest
stable
release.
This
is
this.
Is
again
this
kind
of
difficult
teenage
fades
where
we're
moving
from
the
monthly
point
release
cadence
that
we
had
before
to
this
is
polishing
it
and
beer
and
Peter
and
lease
candidate
process
where
Sarah
15
is
going
to
stay
our
latest
for
the
next
couple
of
months,
silly
until
November
I.
B
B
The
key
thing
is
that
the
latest
tag
still
points
to
0.15,
we're
not
we're
not
going
to
tag
biggest
in
our
release,
candidates
as
latest,
and
it's
going
to
drop
drop
them
on
people
because
they're
not
just
there
is
a
significant
upgrade
Delta,
but
also
like
we're
we're
removing.
We
are
difficult
new
introducing
applied
between
some
things
which
we'd
like
it
opting
to
conscientiously,
rather
than
just
dropping
them
on.
You
might
well
good
luck.
So
that
is
that's
pretty
much.
B
D
Five
Michael
here
so
I
think
I
I,
think
I
get
so
I
was
interested
in
sort
of
the
reasons
why
sort
of
switching
from
me
ingress,
router,
HTTP,
proxy
and
I-
think
I
I
get
that
now.
From
a
timing
point
of
view,
it's
not
great
for
us
just
in
the
we're
going
we're
happy
to
go
GA
or
generally
available
for
our
platform
in
the
next
couple
of
weeks.
D
So
we're
going
to
have
to
do
a
migration
from
nginx
across
to
contour
and
then
across
to
HCP
proxy,
and
then
we've
also
got
some
outstanding
issues
which
I
don't
know
whether
we
want
to
go
in
here
like
things
like
fall
back
and
SNA
health
checking
and
stuff
like
that.
So
I
think
this
is
good.
But
you
know
timing
is
not
great
for
us,
but
we
can
work
through
that.
But
thanks
for
the
background
on
sort
of
why
I'm
making
a
change
yeah.
B
B
Even
if
we
were
not
renaming
English
after
hosting
proxy,
the
the
change
from
the
change
from
delegation
to
inclusion,
which
sounds
sounds
big.
This
actually
isn't
more
straightforward.
I
concludes
her
a
top
with
a
lighter
now
they're
no
longer,
but
we
think
tucked
under
a
route
which
just
never
made
sense
conditions
are
what
people
have
been
asking
us
for
a
long
time
they
want.
B
So
let
me
I've
said
that
we
we're
going
to
keep
support
for
ingress
route
around,
but
it
is
difficult
to
back
port
features
into
it
because
the
truth
is
not
holes.
Is
that
and
just
like
in
a
kind
of
Python
to
Department
three
transition?
We
don't
want
to
keep
the
old
deprecated
version
around
and
in
and
continue
to
kind
of
back
port
features
to
it,
because
it
will
discourage
people
from
moving
off
at
the
first
place,
which
we
should
definitely
talk
offline
about
how
long
ingress
router
stays
around.
B
But
the
that
is
not
like
it's
not
just.
That
is
not
where
I
focus
is
at
the
moment.
It
is
this
to
deliver
the
food
to
the
people
been
asking
for.
We
literally
don't
have
this
box
in
the
old
English
yeah
more
like
it's
not
structured
in
a
way
that
will
let
us
do
that.
There
is
no
way
to
we
could
we
could
add
header
matching
kind
of
like
keys
to
route
objects,
but
the
the
that
would
suggest
somehow
it's
possible
to
delegate
on
a
header
which
was.
B
It
was
a
piece
of
design
that
tripped
us
up
for
months.
It
just
didn't
make
any
sense,
and
so
by
separating
the
idea
of
the
conditions
which
are
the
things
that
match
on
and
the
includes
which
are
which
configuration
do
I
grab
from
other
namespaces.
We
simply
we've
created
something
that
makes
more
sense
than
just
sticking
delegation
as
a
kind
of
pseudo
service
like
you,
either
send
traffic
to
a
service
or
you
send
it
to
a
delegate
that
just
wasn't
fun
scalable.
B
But
yet,
let's,
let's,
let's
definite
awk
offline
about
a
reasonable,
reasonable
deprecation
plan.
Like
there's
a
train,
not
not
continuing
to
do
not
continue
to
try
and
like
continue
to
try
and
back
port
bugfixes
English,
ending
aggressor
and
we're
moving
the
English
that
completely
took
weather
that
offline
yeah.
D
No
is
I
mean
I.
Think
from
our
point
of
view,
I,
all
sort
of
what
we
maybe
need
to
think
about
is
is
hold
off
now
cut
across
the
contour
is
the
primary
until
we
get
a
shaping
proxy
just
to
stop
that
churn,
I'm
not
worried
about
keeping
ingress
around
alive
forever,
like
you
know,
deprecated
stuff
and
get
rid
of
it
right.
D
B
The
that
gives
you
justice
for
why
we're
moving
quickly
to
this
is
when
we
get
to
wonder.
Oh,
this
is
like
one
dollar
of
a
product
like
we're.
This
is
our
opportunity
to
get
serious
about
backwards-compatibility
serious,
about
creating
a
stable
foundation
that
people
can
build
community
subjects
that
last
three
years
on
this.
B
Hopefully,
by
taking
the
pain
now
we
can
create
a
more
stable
place.
I
quit
I'm
very
serious
when
I
say
wonder.
Oh
is
like
that's.
Why
I
want
to
go
to
a
window,
not
this
zero
dot,
something
something
kind
of
not
non-committal
must
so
the
this
this
is
building.
This
is
our
attempt
to
build
a
foundation
for
documents
that
kuku
names
dockets.
B
Okay,
any
other
any
other
questions.
B
You
okay!
Well,
let
me
continue
with
the
release
theme
coming,
which
is
better
one.
This
Friday,
we
really
were
really
pushing
hard
to
get
it
out.
Last
Friday,
the
the
truth
was
we
weren't
we
weren't
quite
ready,
and
rather
than
push
it
out
in
a
state
that
would've
met.
We
only
have
to
do
another
race
till
week
later
to
be
like,
oh
yeah,
he's
quite
obvious.
B
Bugs
you
have
to
take
another
week,
give
a
bit
more
polish,
especially
we're
not
actually
coding
as
much
we're
we're
trying
to
get
the
documentation
to
us
into
the
form
because
Co
Bronson's
service,
but
if
the
documentation
needs
to
be
informed
that
you
can
make
make
make
usage,
you
can't
understand
how
you
do
it.
You're
not
gonna,
be
able
to
give
us
good
feedback,
and
it's
the
a
lot
of
the
effort
is
wasted.
After
that
we're
going
to
move
into
series
of
release
candidates
released
kind
of
one
it's
about
two
weeks
two
weeks
from
now.
B
Second,
one
will
do
another
move,
probably
enough
time.
You
know
to
a
second
release
candidate.
At
the
moment,
it
doesn't
look
like
going
to
a
third
release
candidate
like
hopefully,
by
that
time
we've
got
the
daughter
down
the
daughter
down
pretty
low
to
the
point
that
some
summer
in
November
we'll
be
getting
going,
but
we
we
put
the
$1
Monica
on
it
and
the
big
plan
is
that
we'll
see
everyone
in
San,
Diego
I
know
Stephen
Nick
will
be
there.
Tom
team
will
be
there
for
the
contra
for
the
contour
release
party.
B
So
that's
the
that's
the
kind
of
book,
the
both
the
horizon
that
I
can
see
as
far
as
November
and
also
to
say.
Well,
this
is
what
we're
really
focusing
on
for
the
moment
and
then
we're
going
to
take
a
step
back.
I
know
there
are.
There
are
a
lot
of
open
issues
on
the
backlog
and
we've
been
prioritizing
kind
of
trying
to
stabilize
the
features
that
we
have
now,
rather
than
continuing
to
add
into
that
set.
B
But
after
wonder,
though,
will
be
definitely
time
of
taking
stuff
and
saying
what
are
the
big
things
that
we
can
add
to
throw?
What
are
the
big
problems
that
your
that
Tonto
users
have
that
we
can
solve
it
in,
hopefully
in
a
more
holistic
way,
rather
than
rather
than
paying
kind
of
feature
whack-a-mole?
We
can
look
at
the
big,
the
bigger
issues
around
authentication,
a
big
one.
B
I
want
to
look
into
his
observability
I
want
to
go
back
to
take
a
serious
look
at
our
metrics
I
think
they're
a
bit
kind
of
sporadic
at
the
moment,
and
so
in
terms
of
the
administrators
who
are
looking
after
contour
clusters.
Do
they
have
the
do
they
had
the
information
they
need
to
help
them,
give
us
the
right
to
buy
the
information
and
if
we
need
to
get
involved
to
help
other
to
help
their
users.
When
they
say
look,
you
know,
I
deployed
this
HP
proxy
object.
B
I
can't
figure
out
why
or
my
application
saying
500
say
like
give
them
those
operability
tools.
That's
definitely
something
that
I
want
to
look
into.
But
that's
that's
something
probably
talk
about
Pro
talk
more
about
after
coop
con
or
certainly
after
the
next
call.
So
maybe
I
mean
we're
getting
really
close
to
the
compared
notes
that
I
have
there
any
other.
B
Well,
so
let
me
let
me
close
then
on.
Please,
please
give
us
feedback
about
HP
proxy.
You
can
give
that
to
us
in
any
form.
You
like
you
can
nag
us
on
Twitter.
You
can
come
under
the
kubernetes
like
you
can
raise.
Given
you
can
raise
github
issue
you
can
you
can
find
in
fact
you
can
find
a
particular
comment
and
get
committed
github
that
you
don't
like
and
leave
a
comment
there.
All
three
backers
is
one
only
welcome,
because
this
this
is
the
document
that
we're
pretty
confident
win.
B
We've
been
road-testing
these
ideas
internally
in
for
a
couple
of
months,
even
though
it
looks
like
it
be
changed
because
it
seems
to
be
a
whole
new
object.
If
you
look
at
the
upgrading
guide,
you
can
see
that
almost
all
of
the
ideas
have
been
brought
over
from
in
dorset.
It's
really
thin
the
notions
of
inclusion
and
conditions
which
are
the
the
they
the
two
changes.
Of
course,
bug
reports
were
only
received.
B
The
the
main
thing
we're
going
to
be
working
on
up
outside
of
documentation
and
examples,
and
all
that
good
stuff
is,
is
the
the
spittin
polish
around
status
around
improving
our
tests.
We
ran
into
n
tests
to
really
try
and
check
out
as
many
bugs
as
we
can
out
of
the
product
we
have
fixed
in
the
last
two
releases.
B
The
leash
account
hasn't
gone
below
100,
which
is
kind
of
psychological
blow
to
me,
but
the
the
number
of
long-standing
issues
in
terms
of
in
the
niggling
ones
of
correctness,
ones,
we've
fixed
an
awful
lot
of
them
over
the
last
two
releases,
so
I'm
I'm
feeling
pretty
confident
about
the
the
fidelity
and
the
quality
of
the
product.
We
have
helped
the
good
old,
Help,
Wanted
and
good
first
issues
on.
B
Github
they're
always
contributions
are
always
welcome.
There's
always
issues
tags
there.
If
you
want
to
get
involved
in
the
pro
project.
There's
a
really
interesting
one
about
setting
up
only
to
edit
llamo
ya
know
is
everyone's
favor
programming,
language
and
I
added
a
gambling
target
to
it
to
the
make
our
recently
I
would
love
it
if
we
could
buy
one
dodo
make
that
be
actually
turn
that
on
as
part
of
CI,
there
are
a
ton
of
niggling
yeah
well,
because
yeah
yeah
most
in
taxes
gives
you
no
guidance
whatsoever.
B
There
are
a
ton
of
little
niggling
things
that
we
need
to
address.
These
are
not
correct
in
cities
they
would
use
like
two
spaces
versus
one
and
a
Pegasus
based
on
all
the
other
annoying
stuff
in
Yemen,
but
we
need
to
address
all
of
those
before
we
can
make
that
Yemen
target
the
default
that
that's
just
one
of
the
one
of
the
places
that,
if
you're
interested
in
getting
involved
involved
in
project
and
yeah,
though
those
are
all
the
ways
that
you
can
get
in
contact
with
us.
B
A
I
do
have
a
yes,
a
quick
question
for
both
Dave
and
Steve.
Actually
so
looking
at
HTTP
proxy
here
and
we
we
have
the
beta
coming
out
on
Friday,
would
you
say
the
all
the
documentation
and
everything
is
stable
enough
to
do
a
quick
blog
post
on
the
demo
that
you
have
there
Steve
similar
to
the
kind
blog
post
I
did
earlier
a
couple
months
ago.
Just
so
people
can
see
hey
here's,
the
new
HTTP
proxy.
B
Absolutely,
and
to
talk
a
little
bit
more
about
one
of
the
things
that
I
I
want
to
improve
of
than
over
the
next
month.
We
have
October
for
this.
This
polishing
I
want
to
improve
over.
That
time
is
to
move
our
documentation
from
being
is
kind
of
very
factual.
This
is
the
name
of
this
is
the
this
is
the
name
of
the
field.
These
are
the
babies
that
accepts
to
talk
more
about
solutions
to
talk
more
about.
How
do
I,
you
know
like
to
take
care
the
questions.
B
B
How
can
I
make
sure
that
only
these
users
can
edit
the
configuration
with
this
website?
How
can
I
do
Bluegreen
deployment?
How
can
I
smoke
test
new
version
or
application?
This
is
something
I
totally
forgot
to
mention
one
of
the
one
of
the
features
that
we
added
was
mirroring
support,
so
you
can
nominate
one
of
your
backends,
so
you
have
the
standard
service
stanza
and
you
can
nominate
one
of
those
as
a
mirror.
This
is
a
feature
that
envoys
had
for
a
long
time.
I
wanted
to
turn
on
for
the
the
longest
time.
B
Basically
lets
you,
it
will
send
two.
It
will
send
a
copy
of
any
incoming
traffic
to
a
second
application
to
a
second
pod.
He
then
throws
away
the
response,
so
basically
you
can
have
an
application
running.
You
can
consider
it
read-only
mode
or
consider
it
if
you
wanted
to
smoke
a
test,
a
new
version
or
application
using
live
traffic
without
that
light
traffic.
You
know
without
actually
that
traffic
going
back
to
the
user
mirror
mode
is
a
really
good
way
of
doing
that.
B
This
comes
from
the
idea
of
cornering
which
is
used
in
in
layer,
3
layer,
3
network
II.
So
there
I
want
to
talk
more
I
want
and
I
want
its
structure.
Most,
the
documentation
will
be
on
project
contra,
oh
not
in
our
just
kind
of
github
documentation.
The
github
documentation
is
a
reference
manual,
but
I
wanted
to
talk
more
about
scenarios
and
the
ways
you
can
use
contour
to
salt
to
to
solve
problems
that
application
teams
have
had
away
how
do
I
serve?
How
do
I
split
my
application?
B
How
do
I
serve
that
of
two
clusters?
Haddaway
serve
it
from
two
pods.
How
do
I
do?
How
do
I
do
a
rolling
deployment?
All
of
these
questions
and
that's
I,
want
to
add
as
examples
as
tutorials,
and
if
you
look
on
the
Envoy
site,
they
have
a
section
called
learn
which
is
exactly
the
same
thing.
I
want
to
learn
how
to
do
this
specific
thing.
So
those
are
those
are
my
goals
for
improving,
not
just
the
factual
documentation,
but
the
resources
for
using
contour
assault,
particular
problems
that
application
new
status
and
others
have.