►
Description
[SIG-Network] Ingress NGINX Bi-Weekly Meeting for 20211207
A
Hello,
everyone
thank
you
for
joining
today
is
december
7th
2021.
This
is
the
sig
network,
ingress
engine
x,
sub
project
meeting
and
as
always,
this
is
the
kubernetes
community
meeting.
We
ask
you
to
comply
with
the
cut
of
conduct,
which
is
basically
be
excellent
with
each
other.
If
you
have
any
issues,
please
report
that
to
the
governing
body
and
or
myself
or
ricardo,
and
with
that
we'll
go
ahead
and
get
started.
So
we've
got
a
lot.
A
We've
got
action-packed
meeting
today,
we've
got
a
lot
of
stuff,
so
thanks
for
that,
noah
you've
done
been
doing
an
awesome
job
of
keeping
us
on
our
toes
making
sure
that
things
need
to
be
reviewed
or
looked
at.
I
don't
think
we
have
anyone
new
today
go
ahead
and
double
check,
nope
pretty
light
today,
as
we
expect
for
the
holiday
season,
so
we
can
go
ahead
and
skip
that.
A
B
Yeah
I
I'm
up
to
if,
if
noah
is
okay
with
that
as
well,
I
am
up
to
maybe
skipping
the
triage.
I
I
I
owe
you
folks,
a
lot
of
triage
and
a
lot
of
reviews
as
well.
I've
been
away
the
last
a
few
weeks,
traveling,
so
probably
this
weekend,
I
will
have
some
time,
but
I've
been
mostly
focused
on
the
security
stuff,
but
I
think
that
we
should
probably
so
I
actually
know
do
you
think
there
is
something
really
urgent
that
we
need
to
take
a
look.
B
Otherwise,
I
would
just
say:
hey
if
you
see
something,
that's
that's
like
important
and
they
both
keep
cycling
like
putting
this
tail.
We
can
do
a
life
cycle
frozen
on
that
and-
and
maybe
a
think
like
postpone
that
I
can
take
a
look
at
that
as
well.
That's
okay,.
C
So
the
thing
I
do
is,
I
usually
go
through
the
oldest
ones,
that's
also
the
ones
I
I
always
mention
here,
but
there's
nothing
really
really
really
important.
I
think
that
was
so.
I
was.
A
C
A
Thinking
this
one,
because
I
don't
know
how
much
bandwidth
alvin
has,
I
know,
there's
a
couple
other
lua
things
out
there
and
I
saw
this
one
I
didn't
know
if
we
wanted
to
reach
out
to
alvin,
if
he's
even
has
the
capacity
to
help
or
if
we
need
to
reach
out
and
get
support
for
lure
elsewhere,
we
can
pull
this
one
up
and
we
can
talk
about
it.
That's
the
only
thing,
other
other
stuff
looks
pretty
similar
right.
Like
you
said
you
know,
ricardo
needs
some
status
and
follow-up
and
reviews
on
some
things.
A
I
think
this
one
actually
is
a
bug.
I
was
going
to
look
at
this
one,
so
I'll
probably
assign
this
one
to
myself,
but
I
think
this
one
is
probably
the
main
one.
We
should
probably
look
at
if
we're
just
because
it
no
one
else.
No
one
on
this
call
is
a
little
expert.
We
should
probably
have
that
conversation
yeah
so.
B
You
know
like
from
my
side,
if
I
could
change
from.
Let's
be-
let's
be
really
honest
here.
So
if
I
could
change
from
lua
to
like
using
njs
and
using
javascript
would
be
better
to
maintain
for
my
site,
because
I
don't
know,
don't
know
lua,
I
don't
know
javascript
either,
but
javascript
is
like
better
to
understand
than
bula,
but,
as
we
were
speaking
like
with
jintao
and
alvin
and
other
folks,
I
guess
like
open
rest
is
pretty
well
used
on
around
there
right.
B
So
I
think
that
we
should
at
least
like
try
to
make
a
separate,
specific
meeting
with
lower
folks
and
say
hey
folks,
so
we
need
your
help
or
we
need
to
think
on
another
approach,
because
it's
it's
like
hard
for
folks
that
maintain
that
that
are
maintaining
with
you,
maintaining
like
ingress,
enjoyments,
plus,
maintaining
lua
plus
maintaining
health
shards,
please
maintaining
a
lot
of
stuff
and
like
we
don't
have
all
of
that
that
expertise
here.
B
So
how
you
folks
think
about
you
can
help
us
if
you
look
like
the
past
cves,
the
majority
of
them,
where,
because
of
some
something
in
in
lua
right
and
I'm
not
saying
that's
bad
at
all,
like
I
think
that
lua
is
open.
Rusty
is
a
pretty
amazing
tool
that
that's
been
helping
like
kong
is
all
built
over.
That
was
all
built
over
there
as
well.
I
just
think
that
maybe,
if
we
can't
maintain
that,
probably
we
should
think
about
some
other
approach
that
we
can
maintain
right.
B
It's
not
like
a
a
a
short
term
or
a
midterm
change
in
my
opinion,
but
I
think
that
we
need
probably
to
have
this
conversation
and
think
how
can
we
evolve
into
something
that
more
people
can
just
jump
in
and
maintain
right?
Because
I
honestly
I'm
not
looking
right
now
into
learning
a
new
language
like
learning
lua,
as
I
am
just
dealing
with,
go
hell
and
to
go
python
and
yeah.
So
it's
it's
pretty
hard
and
even
like
open
rest.
B
You
have
a
lot
of
stuff
in
c
right,
so
the
previous
chord
that
we've
got
was
like
a
c
problem
that
we
needed
to
reach
when
open
rest
in
maintainer,
and
then
they
could
figure
out
what
was
the
real
problem.
So
I
am
just
up
to
maybe
trying
to
have
less
external
stuff
in
ninja
next,
but
this
is
my
opinion.
I
I
I
I
think
that
we
should
probably
have
this
honest
conversation
with
between
all
of
all
of
us
and
say
hey.
B
This
is
the
path
that
we
want
to
take
or
no,
we
can
still
stick
in
our
path,
but
we
need
some
support
from
the
community.
Otherwise,
it's
just
a
maintainable
values.
A
B
Open
rusty,
let's
open
rusty
from
rest
rest,
you
know
rest
rest
in
peace,
yeah.
B
Yeah
cool,
so
I
was
talking
also
with
with
alejandro
those
days
like
we.
We
usually
speak
some
random
stuff,
and
apparently
there
are
some
other
things
like
arising
in
angina
x.
I
guess
web
assembly
or
something
like
that.
So
I
think
we
need
to
probably
think
in
a
long
term
what
we
want
to
do
right.
So
we
know
that
we
want
to
move
to
gateway
api.
B
We
know
that
we
need
to
split
like
the
controller
from
gynx
and
all
of
those
things
they
are
walking
so
damien
that
it's
it's
it's
an
item
in
our
agenda,
like
damien,
did
some
cool
job
like
splitting
open
telemetry
from
giants,
and
I
want
to
use
that
as
a
base
for
like
mod
security
and
other
models
as
well.
B
But
I
think
that
this
is
like
things.
Let's
say
those
are
things
that
that
that's
a
that's
a
janitorial
job
that
we
are
doing
right
now
right.
So
we
are
cleaning
up
things.
We
are
making
them
slim,
but
we
need
to
think
in
a
long
term
what
we
want
to
do
from
the
project.
That's
my
my
opinion.
A
B
Probably
more
profitable
than
lua,
but
yeah
yeah.
I
would
say
that
even
from
nginx
folks
right,
because
njs
is
a
really
new
technology,
that
nginx
has
been
using
new
like
two
or
three
years
old,
but
I
can't
see
a
lot
of
people
using
that
right.
So
it's
it's
something
that
even
for
engine
x
for
f5,
it's
something
new,
also
the
if
the
performance
is
worse
than
open
rest,
it's
up
to
to
f5
folks
and
in
ginax
folk
fives
to
say:
hey!
Okay!
We
can
do
that
better
than
open
rest.
B
You
right
so
sorry
carol,
but
would
be
like
a
challenge
for
you
like
hey.
Why
aren't
we
using
everything
that's
on
core
of
nginx,
because
openrest
is
faster
than
njs,
so
f5
folks
needs
to
fix
that
right.
That's
like
my
fake
on
that.
A
You
brought
it
up
just
moving
on
to
the
next
thing,
the
splitting
up
the
ingress.
Do
we
just
need
more
folks
from
the
community
to
do
testing
on
that
one,
so
you
assigned
yourself
to
it.
I
was
just
asking
what
what
do
we
probably
need
more
testing.
B
Yeah,
so
I
think
it
would
be
good
like
some
like
you
me
and
other
folks
that
been
doing
dealing
with
image
building.
We
actually
need
to
take
a
look
into
how
this
can
improve.
So
what
are
the
caveats
of
that?
What
are
the?
What
points?
Are
we
missing
on
that
right?
Because
that's
a
that's
a
big
change.
B
We
are
just
saying
hey
now,
if
you
want
to
run
a
model
in
ingress
controller,
you
need
to
you
need
to
add
a
sidecar
and
mount
that
following
that
model
as
a
as
a
an
empty
volume,
or
something
like
that
right.
So,
if
that,
if
that
take,
is
right,
we
are
to
get
some
some
good
things
for
the
community
and
even
for
kubernetes
folks
right,
because
we
are
going
to
make
the
size
of
our
image
really
smaller,
but
we
we,
we
can't
make
this
more
complicated
there.
B
It
is
so
I
would
have
like
a
second
click.
I
didn't
look
it
into
damien
piaria.
I
just
did
a
zoom
with
him
because
he
he
asked
me
like
hey.
Can
we
just
make
a
quick
shot-
and
I
say
hey-
this
is
my
my
take
on
that
and
he
was
yeah
cool
let's.
Let's
do
this
way
right,
but
this
would
probably
became
like
a
framework
if
people
wanna,
for
example,
hey,
I
wanna,
add
this
model
into
ingredient
ginettes,
and
so
how
can
I
do
that
right?
Can
I
just
build?
B
Can
I
what's
the
read
me
of
that
for
for
exchanging
gynex
with
other
models
right,
so
we
need
first
of
all,
we
need
to
see
if
this
is
right.
If
this
is
this
is
the
right
approach
that
we
are
taking
and
then
we
probably
should
write
like
hey.
If
you
want
to
add
a
third-party
module
and
we
don't
accept
it,
we
don't
accept
it.
You
still
can
use
that
making
building
this
way
and
adding
as
a
side
car-
and
this
is
the
way
that
we
do
we
do
so.
B
I
think
that
in
a
mid-term
this
is
going
to
be
huge
right,
so
this
is
going
to
be
a
huge
take
into
how
we
building
raising
gynex
and
how
we
turn
that
into
like
responsible
for
other
nginx
models
that
people
wanna
wanna
use.
So
I
would
at
least
that
folks
take
a
look
into
that
and
say
hey.
This
is
cool.
This
is
not
cool.
This
works.
B
You
are
missing
this
point
right,
so
you
you
are
missing
this
this
this
thing
here
and
and
another
better
than
like
people
really
using
that
that
to
to
review
and
say
that,
like
and
say,
hey
yeah,
you
are
missing
this
thing.
This
is
going
to
break
users
anyway.
I
don't
plan
to
like
make
this
as
a
minor
release
or
something
like
that.
The
same
way
we
did
before
I've
learned
it
with
my
mistakes
right,
the
sanitization
stream,
but
yeah.
A
This
I
mean
this
definitely
would
be
a
a
major
change.
Okay,
I
can
I'll
add
it
to
my
list
of
things
to
test.
So
I
think
I
was
gonna.
I'm
gonna
go
ahead
and
assign
this
one
to
myself
the
persistent
one,
because
they
put
in
a
lot
of
issues
in
that
one.
So
I
will
I'll
add
this
to
my
backlog
of
my
stuff,
so
it's
8,
13
80
13
to
review
8013
tests.
A
Okay,
this
one-
I
don't
know
if
you
had
a
chance
to
look
at
it,
looks
like
the
stickiness
isn't
working
with
the
original
pod
after
it's
been
mapped
out,
so
I'm
going
to
scroll
all
the
way
down
to
their
test.
A
He
actually
does
a
really
good
job
of
mapping
this
all
out,
so
one
everything
looks
good
the
hash
it
goes
to
the
same
pod
same
podca,
pod
deletes
it
uses
the
same.
A
Cookie
doesn't
go,
it's
not
going
to
the
same
one,
every
single
time
now,
but
now
I
I
was
going
to
go
ahead
and
test
this
just
to
validate
that
this
is
an
issue,
so
I'm
going
to
replicate
this
and
then
we'll
figure
out
where
to
go
from
there,
so
I
at
least
want
to
be
able
to
replicate
and
accept
the
triage
on
this
one.
So
that's
what
I'll
do
for
this?
For
myself,
how
does
it
work?
Is
it
some
lua
magic.
B
That's
a
good
question:
yeah
yeah
it
is,
it
used
to
be
a
annex
and
then
it
turned
to
be
into
a
lua
magic,
yeah.
D
Magic
yeah,
I'm
actually
curious,
also
like
what
what
technique
it's
using
to.
I.
B
Would
I
would
I
would
ask
some
fine
like
for
alvin
or
someone
to
make
a
walkthrough
into
lower
code,
because
every
time
I
need
to
change
something
there?
I
keep
like
hitting
my
head
on
the
wall
and
saying:
hey.
Probably,
I
will
break
something
here
instead
of
fixing,
but
that's
overall,
how
like
how
lua
works
here?
I
don't
know
if
you
know,
but
the
thing
is
that
like
when
you
what
it
does
is
actually
it
returns
for
you,
the
back
end
right.
B
So
what
what
it
makes
is
like
when
you
hit
that
part
of
the
code,
lua
runs
and
say
hey.
So
if
you
have
this
condition
on
that
condition
on
that
condition.
So
from
this
table,
I'm
going
to
return
to
you
this
backhand.
B
So
that's
all
of
all
of
what
it
does
and
that's
the
same
way
that
njs
works
and
that's
the
same
thing
for
openssl
for
tls
certificates,
so
that
asset
that
lua
by
block
something
what
it
does
is
actually
it
it
feels
it
returns
to
engine
x
what
it
should
present.
So
that's
mostly
like
a
string
that
gets
returned
like
what's
the
balancer.
What's
the
certificate
or
something
like
that.
A
A
Okay,
so
that
one
I
know
we
weren't
going
through
the
list
so
that
one
this
one.
A
Was
old
and
it's
pointing
to
main,
but
I
know
someone
asked
about
his
stream
snippets
so
adding
a
new,
a
new
snippet
for
adding
streams.
It
looks
it
looks
fine
in
the
code.
I
did
a
review
of
it,
but
I
didn't
know
why
it
was
closed.
It
looked.
I
don't
see
why
it
was
closed
at
all
and
the
only
problem
I
have
with
it
is
that
it's
pointing
to
main
anything
other
than
that
it's
just
pretty
straightforward
as
a
snippet
adds
it
in
the
lure
code
adds
it
to
the
documentation.
A
A
The
only
other
thing,
the
only
the
only
question
I
have-
is
it
since
it's
a
new
snippet
does
this
person
have
to
do
anything
with
the
the
block
list
that
we
put
in
place?
I
don't
know
if
everything's
covered
by
it,
because
it
looks
at
all
snippets.
I
I
can't
remember
either,
but.
C
And
maybe
change
the
target
branch
yep.
C
A
Okay,
I'll
go
ahead,
and
do
that
talked
about
that
one,
this
one,
I
don't
remember
somebody.
Oh.
This
was
an
older
issue
that
I
was
brought
up
in
during
a
slack
conversation,
so
it
looks
like
there
might
be
a
breaking
change
from
an
older
version
with
path
types.
A
D
We
had
a
a
big
internal
issue
where
teams
were
blaming
each
other
and
I'm
like
all
right.
I'm
gonna
look
into
this
and
I
found
all
the
code
responsible
for
it.
I
don't
know
it's
not
it's
not
a
bug.
It's
just
that
like
when
you
switch
from.
I
don't
think
that
extensions
v1
beta
1
or
whatever
the
old
api
version
was
defined
the
behavior
for
path
matching,
but
now,
with
networking
api
version,
I
think
v1,
both
v1
beta,
1
and
v1.
D
So
that's
a
dot,
basically
they're
they're
their
path
matching
ends
in
a
in
a
period
not
in
a
slash,
and
now
the
ingress
specification
says
that
path
matching
should
be
on
a
slash
boundary
and
alejandra
made
that
change
back
at
some
point
and
when
we
upgraded
to
the
version
that
had
that
change.
Everyone
had
this
unexpected
behavior,
because
they
hadn't
realized
that
the
spec
changed
in
being
all
implementation,
specific
path
matching
to
now
it's
slash,
boundary
path,
matching
and
nginx
location.
D
That's
just
prefix
matching,
that's
never
been
slash
boundary,
so
it's
kind
of
an
additional
thing
that
the
kubernetes
ingress
spec
added
in
for
us.
I
don't
since,
since
this
adheres
to
the
spec.
I
don't
know
that
it's
like
a
bug,
but
it's
definitely
something
that's
going
to
come
up
with
people
who
are
upgrading
that
we're
relying
on
that
behavior.
D
D
B
Right
so
remember
when
I
was
saying
that
in
past
the
main
problem
that
I
was
fighting
was
like,
because
of
you
and
better
one
like
the
pet
prefix,
the
peptide
didn't
exist
and
then
it
started
to
exist
and
they
have
changed
the
way
it
was
implemented.
So
there
wasn't
like
a.
I
can't
say
there
was
like
a
breaking
change.
There
are
some
some
care
about
the
breaking
changes
inside
the
resin
api.
B
Nothing
raising
ingredients,
but
all
of
the
ingress
is
because
of
it
was
still
like
a
v1
data
api
right
and
but
to
be
honest,
I
don't
know
if
we
are
doing
this
right
now,
the
right
way
or
not.
D
There's
another
edge
case
here:
if
the
server
block
has
regex
enabled-
and
if
you
haven't
looked
at
that
logic
before,
if
either
any
of
the
ingresses
in
under
that
host
name,
have
used
regex,
true
or
any
of
them
have
rewrite
target.
True,
then,
all
of
the
location
directives
under
that
host
name
under
that
server
block
now
are
set
up
with
regex
and
that
still
is
prefix
matching,
because
it's
just
carrot,
then
the
location
and
it
doesn't.
It
doesn't
put
a
slash
on
the
end
of
it.
Okay,
so
so
you
can.
D
D
A
I
don't
like
the
volunteering
people,
but
tom.
It
sounds
like
you've
got
the
best
handle
on
this.
A
A
Do
you
want
me
to
open
it?
Well,
we've
already
got
an
issue
open.
You
want
me
to
just
assign
this
one
to
you
sure.
Will
that
help.
I
don't
know
what
would
be
most
helpful
for
you
for
a
reminder.
D
A
Well,
that's
good
thanks
for
that.
Okay,
I
think
we've
gone
through
all
the
ones
that
folks
have
asked
about
in
slack.
Recently,
we've
gone
through
most
most
of
these.
I
think
we're
good
from
that
respect.
So
now
that
we've
worked
through
all
of
those
issues
and
we've
done
some
of
that,
we've
got
two
things
that
I've
seen
the
last
two
updates
to
the
helm.
A
Chart
nobody's
updated
to
read
me
so
I've
seen
two
come
through
and
it
still
has
the
old
update
to
one
one:
zero,
so
nobody's
updating
the
helm.
Chart
read
me
so
when
I
get
the
artifact
email,
I'm
not
seeing
updates
to
that.
A
So
I
just
want
to
remind
folks
that,
when
we're
doing
updates
to
the
hell
and
short
the
home
shot
has
its
own
separate
readme
or
a
change
log
that
needs
to
be
updated
and
then,
of
course,
the
fun
I
haven't
seen
the
email
yet
on
the
dev
group,
the
kubernetes
dev
group
that
123
is
going
to
get
released
today.
This
also
brings
up
the
conversation
around
that
drops.
119
support
and
119
was
the
last
one
for
the
beta
1..
A
So
now
we're
into
the
fun
territory
of
only
supporting
bug
fixes.
I
was
thinking
one
of
the
things
that
we
need
to
do
probably
to
help
from
a
user's
perspective.
Part
of
the
conversation
we
had
what
a
month
ago
is
that
we
probably
should
put
a
release
date
in
there
for
those
in
that
readme.
So
we've
got
the
the
versions
for
everything
and
then
our
release
date.
Just
so
you
can
see.
I
have
that
conversation
where
it's
like
we've
released.
A
0.5
0.49
and
those
things
I'm
just
only
having
this
six
month
support
conversation,
because
I
think
that's
what
we
originally
talked
about
any
takers
thoughts,
because
I
mean
dropping
119
support
right
now.
If
we
continue
down
with
the
n
minus
three,
that's
gonna
always
raise
some
questions.
D
A
Nope,
that's
fine.
Thank
thank
you
again
for
keeping
us
on
point
tom.
So
it's
not
a
concern
yet,
but
we
do
need
to.
We
do
need
to
add
just
for
tracking
just
need
to
add
a
an
issue
for
someone
to
add
123
to
the
testing
loop
and
drop
119.
A
B
Just
be
just
be
aware
that
to
add
that
to
each
we
test
we
need
first
to
have
an
image
for
kind
and
ben
doesn't
release.
I
mean
I
know
that
he's
been
doing.
Some
runs
to
release
kind
image
versions
together
with
kubernetes
release,
but
I
don't
think
he
does
have
that
yet.
So
we
can.
B
Yet
I'm
just
saying
I
haven't
seen
that
yeah
I
mean
like,
as
we
are
just
hitting
holidays
and
other
stuffs.
I
don't
think
that
the
kind
folks
they
are
going
to
read
these
123
image
just
before
just
yeah,
just
after
sorry,
just
after
the
release
of
of
123
today.
So
it's
it.
It
is
a
good
first
issue,
but
I
would
just
open
that
as
soon
as
we
know
that
there
is
123
in
kind.
Otherwise
we
are
going
to
get
people
just
jumping
in
and
saying
hey.
B
B
Yeah
about
the
dedication
things
I
have
like
two
lines
of
thinking
right
so
as
a
developer
of
a
maintainer
of
ingress
in
china's.
I
think
that
the
best
path
to
us,
what
was
going
to
be
like
just
deprecate
the
legacy
one
but
thinking
into
the
users.
I
think
that
and-
and
I
really
like
what
don
said-
that-
probably
we
should
be
careful
to
say:
hey-
we
don't
support
version,
one
better,
one
as
we
don't
support
anymore,
like
121
or
122
or
whatever
right.
B
B
I
think
that
we
should
be
at
least
a
bit
careful
about
that,
like
maybe
doing
some
research
and
watching
to
see
how
many
of
our
users
are
using,
are
still
using
the
legacy
branch
and
why
they
are
using
that.
So
we
we
you.
I
guess
we
discussed
about
that
in
best
right,
james,
like
making
some
yeah
some
formulary.
A
B
Let's,
let's
talk
with
c
infra,
because
I
think
they
have
that
they
have
that
that
stat,
the
stats
right.
I
know
that
they
they
have.
This
stats
at
least
like
the
second
most
downloaded
docker
image
from
from
from
kubernetes
infra
is
ingressing
jynx.
The
first
one
is
q
proxy
right.
So
probably
they
have
also
the
tag
for
that.
So
we
can.
We
can
ask
them
like
hey.
We
need
some
stats
about
the
tag
right.
A
A
With
that,
do
we
have
anything
else?
I
know
I
think
we
ran
through
most
of
everything.
A
All
right
folks,
unless
there's
anything
else,
I've
got
some
updates
that
I'll
add
to
the
tickets
like
taking
those
notes,
and
I
don't
think,
there's
anything
else.
We
need
to
discuss
from
that
and
if
we're
going
to
cancel
the
21st
so
make
sure
that
everyone
knows
that
as
a
holiday
for
most
of
us,
we'll
get
I'll
get
casey
to
cancel
that
for
us
and
I'll
drop
the
note
in
the
channel,
probably
on
the
day
of
as
well,
even
though
it's
my
day
off
I'll,
just
make
sure
to
drop
that
note.