►
From YouTube: [SIG-Network] Ingress NGINX meeting for 20230803
Description
[SIG-Network] Ingress NGINX meeting for 20230803
A
Thank
you,
hello.
Everyone,
it's
James
strong!
This
is
the
city,
networking,
Ingress,
nginx
sub-project
meeting
and
today
is
August
3rd,
and
this
is
a
cncf
community
meeting,
which
means
we
have
to
adhere
to
the
cncf
code
of
conduct,
which
means
be
kind
to
each
other.
If
you
have
any
issues,
please
report
those
to
myself
or
the
Sid
Network
leads
and
with
that
we'll
go
ahead
and
get
started
and
as
always,
the
fun
I
don't
have
anything
on
the
board
today,
but
we'll
go
ahead.
Introduce
the
new
members
I
see
someone
new
here
Phillip.
B
A
A
Nothing
on
the
release
perspective
I
was
going
to
try
to
do
it
last
week,
but
I
had
personal
emergency.
Wasn't
able
to
do
any
of
the
release?
Stuff
I
attempted
to
start
doing
more
of
the
release
things.
It
looks
like
there's
some
issues
Ricardo
with
some
of
the
new
images.
I,
don't
know
what
the
issues
are.
I
just
saw
that
it
all
failed.
So
that's
why
I
set
up
the
testing.
It's
not
the
new
kubernetes
versions
that
I
tested,
because
I
bumped,
all
of
them
to
their
latest
releases
from
kind.
A
The
images
are
having
some
issues
so
I
know
that's
stopping
from
getting
a
release
out,
because
I
wanted
to
upgrade
all
of
the
images.
So
we've
got
to
go
through
all
of
those
before
I
can
get
182
out
and
just
from
my
perspective,
we
might
want
to
just
blow
away
the
one
nine
one
190
release
Branch,
because
it's
taking
so
long
to
get
182
out
and
I
don't
want
to
have
to
go
back
and
cherry
pick
all
of
those
because
we
haven't
released
the
cpdp
annotations
of
it.
A
Okay,
and
of
course
it
didn't
reschedule
this
to
9
A.M
Eastern
I
need
to
do
that.
I
think
I
need
to
talk
to
Casey
about
not
Casey,
it's
Sean.
Now
all
right,
Sean
Sean
owns
our
meeting
yeah.
Okay,
well,
I.
Think
most
of
the
open
stuff
was
the
release
conversations
so
we'll
just
go
right
into
triaging.
Some
issues.
A
A
A
A
C
D
D
Maybe
maybe
the
classics
is
not
working
for
them.
They
are
just
using
that
washing
Ingress
without
class
or
watch
anything
or
don't
feel
like
rely
on
the
class
or
maybe
all
of
those
classes.
They
have
the
same.
You
know
the
spec
dot,
Ingress
fqdn
did
they
provided
the
risk?
The
house
is
right
there,
no,
no,
the
the
class,
the
the
object
class.
D
Yeah
ask
them
to
send
the
Ingress
class
specification
and
how
we
deploy
the
Ingress
controller,
because
if
they
are
using
that
model,
where
you
have
like
three
different
Ingress
classes.
But
you
use
that
not
not
by
the
name.
You
remember,
but
the
dot
spec
dot,
something
probably
they
are
just
using
the
same
class.
A
D
A
D
A
This
one
I
read
this
one
the
other
day
and
I
think
this
one
might
be
because
remember
when
we
had
the
ordering
issue
a
while
ago
that
the
certs
have
to
be
in
a
specific
order.
I
think
that's
what
might
be
the
issue
with
this
one.
But
let
me
like
this
bad
line.
This
sounds
like
an
issue
with
their
serve.
D
A
A
D
A
A
C
D
A
C
A
D
A
D
D
D
D
A
C
A
A
D
A
A
C
A
D
A
A
A
A
Okay,
what
was
the
other
one?
There
was
another
memory
issue,
I
think
it
was
a
scale.
One
might
be
this
one
we
might
have
already
talked
about.
It
aren't
sure,
because
I
asked
oh,
no
I'm,
sorry
that
wasn't
slack.
Somebody
in
slack
was
like
yeah
we're
using
one
thousand
to
six
thousand
Ingress
objects
and
we're
having
issues
I'm
like
that's,
that's
a
lot
of
reloads.
A
A
A
A
A
Know
yeah
I
want
to
see
what
your
thoughts
are.
Let's
go.
Look
at
my
my
pull
request,
because
I
think
all
we
did
on
the
runner
was
upgrade
to
126.
the
only
other
option.
The
only
other
things
that
we've
changed
to
is
the
the
Lua
versions,
but
that
got
all
passed
CI
before
already
I'll.
Take
the
container
images
so
I've
got
too
many
I've
got
too
many
PR's
open
that
what's
what's
happening,
it's
failing,
yeah,
it's
failing
on
so
what's
interesting.
A
D
D
A
D
A
D
A
D
D
D
A
D
Yeah
we
need
to
take
a
so
you
need
to
run
it
locally
only
that
test
and
see
if
it's
like
crashing
back
you're,
not
trying
to
pull
something
that
doesn't
exist
before
okay,
really
running
because
apparently
what's
happening.
It's
fading
on
at
least
to
me
on
on
taking
this.
This
quick
look
yeah,
it's
trading
on
on
a
really
fast
moment,
probably
on
the
pre-creation
right.
D
A
I'll,
do
that
so,
once
I
can
get
once
I
can
figure
out
what
why
those
are
failing.
I
can
get
182
out
by
the
time
I
get
182
out
go,
127
is
going
to
be
released.
It
looks
like
there's
already
a
release
candidate,
so
we'll
have
to
go
back
to
this
again.
I
really
think
we
need
to
pause
and
take
a
time
and
just
make
it
so
that
it's
only
two
PR's,
maybe
even
just
three
I-
think
it's
still
going
to
be
three
because
we
have
to
make
the
change
It's
gotta
have
to
rebuild.
A
D
Yeah
yeah
yeah
yeah
yeah.
We
we
can.
We
can
take
a
look
at
those
things
later
so
just
to
let
you
know
my
plans
now
they
are
just
to
return
working
on
the
control
plane.
Data
plane,
seeing
really.
Okay,
slow
and
I
have
other
two
teams
in
my
pocket,
which
are
one
it's
GSS
office
through
fixing
a
lot
of
people.
D
Ask
that
on
that
streaming
on
on
other
places,
so
doing
ninja
next
to
the
SSL
pass
through
and
remove
that
proxy
from
the
controller
gotcha,
yeah
and
yeah
and
looking
into
njs
it's
my
it's
becoming
my
top
priority
to
stop
using
open
resty
and
the
migration
to
njs,
at
least
for
the
load
balancers
to
the
certificates.
I,
don't
think
it's
going
to
be
easy,
but
it's
doable
I
could
test.
It
seems
pretty
straightforward
to
do.