►
From YouTube: Contour Community Meeting - Sept 1, 2020
Description
September 1, 2020
News
Status output performance issue found by @mattmoor
[youngnick] I propose we fix it and cut a 1.8.1 point release.
What have we been working on?
Refactoring work
[stevek] DAG builder refactoring part 1
Issues
[stevesloka] External Name Regression
[zianke] Add clickable anchor links to the website
[jonasrosland] Will look into CII Badge Silver status
A
B
I
do
I'm
just
adding
a
link
to
the
finish
doing
that
there
you
go
that's
now
link.
Could
you
click
that
open
for
me,
so
matt,
moore
from
k
native,
has
found
a
performance
slow
down
under
heavy
churn.
That
looks
like
it's
always
there,
but
it's
unless
it's
only
really
noticeable.
It's
a
massively
noticeable
on
the
heavy
churn.
So
yeah
he's
found
that
he's
found
what
appears
to
be
most
of
a
fix.
B
There's
a
second
fix
that
we'll
bring
in
as
well
there's
pr
there
that
looks
good
to
me
and
james.
So
once
we've
got
those,
I
think
we've
merged
that
one
now,
once
there's
once
we've
got
the
two
fixes
merged
into
master.
I
am
proposing
that
we
cherry
pick
those
back
to
the
release,
1.8
branch
and
cut
a
release
1.8.1.
B
I
suspect
that
we've
had
some
other
reports
of
weird
problems.
We,
where
sometimes
the
status
the
status
doesn't
update
and
things
take
a
long
time
to
converge.
This.
This
performance
problem
is
because
the
way
that
we
do
status
at
the
moment
blocks
on
the
status
update
actually
being
applied
to
the
api
server,
and
so,
if
there's
a
lot
of
status
updates,
you
can
hit
the
api
server
rate
limit,
which
means
that
then,
the
dag
updates
cannot
complete
until
the
api,
server
status,
updates,
train
and
so
there's
two.
B
D
B
B
B
B
C
Chris
yeah,
I
just
threw
my
recent
pr
under
this
refactoring
bullet.
I
know
other
folks
have
been
working
on
refactoring
as
well,
but
I've
been
working
on
taking
some
of
the
work
that
steve
slocus
started
around
refactoring
the
code
that
does
dag
building
from
the
contour
or
ingress
apis.
It's
basically
starting
to
separate
things
out
to
be
a
little
bit
more
modular.
E
Yeah
so
someone
reported
an
issue
with
external
names
and
I
did
some
work
today
on
that.
I
think
it
might
be
a
regression
where
it
doesn't
work.
So
this
is
where
you
have
an
external
name,
and
you
want
to
route.
You
know
through
contour
through
envoy
out
to
some
external
resource.
So
I
think
what
I
found
is
that
the
header
rewrite
is
not
happening
at
this
point,
so
something
poke
into
just
something:
I'm
fully
written
test
against
it
to
prove
it.
But
it's
it
looks
like
it's.
It's
not
working.
B
E
F
B
A
D
B
Awesome
for
me,
I've
been
reviewing
prs
doing
gardening
and
I
spent
some
time
yesterday
having
a
look
into
moving
that
channel
that
we're
to
change
to
buffered
to
instead
use
one
of
the
kubernetes
client
go
work.
You
isms,
it
doesn't
look
like
it'll
work
very
easily
with
the
pattern
that
we've
got
at
the
moment,
and
we
think
the
pattern
that
we've
got
at
the
moment
is
there
for
the
reasons.
So
we
probably
won't
do
that
which
always
sucks
but
yeah.
B
A
So
for
contour
we
did
a
caia
best
practices
badge
a
little
while
ago
and
we're
at
passing
grade,
and
there
are
two
other
levels
above
it
so
silver
and
and
gold,
and
I
was
just
wondering
if
you
wanted
to
kind
of
start
looking
into
what
silver
would
look
like
the
when
you
start
looking
at
into
it.
We
already
have
a
lot
of
the
things
in
place
and
it
could
be
just
a
few
hints
essentially
on
on
how
to
make
sure
that
we
make
the
project
adhere
to
even
better
practices.