►
From YouTube: [SIG-Network] Ingress NGINX meeting 20210622
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
Hello,
everyone-
this
is
the
seg
network,
ingress
nginx
sub
project
meeting
today
is
june.
22Nd
2021.
This
is
a
kubernetes
community
meeting
and
we
ask
you
to
comply
with
the
code
of
conduct,
which
basil
very
means
be
excellent
to
each
other.
If
there
are
any
violations
or
issues,
please
report
them
to
the
fig
chairs
or
to
myself
privately
with
that
we
can
go
ahead
and
get
started.
We've
got
a
lot
of
ground
to
cover.
We've
got
a
big
update
coming
through
and
we
need
to
walk
through
that
and
discuss
that.
A
So
before
we
get
started,
we
have
some
new
faces,
some
new
members
on
the
team,
so
we
go
ahead
and
go
around
the
block
and
you
can
introduce
yourselves.
B
B
E
Okay,
so
then
it's
only
me
left,
so
I'm
noah
and
I'm
new
to
to
the
community,
and
I
want
to
to
get
involved
and
help
things
so
yeah,
I'm
looking
forward
to
it.
A
Awesome
thanks
guys
thanks
for
joining,
I
definitely
look
forward
to
helping
out
like
I
was
telling
we
I
met
and
talked
and
discussed
things
with
no
yesterday,
I
think
the
big
thing
is
just
we're
working
on
the
stabilization
of
products,
so
we've
got
three
big
focuses
right
now
as
an
organ
as
a
community.
One
is
the
122
release,
which
we've
got
a
lot
to
discuss
about.
A
That
ricardo
is
going
to
give
us
an
update
on
the
release
cycle,
understanding
what
our
release
cycle
is
going
to
look
like
and
making
that
a
little
bit
more
transparent
right
now.
It's
so
clue.
G
is
probably
the
best
word,
so
it
takes
some
time
so
we're
going
to
try
to
work
on
cleaning
up
the
release
cycle
and
then,
of
course,
looking
at
our
base
image,
because
we
do
it
takes
about
an
hour
and
a
half.
We
just
did
a
release
with
the
120
nginx
version.
A
It
took
about
an
hour
and
a
half
to
get
from
the
compile
time
to
build
to
about
three
hours
for
a
release,
so
we're
trying
to
look
to
figure
out
what
we
should
be
doing
from
a
community
perspective
on
that.
What
is
that?
Do
we
want
to
walk
through
the
the
triaging
of
some
issues?
Ricardo.
I
know
that
we've
got
a
lot
of
people
looking
at
things.
A
Is
there
any
major
things
that
we
need
to
look
at
from
right
now,
or
should
we
just
really
just
jump
into
the
open
topics,
because
I
know
that's
going
to
take
a
good
portion
of
time.
Yeah.
F
So
I
think
we
can.
We
can
go
to
the
open
topics
right
now
and
if
we
got
some
time
later
to
make
some
issue
ishitriash,
I
I
have
started
to
prioritize
at
least
the
ones
that
I
think
that
might
be
urgent,
like
that
one
from
segmentation
fault
and
that
other
one
that
was
a
new
pointer
in
the
admission
webhook.
That
is
solving.
F
A
Sounds
good
to
me
because
I
think
we
need
to.
We
need
to
get
on
to
the
get
the
122
fix
in
and
discuss
the
release.
Branching.
F
F
The
first
one
is
about
the
brand
management,
so
we've
been
discussing
from
like
for
a
while
if
we
should
keep
supporting
the
old
ingress
version
with
the
view,
one
better
one
and
what's
what's
our
support
window,
so
I
don't
know
if
everybody
knows
carlos,
but
carlos
is
from
c
release
he's
pretty
he
he.
He
got
some
pretty
expertise
in
in
branch
management,
and
I
asked
him
if
he
can.
F
He
can
help
me
with
this
branch
management
and
how
would
he
do
this,
this
branch
management
and
he
proposed
us
that
we
have
two
two
branches,
so
one
is
called
release
view
one
better
one
which
contains
the
old
ingress
version,
supporting
the
view,
one
better
one,
and
then
we
can
work
over
that
with
the
bug,
fixes
and
and
cutting
specific
releases
on
on
that
case,
like
yeah,
we
got
a
segmentation
file
that
we
need
to
fix
on
both
of
them
and
the
other
one
being
the
main
master.
Whatever
we
we
can.
F
So
the
idea
is,
if
we
find
some
bugs
in
previous
in
previous
in
previous
versions,
they
affect
both
versions.
So
if
they
affect
both
versions,
we
will
open
the
pr
and
cherry
peak
into
the
previous
branch
as
well.
Otherwise
we
work
on
the
on
that
specific
branch.
If
it
only
affects
like
the
older
version
or
the
newer
version
we-
which
I
don't
think
it's
going
to
be
the
case,
because
we
are
not
doing
a
huge
refactor
of
the
code,
but
only
dropping
the
support
for
v1
better
one
and
I've
asked
him
about
the
ci
jobs.
F
How
we
could
take
care
of
about
that.
So
we
should
probably
modify
the
ci
jobs
after
splitting
the
branches
for
specific
kubernetes
versions.
So
in
case
of
release
dash
v1
beta1,
we
we
are
going
to
keep
the
ci
the
ci
fests
for
kubernetes
version
116
to
121
and
for
the
the
new,
the
new
branch,
the
main
range,
only
keeping
from
view
v119
and
on
forward
yeah,
and
the
last
thing
about
this.
This
subject,
specifically,
is
that
yeah
we
are
gonna
have
this
was
actually
me
thinking.
F
So
james
knows
that
pain
about
couldn't
release
and
yeah.
We
are
probably
going
to
have
this
pain
for
right
now,
for
instead
of
one
branch
into
like
for
two
branches,
so
we
probably
need
to
think
better
about
the
automation
of
this
release,
cutting
as
well
otherwise,
you're
gonna
spend
like
one
day
one
when
one
whole
day
just
coding
releases
and
if
we
got
some
specific
updating
to
the
engine
at
space
image
and
not
in
the
final
one.
F
We
are
going
to
spend
like
two
days
doing
that
right
james,
because
it
takes
a
lot
of
time
yeah.
So
this
is
about
the
branch
management
and
removing
the
view
on
better
one
support.
F
A
F
I
wanna,
I
wanna,
really
move
this
forward
fastly.
So
probably
we
should
use
like
our
15
minutes
later
this
meeting,
to
make
some
issue
triage
into
the
more
critical
bugs
separate
them
as
things
that
we
need
to
fix
before
cutting
this
range
and
saying
yeah.
Okay.
So
now
we
are
freezing
the
support
for
v
for,
like
you
and
better
one,
and
we
are
just
going
to
accept
prs
for
the
main
range
if
they
target
the
new
release
right.
F
Yeah,
so
I
I
am,
I
am
reading
the
comments
on
that
one.
We
we
can
go
actually
through
that
one
later
today,
but
also
like
we
have
folks
from
inginx,
maybe
they
they
got
some
idea
of
that
that
as
well,
but
some
folks
they've
put
some
specific
thoughts
on
that
about
being
some
problem
with
with
luigi
and
not
with
inginx,
because
of
like
some,
probably
some
some
heavy
reloads.
F
So
I've
asked
it
for
wayne
and
for
elvin
to
make
some
comments
there,
but
we
should
probably
take
a
look
because
they
they
are
like
our
experts
in
lua
and
probably
they
know
if
there
is
some
impact
about
updating
the
luigi
in
the
container
for
some
newer
version.
I
I
am.
I
am
mostly
up
to
doing
that.
I
have
not.
F
All
right,
so
the
next
subject
in
the
meeting
agenda
is
about
view
embeddable
and
dropping
status.
It's
ready.
I
finally
could
manage
all
of
the
fading
tests
and
all
of
the
all
of
the
edges
of
the
of
the
ingress,
apparently
is
everything
working.
So
alejandro
did
a
really
really
really
great
job,
leaving
a
lot
of
ci
things
a
lot
of
e2e
tests.
So
I
am
pretty
confident
that
we
are.
We
are
going
to
have
some
problem,
but
not
like
a
big
problem
before
something
that
we
forgot.
F
Everything
is
working
just
fine
except
to
a
specific
point,
which
is
the
graceful
shutdown
that
I've
commented,
the
e3
test,
because
it's
failing
on
github
actions,
but
not
on
my
machine
and
I
have
tested
on
different
machines.
So
it's
probably
some
some
problem
with
timeout.
I
I
didn't
figured
out
that
yet,
but
I've
left
a
to
do
and
I'm
thinking
about
probably
opening.
I
need
to
open
an
issue
and
left
that
at
least
like
hey,
you
need
to
figure
out
what's
happening
here
and
and
grow
back
this.
F
C
Oh,
no
sorry,
I
just
had
myself
unmuted.
I
was
just
hanging
out,
but
yeah
I
mean
with
all
of
this.
I
mean,
if
there's
any
specific
areas,
that
we
can
be
most
helpful
on
to
to
kind
of
help
out
and
get
the
ball
rolling.
Like
you
know,
please
let
us
know
we
can
see
what
resources
we
can
get
looking
at
this
and
just
jump
in
where
we
can
help.
F
A
F
I
have
pretty
low
bandwidth
for
for
the
community
stuffs
here,
but
yeah.
We,
we
should
probably
start
discussing
about
that
after
we
cut
that
release
and
say,
hey
okay.
Now
we
support
also
weekly
yeah
right
because,
in
my
opinion,
this
being
like
a
community
effort
and
the
the
official
ingress
that
is
being
used
in
a
lot
of
stuffs.
It's
pretty
we.
We
really
need
to
have
like
that
that
kkk
api
support
as
well,
but
right
now.
F
I
would
like
to
ask
if,
if
you
have
some
time
to
take
a
look
into
the
issues
and
say
hey
yeah,
we
we
know
about
that.
We
can
help
them
that
we,
we
have
a
lot
of
issues
with
health
charts
so
but
we
have
people
working
on
the
health
charts.
I
guess
mostly
is
about
like
the
cold,
the
gocal,
the
ninja
ex
best
practices,
for
example.
So
we
we
could
make
some
usage
of
that
as
well.
C
Yeah
yeah,
that's
that's.
Definitely
I
I
will
let
brian
comment
on
the
the
api
or
the
gateway
api
topic,
as
he's
been
looking
a
lot
more
into
that,
but
we
can
definitely,
you
know,
look
through
the
topic.
Look
through
the
issues,
see
if
there's
anything
that
you
know
we
have
the
cycles
to
to
address
and
anything
like
that
and
yeah.
Like
you
said,
if
there's
anything
specific,
like
the
you
said,
I
heard
there
were
some
crashes
of
maybe
related
to
lua,
possibly
not
nginx.
F
C
No
man
yeah,
that's
always
fun,
to
try
to
spend
that
many
up,
but
you
know
it.
It
sounds
like
we
can
at
least
get
a
baseline.
We
can
probably
recreate
it
to
a
certain
extent,
but
with
that
many
and
depending
on
the
features,
I
think
you're
right,
leaning
towards
it
being
an
issue
with
lua.
You
know
causing
issues
there.
A
C
Yeah,
I
think,
there's
probably
going
to
be
a
lot
of
that
so
yeah.
I
would
be
more
than
happy
to
dig
through
that
one
just
get
an
idea
of.
What's
going
on
and
yeah
with
like,
but
like
I
said
with
that
many
ingress
resources,
I'm
not
entirely
surprised,
but
yeah
I'll,
be
good
to
look
at
it,
see
what
functionality
they're
trying
to
use
that
could
be
adding
to
their
problem
right.
C
A
Okay,
definitely
yeah
load
testing,
I
think,
would
be
a
big
bit
how
you
guys
do
load
testing
understanding,
how
you
do
that
and
how
we
could
replicate
it
from
a
community
perspective
would
be
helpful.
I
think
just
so.
We
can
see
when
we've
got
issues
like
that,
but
other
than
that
from
the
discussions
around
the
branch
management
or
anything
else.
That
ricardo
talked
about
any
comments
or
questions
or
concerns.
You
guys
have.
C
I
mean
it,
it
seems
pretty
well
thought
out
to
me
brian,
any
any
comments
around
that
I
think
you're,
probably
the
better
one
to
talk
about
that.
I'm
I'm
out
of
the
branch
management
stuff
for
a
long
time
here.
So
I
don't
want
to
overstep
my
bounds.
D
I
I
was
about
to
say
what
would
it?
What
do
you
mean?
Damien?
No,
I
mean
this
is
this
looks
well
thought
through
and
from
from
our
perspective,
you
know
this
is
this
is
what
you
guys
sort
out
to
to
work
through
the
to
work
through
the
project
right,
we're
we're
here
to
help
we're
here
to
support
we're
here
to
we're
here
to
provide
resources
as
we
can,
so
we
we
want
to.
We
want
to
make
sure
that
the
project's
successful
and
that
and
that
you
folks
can
can
keep
moving
forward.
That's
that's!
That's
re!
D
C
And
I
think
one
of
the
other
things
we
would
think
that
might
be
helpful.
Is
I
don't
know
if
there's
any
like
sort
of
housekeeping
work
that
you
know
what
might
be
helpful
to
have?
We
just
got
a
new
person
on
our
team
who's,
doing
a
kind
of
program,
management,
sort
of
work,
but
very
technical
background.
So
I
don't
know
if
that
would
be
helpful
too
to
just
kind
of
put
some
sanity
around
it.
C
A
I
I
definitely
think
I
that
would
be
helpful
to
me,
because
that's
the
role
that
I
feel
like
I'm
trying
to
help
just
triage
and
direct.
So
that
would
be
helpful
from
that
perspective.
But,
okay.
B
A
Go
ahead
and
carter:
do
you
wanna?
Did
you
say
we
wanted
to
work
through
the
branch
management
stuff
now
or
are
we
just
do
we
wanna
I've
got
time
later
today?
I
don't
know
what
your
day
looks
like.
We
want
to
actually
try
to
cut
the
release
today,
but
I
can
just
push
back
if
there's
some
time
this
week.
Should
we
just
look
at
schedules
and
try
to
get
that
scheduled
out,
so
we
can.
We
haven't.
A
A
F
About
having
a
lot
of
books
or
to
to
to
close,
but
as
well
like
we
can,
we
can
use
some
sherry,
picking,
better
and
say
yeah,
so
we
we
are
working
into
like
fixing
those
bugs
and
parting
them
to
the
previous
movie.
So
would
I.
F
That's
too
much
overhead
you
mean
for
that
release
yeah
after
that
yeah.
We
should
probably
make
that
release
as
well,
because
of
that
admission
controller,
no
pointer-
I
just
didn't-
have
enough
time
to
make
that,
but
as
an
example,
long
long
he's
not
here
but
he's
asking
to
be
more
helpful
and
he
wants
you
to
to
help
with
that
as
well.
So
you
can,
you
can
sing
with
him
if
you
want.
B
F
F
A
F
That's
the
approved
one:
that's
you
are
almost
there
we
dropped
you
one
better.
One
yeah
you
passed
it
seven,
one.
Five,
six.
F
A
A
Okay,
so
you're
just
asking
people
to
test
it
for
us
before
we
merge
it
in.
F
No
actually,
I
I
want
to
merge
it
and
cut
enough
of
a
religion
as
for
people
to
test,
but
I
wanna
I
wanna
I
wanna
before
merging.
I
want
some
folks,
like
elvin
and
like
anyone
that
wants
to
make
some
fast
review
and
see
if
I'm
forgetting
something
I
am
probably,
and
this
is
why
alpha
releases
the
exists
right.
F
Yeah
yeah
yeah-
I
I
can
add
you
and
carlos
as
well.
You
just
need
to
open
a
pr
on
my
on
on
a
repo
and
I
can
and
they
can
approve
that.
F
Okay,
the
last
thing
on
the
agenda
topic
from
my
side
is
the
bugs
and
priority
bugs.
So
this
is
actually
what
I
wanted
to
do
with
you
folks
right
now,
I'm
doing
some
triage
into
critical
or
prioritizing
issues
like
that,
one
with
the
new
point
there,
but
I
need
some
help
to
look
into
them
and
at
priority
confirmed
that
it's
actually
an
issue
or
it's
a.
B
F
And
I
am
not
pretty,
I
am
not
pretty
available
to
triage
all
of
them,
so
I
want
at
least
to
confirm
which
one
is
actually
really
a
bug
that
we
should
take
care
of
in
like
a
short
thing
and
which
one
is
like
yeah.
This
is
a
bug,
but
there
is
a
workaround.
It's
not
like.
You
are
not
getting
a
panic
as
an
example.
It's
not
it's,
not
a
segmentation
fault
right.
F
Them
so
the
newest
first,
I
would
go
into
the
actually
the
the
orders
first,
so
we
can
close
them
if
they
are
not.
C
F
F
F
Yeah,
so
I
wanna-
I
wanna
use
this
like
as
a
way
of
filtering
them.
So
if
this
is
a
really
a
bug
or
a
security
issue,
you
we
can
use
like
important,
critical,
urgent,
otherwise
that's
an
important
soon.
Otherwise,
if
that's
some
sort
of
cleanup
important
long
term
right,
so
it
would
be
helpful
for
us
to
at
least
look
into
the
which
of
them
really
needs
our
attention
on
which
of
them.
It's
not.
A
C
F
Yes,
I
need
some
help
with
that
yeah
cool
yeah.
Definitely
so,
let's
take
a
look
into
that
one
why
this
search
range
is
not
working
properly
with
proxy
protocol.
This
is
like.
A
Yeah,
I
think
we
we
looked
at
it
last
and
he
just
keeps
reopening
it
so
go
back
up
to
the
top.
This
is
part
of
what
I
was
asking
noah
to
do
for
us,
so
just
look
at
unlabeled
tickets
or
older
tickets
and
asking
them
to
test
with
newer
versions
or
ask
if
it's
still
an
issue
or
a
priority,
so
there's
a
lot
to
go
through.
We
just
need
to
continue
to
work
through
them.
B
F
F
A
A
F
F
F
F
F
A
F
A
It's
no.
I
can't
tell.
F
A
A
A
C
A
F
C
B
C
C
Am
okay?
F
C
C
C
Bots
they
are
cool,
hey.
I
I
used
to
give
make
fun
of
one
of
my
friends
because
she
started
spending
more
time
in
powerpoint
than
in
the
terminal,
and
I
got
to
that
point
now
as
well.
So
hopefully
I'm
going
to
be
able
to
claw
back
a
little
bit
more
of
the
terminal
time.
F
Okay,
so
we
got,
we
got
another
issue
with
canary
right,
the
first
one
that
that
that
there
is
already
a
pr
take
a
look
into
the
go.
Go
back
to
the
issued
list.
Oh
there's
another
one.
F
F
F
A
B
F
F
F
It's
35.
F
F
F
F
F
C
Well,
that
is
one
of
our
engineers.
I
was
making
comments
there,
so
we
can
always
see
if
they've
had
a
chance
to
look
at
this
again.
A
C
Yeah,
let
me
give
you:
let
us
try
to
do
that
here,
because
defend
is
one
of
our
one
of
the
core
engine
x
engineers,
one
of
the
you
know:
old
school
old
school
been
riding
nginx
for
years,
so
he's
a
good
dude,
but
yeah
it
seems
like
this
is
a
bug
with
mod
security,
less
than
a
bug
with
the
ingress
resource.
So
there's
a.
A
Is
that
already
it's
still
labeled
you
want
me,
I
think
we
should
put
this
on
the
backlog
better,
more
important,
long
term,
probably
yeah
yeah.
F
That's
not
a.
I
wouldn't
say
that
this
one
is
something
like
a
stop
point
for
us
for
moving
forward.
Yeah,
not.
F
E
F
A
F
A
C
Yeah
well,
and
even
just
that's
a
that's
just
a
big
config
problem
right,
because
it's
reading
it
all
into
memory
and
and
trying
to
execute
that,
but
yeah
we
will
will
definitely
cause
some
extra
headaches
there
and
it's
does
it
call
out
I'm
just
kind
of
scrolling
through
here:
does
it
do
they
link
off
to
their
ingress,
configure
just
more
details
on
what
they're
doing
with
it
in
here.
A
Not
on
the
original
okay,
but
there
is
some
somebody
there's
a
lot
of
people
confirming
the
issue.
Yeah
yeah.
C
F
So
some
folks
say
that
this
went
away
when
they
downgraded
from
0
45
to
0
43.
Like
that
comment
in
may
3rd,
one
thing
that
we
should
probably
do
later
james
is
compared
between
both
tags
and
see.
If
the
update
from
alpine
was
only
the
thing
that
was
actually
updated
of,
if
the
lua
was
updated
as
well,
what
what
else
was
updated
right?
F
C
E
E
A
A
F
C
A
D
A
A
C
A
F
F
B
F
Yeah
digging
into
the
cold
and
seeing
exactly
what
changes
right:
okay,
yeah!
So
we
have
three
more
minutes,
james,
so
yeah
so
for
for
now,
during
the
afternoon,
I'm
I'm
gonna
see
with
you
about
creating
that
new
branch.
A
F
We
can
and
what
what
I
think
we
can
do
is
actually
prioritize
that
cordon
theme
and
if
we
find
why
exactly
that's
happening
so
then
we
we
are
going
to
share
repeat
that
to
the
best
version
as
well.