►
From YouTube: [SIG-Network] Ingress NGINX meeting for 20230928
Description
[SIG-Network] Ingress NGINX meeting for 20230928
A
Hello,
everyone-
this
is
James
strong.
This
is
the
sub
project
for
the
Ingress
nginx
project.
This
means
is
a
cncf
project
and
we
adhere
to
the
code
of
conduct,
which
means
be
awesome
to
each
other.
There
are
any
issues,
please
report,
those
to
myself
or
the
Sig
networking
team
lead
and
with
that
we're
going
to
go
ahead
and
get
started
and
jump
into
the
spawn.
A
I've
got
a
couple
new
folks,
mahab
and
Victor.
Do
you
want
to
introduce
yourselves.
B
Hello,
my
name
is
mohab
I'm
from
Egypt
yeah
I
didn't
contribute
much
to
cover
this,
but
I'm
looking
forward
to
so
I'm.
Just
you
know
trying
to
experience
things.
C
Yeah
I've
been
participating
on
some
security
meeting
first
time
joining
this
meeting.
What's
going
on
security,
wise.
B
A
Least,
we're
trying
to
I'm
gonna
skip
the
triage
since
I
know
Ricardo
you're
on
short
time
and
we're
going
to
go
ahead
and
talk
about
the
fun
that
we've
been
having
for
the
past
couple
of
weeks.
So
with
V1
with
v190,
we
talked
about
it
for
actually
I
went
back
and
I
looked.
July
was
the
first
time
we
started
talking
about
releasing
what
we
did
in
190,
so
I
did
not
misspeak.
A
We
put
it
in
the
release,
notes,
and
you
know
we
we
try
to
do
our
best
to
make
sure
that
everyone
is
aware
of
the
changes
that
we're
making
we'll
take
that
feedback
into
consideration
with
this
fun
little
doc
that
I'm
going
to
write
about
how
we
do
releases,
what
we
say
what
we
mean
when
we
say
some
things
so
making
sure
that
we're
a
little
bit
more
crisp
and
clear
on
that
communication.
A
I,
don't
have
anything
in
here
just
yet,
but
we
just
want
to
I
just
want
to
make
sure
that
when
we
say
we're
gonna
do
when
we
say
we're
going
to
follow
simvar
what
it
means
for
us.
We
know
what
the
letter
of
the
law
says,
but
what
the
spirit,
but
what
the
spirit
means
and
what
we
actually
do
in
practice.
So
I
want
to
make
sure
that
that's
crystal
clear
when
we
do
a
patch
minor
in
major
version
changes
when
we
and
how
we
go
through
breaking
changes.
A
Things
like
that,
so
I
know
that
one
I
know
did
break
some
folks.
We
have
a
lot
of
comments
in
there,
but
yeah
anything
that
you
wanted
to
add.
Ricardo.
D
We
are
kind
enough
in
the
middle
of
a
lot
of
things
ongoing
and-
and
we
at
least
on
my
side,
we've
been
trying
to
make
our
best
to
not
break
folks,
but
I.
Think
that's
a
good
call
out
that
you
me
and
all
of
the
other
maintainers.
We
are
volunteers,
and
usually
we
do
that
in
our
spare
time
and
like
myself,
I
do
that
on
Sundays
and
we
are
open
to
contributions.
D
But
we
need
people
to
understand
that
we
are
not
doing
that
because
we
want
to
break
people
closer,
but
that's
because
we
are
actually
targeting
to
have
a
more
secure
environment,
and
sometimes
we
try
yeah.
Even
if
we
try
hard
to
to
make
make
everybody
aware
that
some
things
are
breaking
or
changing
they
don't
they
they
got
missed.
D
So
even
if
someone
want
to
be
our
communication,
release
manager
or
whatever
or
help
us
on
the
comms,
we
are
open
to
get
people
doing
a
better
job
that
we've
been
doing
on
the
communication
side
as
well.
A
Yeah
I
think
the
some
of
the
feedback
that
I've
taken
is
that,
like
I
said
when
we
put
out
a
breaking
change,
I
want
to
follow
the
cycle
of
putting
out
a
warn
and
then
putting
out
a
Beta
release,
letting
that
sit,
and
then
we
do
the
actual
change
that
at
least
bakes
for
two
months
and
then
also
the
the
resolution
path
for
when
the
braking
change
does
happen.
What
folks
need
to
do
so.
That
I
mean
we.
A
So
we
have
lots
of
communication
mediums
to
put
those
out
and
we
just
need
to
make
sure
that
as
maintainers
that
we're
better
at
making
sure
that
it
is
known
in
her,
but
we
can't
stop
all
of
them
and
these
things
will
happen
and
we'll
try
to
learn
from
them.
So
that's
that's
I,
think
that's
what
I
want
to
say
about
one
I
know:
if
there's
anybody
on
the
call
that
would
like
to
have
the
conversation
about
that.
That
now
would
be
a
good
time
to
have
that.
A
Okay,
let's
talk
about
some
more
fun
in
our
releases.
I
started
a
doc
a
while
back
ago.
So
what
I
want
to
do
is
with
what
we've
talked
about
with
the
190
things
that
we've
learned
for
2-0.
There
was
a
lot
of
more
things
that
are
going
to
break
and
change
in
2o.
That
I,
don't
think
we've
really
discussed
and
talked
about.
Can
you
guys
see
my
screen
yeah.
C
A
We
have
these
top
four
things
that
we
were
going
to
look
at,
so
one
of
them
against
the
path
validation.
That's
another
cve
remediation
issue,
we're
going
to
flip
that
change
the
true
the
control,
plane,
data
plane,
split
the
architecture
change
for
that,
so
that
will
help
us
put
in
the
planning
for
2-0,
removing
Jaeger
and
all
of
the
others
and
migrating
folks
to
use
the
open.
A
Telemetry
module
actually
force
them
to
use
that,
so
that
will
be
one
of
the
biggest
changes,
I
think
and
then
looking
into
removing
or
replacing
mod
security.
Because
of
the
lack
of
support,
that's
coming
from
its
main
support
or
continuing
to
see
how
that
support
is
going
to
be
picked
up
from
the
community.
So
those
are
the
four
things
we've
already
removed.
Aj
ajp
support
that
was
done
in
190,
or
was
that
done
in
182,
I
can't
remember.
I
saw
that
it
was
when.
D
D
A
That's
the
four
things
that
we're
looking
right
now
for
2-0
and
again
I
know:
all
of
those
are
still
going
to
content
need
work.
I
mean
these
three
things
need
work
great,
we
don't
know,
what's
going
to
replace
mod
security,
if
anything's
going
to
replace
it,
removing
it's
going
to
be
a
little
difficult
because
it
is
built
into
our
images.
A
I,
don't
even
know
what
the
remediation
is
going
to
be
for
Diego,
so
again
putting
the
plan
together
for
all
four
of
these
things.
I
know
we
still
have
some
things
to
work
out
for
cpdp,
so
I
didn't
know.
This
was
just
a
collecting
ground
for
what
we
wanted
to
look
at
for
v2.
A
That's
right,
you
did
tell
me
about
that.
One,
so
I
do
want
to
make
sure
that
we're
tracking
these
I
don't
have
open
issues
with
this
and
I.
Don't
know
if
there's
any
other
changes
that
we
were
going
to
try
to
make
with
2o.
So
again,
when
we
talk
about
the
release
with
December,
we
very
rarely
will
change
the
major
version.
I
think
we
only
changed
it
to
1-0
because
of
the
release
for
going
from
V
beta
1
for
the
Ingress
spec
to
V1.
A
That's
why
we
bumped
to
1-0
to
signify
that
major
change,
so
a
lot
of
our
changes
will
be
in
minor
releases,
it's
very
similar
to
the
kubernetes
model,
where
they'll
put
out
things
in
Alpha
Beta
and
then
put
them
into
GA.
I,
don't
know!
If
we
need
to
go
to
that
one.
We
do
have
betas
releases
that
we
do.
We
did
we've
done
a
couple
of
those.
So
again,
I'm
thinking
you
know,
put
a
one
in
a
patch
put
out
a
Beta
release
and
then
minor
patch.
A
B
A
So
lay
out
the
plan
for
changes
and
then
try
to
work
through
those
with
the
the
201.
Surprisingly,
no
one
yelled
about
the
curl
change,
but
I
did
notice
that
there
it
is
still
in
the
image
and
I'm
guessing
it's,
because
it's
in
the
nginx
based
image,
because
we
use
it
for
the
build
servers
to
build
and
download
all
of
the
Lua
things
so
I
think
that's
one
of
the
things
that
we
need
to
look
at
is
that
the
curls
in
the
base,
image
and
I,
don't
think
we
strip
it
out.
A
A
We
I
think
the
pr
was
to
remove
it
from
the
final
image,
but
I
think
it's
still
in
the
nginx
base
image
layer.
So
I
don't
know
because
removing
it
from
the
that
the
Ingress
image
doesn't
remove
it
from
the
base.
So
it's
still
there
in
a
layer
and
I
think
scanners
are
still
going
to
pick
it
up
so
I,
don't
know
what
we
would
need
to
do
to
either
just
squash
or
just
remove
from
move
away
from
curl
altogether.
If
we're
trying
to
remove
it
from
our
build
system.
D
D
Think
that
other
than
that
I
I
keep
seeing
so
I
would
like
to
see
at
least
the
other.
Oh,
we
have
one
for
2.0,
which
is
in
Gen
X
version.
I,
don't
know
if
you
added
that
to
125
video.
A
No,
we
can
now,
it's
I
think
we
can
do
that
with
that,
doesn't
have
to
be
a
2-0
release.
Yeah
I.
D
Mean
yeah
the
tool
that
I
would
like
to
it's
to
get
njs
instead
of
open
Rusty,
at
least
on
the
majority
of
places
that
we
can.
A
Yeah
I
was
gonna,
say
this
one.
The
cpdp
is
going
to
give
you
because
I
know
that
we
still
have
the
communication
between
the
nginx
Pod
and
the
data
playing
pod.
I
know
there
were
still
issues
with
that.
So
I
didn't
want
to
add
that
add
the
njs
stuff
on
top
of
it,
because
I
know
that's
going
to
take
a
while,
because
we
have
a
lot
of
I
know.
A
Oh
a
Scandinavian
friend
like
Brandon,
he
was
mapping
out
Lua
functionality
so
that
we
could
get
the
njs
functionality
and
work
with
Dylan
and
the
nginx
team
so
that
we
can
make
sure
that
we
have
that
functionality
available
for
njs.
So
I
feel
like
that
one's
going
to
be
a
lot
longer
putt
than
the
other
ones
that
we
have
on
there.
So
I
don't
know
if
we
wanted
to
wait
a
whole
possible
another
year
for
2-0.
So.
C
A
A
lot
of
version
discussions
and
not
really
getting
into
the
issues.
Unfortunately,
this
is
the
regression
that
you
were
talking
about.
Was
this?
No,
this
isn't
the
regression
I'm
thinking
about.
Is
this
the
the
capital
yeah
the
case
issue?
This
is
the
case
issue.
One.
D
D
Is
okay?
It's
on
my
my
list.
I
need
to
start
out
something
yeah
I
think
that
I
am
assign
it
to
this
one.
D
A
D
So
this
this
one,
it's
it's
on
on
my
list
and
and
as
I've
said
I
have
something
you
know
more
important
to
do
for
the
next
two
or
three
days,
but
other
than
that.
I
want
to
get
this
one
fixed
I,
don't
want
21.
one
one,
nine
one.
C
A
Yeah
but
I
hope
we
can
get
that
one,
so
yeah
get
the
Cur
get
Curl
out
for
191
bump
to
one
three
eighteen,
three,
and
also
this
regression.
Those
are
the
top
three
things.
I
think
that
we'll
need
to
I
said
110,
but
we
need
to
start
tracking
that
one
so
I
need
to
open
up
an
issue
for
that,
so
we
can
track
it.
A
That
was
the
other
thing
that
we
could
probably
add
is
about
deprecations.
We
just
thought
opening
issues
open
an
issue
for
the
discussion,
and
then
we
just
tracked
that
issue
there
for
deprecations.
So
maybe
we
can
do
that
as
well.
A
I
think
that
was
the
majority
of
things
that
we
needed
to
talk
about.
I,
don't
know
if
we'll
get
to
the
I,
don't
think
this
will
get
there
for
110,
because
if
we
keep
our
well,
we
can
keep
it
for
110,
because
we
can
just
keep
our
Cadence
and
just
keep
going
one.
Nine
one,
one,
nine
two
three:
until
we
get
to
this
one
I,
don't
know
if
there's
any
other,
this
should
be
doable
by
110..
If
we
have
someone
to
work
on
it,
would
you
agree
Ricardo.
D
Yeah
I
think
that
this
one
specifically,
we
were
waiting
for
some
update
from
datadog
folks
and
by
the
way,
during
the
middle
approach
of
data
dog
and
and
the
Upstream
open
Telemetry
model
in
Gen
X
also
released
their
own
open
Telemetry
model.
So
we
just
need
to
discuss
which
one
we
are
going
to
adopt
and
tell
folks
like
hey.
We
need
to
move
forward
with
this
one
right,
but
there
is
also
a
model
from
from
an
official
one
for
engine
X.
A
D
Maybe
we
should
get
this
subject
with
SN
again,
as
he's
our
open
trade
in
open,
Telemetry,
Guru
developer
and
she
shared
his
feeling
about
using
a
SN.
D
No
no
and
check
if
he
he's
up
to
maybe
what's
his
Feeling
Again
on
using
the
enjoy
next
one.
Okay,.
A
A
Are
there
any
other
issues
top
of
Mind
Ricardo
that
you
know
about
I've
looked
at
the
list,
there
was
one
in
here,
and
so
the
question
we
have
is
like
I
haven't
looked
at
this
one
thoroughly,
but
like
those
crashes
in
164.-
and
there
was
another
issue
with
I
can't
remember-
should
have
wrote
it
down.
There
was
another
one
where
it's
crashing,
but
I
think
it's
because
of
you
limits,
but
I
need
to
go.
Look.
D
C
A
D
It's
the
proxy,
the
TLs
pass
through
the
new
approach
that
I'm
working
as
well
I.
Remember
that
we
have
a
bunch
of
issues
on
that,
but
yeah.
A
Yeah
I
do
remember
that
one.
My
my
concern
with
this
one
is
like
we're
now
on
to
190
and
we're.
If
we're
doing
n
minus
two
technically,
we
can't
support
164..
So
I
was
gonna.
Ask
one
to
get
asked
us
to
provide
more
information
and
to
test
to
see
if
they
have
this
issue
in
190.
A
A
D
I,
no
sorry
James
go
far.
A
I
can't
find
it,
but
I
will
find
it
and
I'll
drop
it
in
the
Ingress
Dev
chat,
but
when
I
finish
up
and
ride
up
the
dock
for
the
release
versions,
so
folks
can
be
aware
of
how
we're
moving
things
forward
or
how
the
release
cycle
works.
A
A
Okay,
we'll
record
with
that
I
guess:
I
can
let
you
go
and
let
everyone
else
go.
Victor
mohab!
If
you
want
to
join,
there,
is
a
Ingress
Dev
Channel,
where
we
talk
about
a
lot
of
this
stuff
asynchronously
in
our
in
our
Channel
and
where
I'll
probably
be
dropping
more
information
as
we
work
through
some
of
this
stuff.
A
Yeah
thanks
Ricardo
for
your
limited
time,
and
we
will
go
ahead
and
one
last
update
just
for
folks
is
that
we're
going
to
move
this
I
think
we
decided
to
move
it
to
9am
Eastern,
because
Ricardo
has
a
lot
of
meetings
that
get
bumped
up
into
this
one,
his
team's
scrum
and
things
like
that.
So
we're
gonna,
get
the
Sig
networking
lead
to
move
this
for
us
so
that
we
can
get
him
to
join
and
have
his
full
attention
because
he's
always
triple
booked
for
this
meeting.
All
right
thanks.