►
From YouTube: [SIG-Network] Ingress NGINX meeting for 20230720
Description
[SIG-Network] Ingress NGINX meeting for 20230720
A
Hello,
everyone,
my
name,
is
James
strong.
This
is
the
Sig
networking,
Ingress
nginx
sub
project
for
Stig
networking,
which
means
the
cncf
project,
and
we
have
to
adhere
to
the
cncf
code
of
conduct,
which
means
be
awesome
to
each
other.
If
you
have
any
issues,
please
report
those
to
myself
or
the
sign
networking
lead
with
that
we'll
go
ahead
and
get
started.
We
have
a
long
time
contributor
but
been
missing
the
meeting
so
Gentile.
Thank
you
for
joining
us
at
11
PM.
A
Yes,
thank
you
for
your
time.
Very,
very
much
appreciate
that
no
new
members
today,
so
it's
just
going
to
be
us
talking
about
all
of
the
releases,
so
I've
got
some
ideas
on
I
want
to
discuss
all
the
releases,
a
little
bits
and
triaging
some
of
the
action
items
we
can
review
I,
don't
think,
there's
any
action
items
to
review,
but
we
can
go
ahead
and
go.
Look
at
the
last
last
two
meetings.
A
Don't
know
if
we
actually
just
discussed
that
one
further
disabling
Snippets,
so
it
looks
like
we
just
got
more
release
stuff
to
discuss.
I,
don't
know
where
we're
at
the
mod
set
issue.
I
know:
we've
got
to
fix
it
for
Mark,
but
I
think
he
was
going
to
put
in
the
fix
and
attempt
to
do
the
pr
okay,
so
that's
three
days
ago,
so
probably
won't
get
it
into
182,
which
is
fine.
A
I'll
follow
back
with
up
with
him
on
Slack,
but
we
did
figure
out
what
that
issue
was
that
he
did
verify
that
that
worked.
So
that's
good
I'm
surprised.
No
one
else
has
ran
into
that
one:
lots
of
deprecations,
it's
fine,
mod
SEC
I
did
not
do
a
write-up
for
the
breaking
I
I
created
the
dock,
but
then
I
also
put
it
back
up
here.
So
I
think
Ricardo
also
have
that.
A
Not
sick
Dylan's,
not
here,
so
we
can't
talk
about
anything
that
perspective
Ricardo's
been
taking
me
a
lot
about.
He's
he's
really
liking
the
JavaScript
library,
so
that'll
be
an
interesting
one
and
we're
we're
also
talking
about
refactoring
cpdp,
the
control
plane,
data
plane
spit
split
to
be
a
little
easier
instead
of
using
grpc
I,
don't
know
if
you
guys
have
been
following
the
conversation
in
slack
about
using
how
to
get
those
to
communicate
with
each
other
they're
still
working
through
that
as
well.
So
nothing
new
on
the
action
items.
A
Let's
go
ahead
and
go
look
at
tree
housing.
Do
we
have
any
issues
that
we
want
to
talk
about
before
I
just
jump
into
the
current
ones?
I've
got
a
couple
here
that
I've
got
pinged
on
and
slack
I.
Think
most
of
these
are
the
helm
chart
ones,
but
any
issues
that
we
actually
need
to.
We
want
to
discuss
before
I
just
jump
into
the
current
issues.
C
I
do
have
that
bug
fix
that
I
worked
on
for
the
Lua
back-end,
the
default
back-end
and
the
canary
splits,
where
the
canary
was
ignoring
the
default
back
end.
When
returning
error
codes,
the
Jintao
said
he
had
some
concerns
about
because
I'm
setting
a
new
variable
specifying
that
it's
a
default
that
the
default
backend
has
been
set
when
changing
the
app
stream
stuff.
So
I
mean
it's
not
urgent,
but
I
know
there
is
someone
waiting
on
that
that
PR?
A
D
A
Well,
with
that,
let's
go
ahead
and
go
into
some
of
the
issues:
I've
not
read
any
of
these
new
ones.
So,
let's,
let's
read
together
and
try
to
keep
us
on
time.
It's
11
11.
A
A
A
B
C
Yeah
I
think
I
think
we
just
need
to
ask
for
more
awesome
to
fill
in
the
template
of
the
issue
with
more
information
like
cluster
set
up.
What
are
they,
what
service
type
they're,
using
Etc
right.
D
B
C
Yeah
some.
E
People
do
and
I
I,
I,
I
I
think
always
should
need
the
reproduce.
The
step
yeah.
A
C
B
D
D
B
E
The
eye
to
the
indoor
this
this
corruption,
she
said,
reproduce
this
issue
on
other
cluster.
A
Anybody
know
what
backwog
size
is:
I,
don't
know
all
of
the
internet
stuff.
C
A
C
We
should
we
should
totally
create
a
bot
that
just
posts
Long's
message
whenever
yeah
is
wrong.
B
B
A
D
A
C
Must
have
updated
the
core
DNS
configs
right
with
something.
A
What
cloud
are
they
running
is
on
on-prem
but
they're
using
the
cloud
deployment.
E
E
Tonight,
I.
E
If
I
remember
correctly
the
deal
as
resolve,
the
account
can
accept
a
lane
to
configuration
items.
B
A
A
C
Well,
those
are
all
external
outside
of
the
cluster.
The
cluster
would
also
have
a
DNS,
wouldn't
it.
B
A
D
A
B
D
B
This
is.
C
A
A
So,
okay
wanted
to
I
need
to
I
think
we
need
to
get
the
because
I
know,
there's
a
vulnerability
out
there.
That
was
fixed
and
golang
126.,
so
I
think
that's
one
of
the
first
things
we
need
to
do
is
we
need
to
get
everything
updated
for
126.
A
and
then
we
can
release
182.
I,
don't
know
if
there
was
anything
else.
I
think
I
am
pretty
sure.
I
just
Cherry
Picked,
a
a
change
for
one
I
think
it
was
one
of
yours,
Gentile
I
need
to
go.
Look
a
box
should
have
yelled
at
me,
which
one
was
that
I
think
it
was
this
one:
the
open,
Rusty,
stuff,
yeah,
I,
Cherry
Picked,
that
one.
A
Okay,
well,
that's
easy
enough!
I,
don't
know
we'll
get
that
one
built,
that's
gonna
build!
Do
we
wanna
because
that's
going
to
rebuild
engine
X
is
fine.
That'll,
give
us
a
new
nginx
base
and
then
we
can
do
the
126
upgrade,
because
that's
the
testing
image
and
the
CI
and
that's
another
PR
run
through
with
case
that
I
own
or
another
promotion.
So
that's
two
promotions,
three
to
get
us
to
128
too
or
182.
A
A
We
can
we'll
ask
recorder:
it's
got
his
name
on
it.
So
we'll
ask
him
if
and
slack
okay
I've
already
created
the
one,
nine
oh
release,
because
I
don't
think
we're
gonna
put
anything
more
in
one.
Eight.
D
A
A
So
we
probably
should
just
cancel
this
because
we
don't
want
to
accept
that
I
know
that's
a
knit,
but
we
want
all
of
our
CIA
to
pass
so
we're
doing
annotations
right.
So
these
specialist
fix
he'll
fix
the
go
format
and
then
we
can
get
that
one
into
one
nine.
A
A
Know
because
we
want
this
to
be
the
ajp
support.
That
was
what
were
you
thinking
2o,
or
are
we
thinking
110.?
So
this
is
this
needs
to
be
thought
about.
I'll
go
through
and
I'll
do
all
of
the
updates
for
the
docker,
all
of
the
depend
about
merges
I'll
go
through
and
just
get
all
of
those
in
the
182.
A
A
B
A
Have
an
issue
for
well
I:
don't
think
we
have
an
open
issue
tracking
the
all
of
the
open
tracing,
Zipkin
and
Jaeger
stuff.
Do
we.
A
A
Okay,
there
was
General,
there
was
one
that
we
wanted.
Brendan
wanted
to
discuss
with
you,
the
it
the
issues
with
Canary
overrides
back
in
the
vote.
I'll.
Let
you
guys
talk
that
out.
B
E
E
For
for
the,
for
the
the
main
points
is
the
the
I
I,
don't
I
so
I
don't
think
this.
This
PR's
implementation,
maybe
you
will-
will
have
some
impact
on
others
of
other
functions,
so
I
I
I
need
some
time
to
check
it.
Yeah.
A
All
right
we'll
wait
to
hear
from
you
on
that.
One
I
think
I
had
a
couple,
others
that
I
wanted
to
look
at,
but
I
think
we
wanted
to
get.
These
are
like
Helm
chart
fixes.
D
A
Like
just
getting
the
the
internal
up
to
speed
with
where
the
external
that.
A
We're
looking
at
9700
pull
requests.
I
never
saw.
A
So
we
just
want
to
look
at
this
one,
a
little
bit
more
I.
Don't
think
we'll
get
this
in
them
in
this
week
and
I.
Don't
think
we
have
a
test
for
internal,
should
we
have
a
test
for
internal
load
balances.
E
I
I
think
our
our
test
case
don't
cover
this
one,
so
see
this
one
needs
to
test
by
yourself,
so
you
can
assign
this
to
me.
Let
me
let
me
check
in
my
cluster.
A
Okay,
would
it
be
would
be
too
much
for
us
to
ask
them
to
add
the
CI
test
for
an
internal,
because
I
don't
think
we
have
one
at
all
in.
D
E
Our
or
to
test.
E
Interchange,
the
values,
don't
change,
the
values
configuration
the.
D
C
So,
for
instance,
from
what
I
understand
is
this
will
remove
all
external
Services.
If
you
run
an
update
on
a
on
an
old
running
cluster
like.
A
A
Yeah
I
think
it
is
too
I.
Think
that's
the
other
thing
so
I
have
to
because
I
know
we
do
it
in
some
places.
A
D
A
A
D
A
Man
I'll
sign
this
out
to
you
and
tell
them
to
test
them.
B
A
A
B
A
Important
piece
we
need
to
get
a
little
bit,
we
need
to
figure
out
and
I
need
to
write
up
an
issue
like
our
testing
like
on
docs
changes,
we
shouldn't
be
running
CI
on
Helm.
Chart
changes,
maybe
only
run
the
helm
chart
tests
instead
of,
like
the
full
CI.
There's
a
there's,
a
lot
of
like
Nuance,
where
we
can
just
save
some
time
on
some
PRS.
C
Maybe
maybe
because
long
I
I
think
I
saw
long
discussing
on
it
somewhere.
So
maybe
we
just
pin
him
and
ask
him
he's,
got
context
on
that
one,
but
yeah
the
home
chart
thing
it's!
It's
just
a
regex
thing
that
you
add
to
the
GitHub
action
right.
A
Probably
do
it
on
time:
52.,
okay,
so
there's
some
things
to
get
through
once
they
open,
Rusty
stuff
finishes.
Building,
let's
see
if
it
actually
started.
Building
all
right,
we'll
just
follow
that
one.
Oh
something
broke.
A
A
You
know
all
right
folks,
oh
gento,
it
was
great
seeing
you
thanks
for
joining
and
we'll
try
to
get
this
moved
up
a
little
bit
sooner.
So
I'll
I'll
discuss
it
with
with
the
things
with
the
stuff
that
person
Ricardo
and
then
I'll
get
sick.
Note
looking
to
move
it
up.
If
he's
good
with
it.