►
Description
[SIG-Network] Ingress NGINX Bi-Weekly Meeting for 20221110
A
Hello:
everyone,
my
name,
is
James
strong.
This
is
the
Sig
networking
subproject
Ingress
nginx,
which
means
that
it
is
subjected
to
the
cncf
code
of
conduct,
which
essentially
means
be
kind
to
each
other.
If
you
have
any
issues
with
anyone
on
the
call,
please
let
me-
or
these
said
networking
leads
know
with
that-
we'll
go
ahead
and
get
started
today.
A
And
Gentile
can't
join
so
might
be
a
short
one
unless
we
all
have
some
things.
I
don't
see
any
new
folks
on
the
call,
so
we
can
go
ahead
and
Skip
to
that
one
and
I
know
Dylan.
You
said
you
had
an
update.
We
can
go
through
that
and
I
know
Sean
we
had
some
I.
Have
some
discussions
I
wanted
to
see
where
we're
at
with
open
Telemetry.
B
A
Was
a
lot
of
tickets
and
a
lot
of
a
lot
of
things
I
just
you
know,
maybe
you
can
help
help
me
through
that,
and
we
can
get
that
one
probably
into
the
next
release
and
hopefully
the
release
after
that
drop,
Jaeger
and
open
tracing
all
right.
That
was
a
lot
of
me
talking
Dylan.
You
want
to
go
ahead
and
give
your
update
on
the
nginx
agent
yeah.
C
Sure
thing
so
we
we
finally
have
a
date
for
a
date
of
sorts,
so
we're
targeting
end
of
November
we're
expecting
a
bit
of
fanfare,
so
they'll
be
I,
think
they
they
were
talking
about
a
blog
post,
we'll
we'll
turn
the
the
repo
from
private
to
public
and
I.
Think
they'll
be
like
a
small
marketing
push
from
us
as
well.
So
those
are
things
that
you
guys
can
look
for
I.
C
Think
most
people
are
just
going
to
be
interested
in
the
repo
once
it's
once
it's
once
it's
open
to
the
public.
A
Yeah
that'll
be
it'll,
be
exciting
and
then
we'll
we
can
see
what
it
helps,
what
problems
it
helps
to
solve
and
hopefully
deprecate
some
features
that
does
bring
up
another
point
that
I
was
thinking
about.
A
Sorry
I've
got
a
lot
of
things
on
my
mind
when
it
comes
to
Ingress
engine
X
and
that
one's
mod
security,
so
we
might
wanna
pull
up
that
one
and
see
what
you
all
are
thinking
about,
how
to
fix
that
one,
but
anyway,
I'll
add
that
as
the
open
topic
Sean
do
you
wanna
am
I
pronouncing
that
correctly
too.
By
the
way,
I'm
sorry
I
I
want
to
make
sure
I'm
pronouncing
that
correctly.
It's
it's.
A
Right
well,
I
apologize
and
thank
you
for
correcting
me.
So
we
did
just
do
the
151
release
like
I
was
talking
about
before
we
started
recording.
Do
you
want
to
give
us?
You
want
to
show
your
screen
and
do
a
walk
through
I
saw
there's
a
documentation,
PR
and
I
know
that
there's
an
issue
tracking
with
a
bunch
of
different
things
and
unfortunately,
like
I
said
I
I'm
I've
been
I'm
struggling
a
little
bit
with
that
one.
A
So
let's
do
you
do
you
have
the
have
that
ready
to
to
do
a
little
bit
of
a
walk
through.
A
B
A
D
And
there's
one
more
change:
that's
it's
not
there!
Yet
we
had
this
problem
with
with
grpc
files
and
so
files,
and
that
we
have
to
copy
I.
I
have
solved
it,
but
I
haven't
made
the
pr
yet
so
the
open,
Telemetry
sidecar
image
will
be
smaller.
D
A
D
A
A
A
Anything
did
you
I
think
the
other
thing
that
we've
also
been
pushing
for
is
end-to-end
pests.
I
just
wanted
to
make
sure
that
we've
got
some
of
we've
got
those
in
there
as
well.
There's.
A
We
do
yeah,
okay,
well,
that's
a
change
in
ch
root,
but
okay,
open
Telemetry
and
then
awesome.
That's
yeah.
It's
always
looking
for
okay.
So
if
they
ended
in
tests
run,
then
we
should
be
able
to
get
this
into
the
next.
The
next
one
I
have
a
question.
This
is
just
because
of
my
own
ignorance.
A
A
A
Okay,
well,
I,
think
I
think
our
goal
was
to
remove
the
the
dependency
because
of
the
lot
of
things
that
we
build
in
the
nginx
module
with
open
tracing
and
Jaeger.
If
we
can
remove
those
dependencies,
so
I
was
thinking,
I
guess,
there's
a
migration
path
that
we'd
have
to
put
together.
D
Yeah
and
one
more
news
here
and
Jacob
collector
also
accepts
the
protocol
I
use
here.
Okay,
so
Hotel
collector
is
not
really
mandatory.
D
B
D
A
Okay,
awesome
well,
I'll,
go
ahead
and
review
it
to
you,
then,
since
I
know,
Ricardo
hasn't
had
a
chance
to
do
that
and
I
haven't
had
a
chance
to
test
this
anyway.
So
thank
you.
Thank
you
for
that
and
then
I'll
just
I'll
I'll
map
it
out
and
probably
put
it
in
an
issue.
Probably
add
it
to
your
issue
on
what
we're
going
to
do
and
how
we're
going
to
release
this
awesome.
Oh
thank.
D
D
Thanks
one
question:
I,
don't
know
how
the
bills
are
the.
Are
they
multi-arc
and
do
you
support
almost
processors,
also.
A
Yeah
I
do
believe
it
does.
The
way
we
can
tell
is
by
going
and
looking
at
I
think
it's
in
the
make
file
when
we
do
a
release.
So
if
you
go
look
at
the
make
release,
Target
specifies
which
ones
we
do.
A
A
Okay,
awesome
thanks
for
all
those
out
before
we
go
into
the
triaging.
Let's
go
ahead
and
I
know
this
one.
A
B
A
A
This
is
why
I
closed
out
either
I'll
find
that
one
I'll
go
ahead
and
go
close
this
one
out,
so
we
don't
have
to
keep
watching
me
stumble
through.
A
All
right
so
I'll
go
ahead
and
review
that
one
we've
already
talked
about
the
control
plane.
Discussion,
I
need
to
I,
haven't
even
looked
at
this
one
I
haven't
followed
up
with
this
one
either
yet
I
know
there's
a
couple.
We
got
a
couple,
others
from
the
stability
stuff
about
hdb
Ben
is
one
the
code.
The
go
vulnerability,
Checker
is
one
the
default
back.
A
End
update
is
another,
so
I
need
to
get
those
two
in
here
and
then,
as
far
as
the
release
process
is
concerned,
I
just
finished
the
151
release
and
the
Sig
release,
notes
tool,
isn't
there's
a
discrepancy
between
the
Sig
release,
notes,
tool
and
whatever
release
notes.
Github
is
generating
and
I
haven't
been
able
to
figure
out
what
the
difference
is
between
those
two
are
so
release
notes
are
going
to
have
to
go
back
to
the
drawing
board.
I
think
we
might
have
to
write
something
from
scratch.
A
A
That
we
can't
use
any
of
the
tools
out
of
the
box.
I
think
we
might
need
just
to
refactor
the
release
process
anyway,
just
because
I
think
there's
about
14
or
15
different
files.
We
touched
from
a
release
perspective
and
the
scattered
across
batch
Scripts,
and
it
just
needs
cleaned
up
and
just
overhold
from
the
ground
up.
A
That's
what
that
on
the
stabilization
projects,
that's
and
then,
like
I,
said
it's
going
to
be
a
short
one.
Today,
I,
don't
think
we
want
to
sit
and
triage
your
shoes.
I
was
probably
going
to
do
those
offline
for
the
next
40
minutes
unless
anyone
had
any
issues
that
they
wanted
to
discuss
and
think
so
I
didn't
think
so.
A
I
want
to
sit
on
a
recording,
for
you
know,
40
minutes.
Anyone
disagree.
Disagree
with
that
assessment.
A
It
is
I
mean
I'm
gonna,
it's
still
going
to
be
completed.
I
was
doing
it
a
little
bit
before
the
meeting,
but
before
we
do
adjourn,
Dylan
I
think
the
one
asked
I
was
talking
about
was
mod
security.
So
we
know
mod
security
is
being
deprecated.
Okay,.
A
And
I
didn't
know
if
nginx
had
comments
on
that.
I
I
know
that's
unprompted
right
now,
so
if
we
need
to
come
back
from
the
team,
that's
completely
fine
as
well,
but
I
don't
want
to
continue
supporting
things
that
are
going
to
be
deprecated.
We
do
a
lot
of
that.
Now
we
pull
in
images,
we
support
them.
Mod
security
would
be
a
huge
undertaking.
I
would
think
we
already
understaffed.
As
is
so
I,
didn't
know
what
nginx's
thoughts
would
be,
as
you
know,
as
a
whole.
C
Well,
I
do
know
that,
with
our
acquisition
by
F5,
a
lot
of
the
mod
security
stuff
has
been
slowly
going
away.
C
B
It's
Daphne.
B
A
That
would
be
great,
I
mean
I,
can't
say
anything
either
we
just
upgraded
to
121.6
from
an
engine
X
perspective
and
I
think
that
is
already
deprecated
from
a
support
perspective,
but
you
know
we're
tied
to
the
open,
Rusty
support
train
as
well,
so
again,
just
working
working
on
trying
to
get
things
upgraded
as
fast
as
possible
and
I
know
that
one's
coming
I
think
that's
mid.
A
Next
year,
I
I
can't
remember
when
the
mod
security
one
was
being
deprecated,
but
I
just
wanna
probably
put
out
an
open
issue
to
get
comments
as
well.
Because
that's
the
other
thing
we
need
to
get
feedback.
On
the
on
the
survey
we
had
a
lot
of
people
I
think
that
was
the
second
or
third
feature
that
folks
used
and
I
saw
a
ticket
today
open
up
about
the
version
of
the
O
wasp
stuff
that
we
use
so
I
know
it's
being
used.
A
I
know
it's
going
to
be
talked
about
so
I
think
I'm,
just
gonna
I'll
put
the
ticket
in
there
as
an
open
issue.
I'll
wait
for
the
comment
from
that.
You
guys
will
can
get
for
us,
and
then
we
can
just
see
what
the
community
comes
back
with
I'm
gonna
start
putting
it
in
the
release.
Notes
because
I
I
I've
done
the
same
thing
with
the
registry.
A
The
the
kubernetes
Sig
release
team
has
done
as
well,
and
we
still
keep
getting
issues
about
folks,
not
understanding
why
they're
not
being
able
to
pull
stuff
so
I'm,
going
to
open
up
the
issue
I'm
going
to
drop
it
in
the
slack
Channel
I
might
put
it
out
in
the
dev
mailing
list
just
to
ask
folks
for
comments,
because
we
just
need
to
put
that
out
there
as
wide
as
possible
as
soon
as
we
deprecate
it
and
folks
are
like
what
happened.
I
want
to
make
sure
we
over
communicate
this
one.
Okay,.
C
We'll
do
we'll
get
we'll
we'll
get
we'll
get
a
full
like.
C
C
A
She
could
update
it
directly,
I
I,
don't
think
the
next
one
is,
you
know
required,
but
you
know
soon
end.
A
B
D
A
No
problem
all
right,
well
I'm,
going
to
take
the
next
half
hour
to
triage
issues
on
don't
really
want
to
stick
around
on
the
recording
to
do
that
and
if
you
folks
want
to
hang
out
you're
more
than
welcome
to
I'll
keep
the
I
can
keep
the
zoom
open
and
with
that
I'll
click.
The
end
recorder.