►
Description
[SIG-Network] Ingress NGINX Bi-Weekly Meeting for 20220118
A
Hello,
everyone:
this
is
the
sig
networking
ingress
engine
xsu
project
meeting.
It
is
january,
18,
2022
and
as
always,
this
is
a
cncf
community
project.
So
that
means
we
adhere
to
their
code
of
conduct,
which
also
means
just
be
awesome
to
each
other.
And
if
there
are
any
issues,
please
go
ahead
and
report
that
to
myself
or
ricardo
go
ahead
and
get
started,
it's
going
to
be
a
light
one.
A
A
This
the
election
id
config
map,
I
saw
that
the
conversation
was
in
slack.
I
think
this
actually
is
an
issue.
I
don't
know
why
it
hasn't
come
up
before
so
when
they
use
helm
to
do
the
install.
We
also
create
a
config
map
for
the
leader
election
id
and
that's
managed
outside
of
helm.
So
when
they
do
the
helm,
delete
it's
not
going
to
it's
not
going
to
remove
that
resource
because
it
doesn't
know
about
it.
A
I
don't
know
if
anyone
else
has
any
other
opinions
around
this
one
I
even
without
having
to
even
without
actually
validating
this.
I
can
see
that
this
actually
is
an
issue.
A
B
No,
I
think
it's
one
point.
A
Yeah,
so
I
was
gonna,
go
I'll,
go
ahead
and
assign
this
one
to
myself
to
at
least
triage
it
and
validate
that
it
is
an
issue
even
without
the
intuition,
so
I'll
go
ahead
and
assign
this
one
to
myself
to
go
ahead
and
look
at
it,
because
that
that
that
one
makes
that
more
makes
sense.
But
as
for
my
code
perspective,
we
will
have
to
take
some
changes.
A
I
read
through
this
one
as
well
before
we
started
why
the
request
path
was
always
defaulting
to
slash.
I
think
it's
because
they're
using
the
prefix
match
the
prefix
is
always
going
to
match
on
slash.
Thus,
why
they're
having
issues-
and
I
think,
long
put
that
out
there,
so
we
don't
have
a
triage
label
for
I
want
to
say
accepted,
because
this
really
isn't
accepted.
I
think
this
is
just
an
issue.
It's
not
really
a
bug.
A
I
think
this
is
more
just
a
support
and
there's
really
no
need
for
a
priority,
which
is
unfortunate
because
it's
not
a.
I
don't
think
this
isn't
too
much
of
an
issue,
so
I'm
going
to
go
ahead
and
assign
this
the
long
since
he
was
asked
answering
the
questions
on
it
and
see
if
he
follows
up
in
slack.
I
didn't
see
any
conversation
around
this
anybody
else.
A
A
A
A
B
A
B
A
A
A
A
Does
the
support
http
2
protocol
nginx,
interfigure
aws,
classic
load
balancer?
I
don't
think
it
supports
it
at
all
anyway.
A
B
A
A
Okay
error:
when
setting
customs
custom
port,
this
will
be
a
fun
one,
especially
and
with
the
valerian
workbook.
That's
the
one.
I
keep
seeing
I've
read
several
ones
reading
through
that
one
as
well:
k3
s,
okay,
indirect
helm,
using
a
different
port
set,
the
controller
port
to
8080
and
the
container
ports
to
8443
inside
the
hound
chart.
A
A
A
A
A
Well,
we'll
wait
to
see
what
he
says
with
that
from
a
response
perspective.
Do
you
mind
if
I
assign
this
one
to
you,
so
we
can
track
it
and
please
quit.
A
And
I
will
add
the
needs
more
information
so
that
it
gets
re
removed
from
the
the
list.
It
needs
information
or
needs
stash
more
information.
I
can
never
remember.
A
A
Add
dachshund
election
id
multiplying
this
controller
guide
looks
like
there's
bank
conversation
on
this
one.
We
found
this
issue
and
solved.
A
A
A
What's
this
one,
multiple,
you
have
exactly
two
insoles
via
helm,
different
controller
classes
dedicated
to
english
class
match
both
in
the
same
name
space.
One
of
them
was
functioning
as
expected:
okay
kind
of
a
global
wheel
election,
the
other
one,
was
handling
ingresses,
but
never
updating
their
status
field.
A
A
I
see
this
one
a
lot,
some
people.
I
think
this
one
was
resolved
with
setting
the
timeout
to
a
minute
towards
the
end.
A
This
person
was
talking
about
the
web
hook,
controller
being
and
they
had
to
update
it.
So
I
asked
them
a
question
on:
did
they
upgrade
and
failed,
because
all
of
the
newer
controllers
are
using
the
newer
image
that
we
maintain?
A
So
I
don't
know
if
somebody
deploys
an
older
one
and
then
they
do
an
upgrade
if
there's
having
issues
with
swapping
out
the
web
hook
from
jet
tech
to
the
one
that
we
maintain,
I'm
waiting
to
hear
back
from
them,
it's
possible
an
issue
we've
also
yeah,
like
you,
said,
you've
seen
the
ca
bundle
issues
before.
A
I
think,
with
the
with
mini
cuban
kind,
we
disable
the
controllers
with
some
of
those
issues
or
the
webhook
validation.
I'm
gonna
go
ahead.
A
A
We'll
see
what
he
says
when
it
gets
back
good
and
pulled
that
one
up
good
first
issue:
we
don't
really
have
any
volunteers
on
here,
looks
like
there's
a
feature
request
for
what
metrics
will
orphaned
ingress
without
endpoints.
A
A
A
A
A
A
And
then
this
one
yeah
this
was
the
one
of
the
open
issues
that
we
talked
about
earlier,
that
I
assigned
to
myself
so
we'll
go
ahead
and
I
don't
think
I
need
to
explain
I'll,
not
accept
it
yet,
but
I'll
definitely
assign
it
to
myself.
A
Okay,
with
that,
I
know
there
were
some
action
items
from
the
last
conversation,
but
ricardo
is
not
here.
Aditha.
Is
there
anything
that
you
wanted
to
talk
about
and
discuss
from
your
the
issues
assigned
to
you
last
week.
B
I
think
I've
taken
care
of
a
few
of
them.
I
may
have
missed
one,
which
I
can
look
back
I'll,
just
pull
them
up.
A
This
one's
fixed,
this
one's
fixed,
didn't
fix
because
it
got
merged
in
here.
Okay,.
A
A
A
I
think
that
was
the
discussion
point
that
we
wanted
to
yeah.
We
wanted
to
push
it
to
the
next
meeting
because
of
the
sidecar
discussion,
and
I
don't
know
where
we'd
be
at
with
that
discussion,
where
his
thought
or
carter's
thoughts
were
on
this
one.
So
I'll
go
I'll
push
this
one
again
to
the
next
meeting.
So
when
we
have
that
discussion
I'll,
add
that
to
the
action
item
so
that
I
can
follow
up
with.
A
Let's
go
ahead
and
look
at
what
was
the
next
one.
B
B
I
was
okay
with
it,
but
then
I
I
don't
know.
A
A
Let's
open
pull
request.
Do
you
want
me
to
sign
it
to
you,
so
it
pops
up
in
your
notifications,
okay,.
A
Okay,
not
doing
that
one
since
ricardo's
not
here
to
talk
about
that.
I
don't
know
and
yamco's
not
here
to
talk
about
stress
test.
We
don't
have
an
open
issue.
A
A
Yeah,
like
I
said,
we
still
did
a
pretty
good
job
of
running
through
using
the
entire
time,
even
though
it
was
just
the
three
of
us,
I'm
impressed.
Are
there
any
other
things
that
we
need
to
discuss?
I
know
that
the
timing,
one,
I
think
it's
poly
as
I
was
talking,
I
think,
that's
the
tool
that
everybody
uses
for
asking
questions
putting
that
out
there.
Maybe
it's
something
else,
I'm
thinking
about
anyway,
anything
else
that
we
need
to
discuss
as
a
group
before
we
sign
off.