►
From YouTube: [SIG-Network] Ingress NGINX meeting 20210511
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
everyone-
this
is
sig
netwicking,
ingress,
nginx
sub
project
meeting
today
is
may
11th
2021.
This
is
a
kubernetes
community
meeting
and
we
ask
that
you
comply
with
the
code
of
conduct,
which
is
basically
be
excellent
with
each
other.
If
you
have
any
issues,
please
report
it
to
the
sig
chairs
or
anyone
running
this
meeting
privately.
Thank
you.
A
So
today
I
wanted
to
get
started
on
the
conversation
just
moving
through.
I
have
the
I
have
some
open
topics
from
the.
I
want
to
look
at
some
of
the
open
issues
that
are
stale
and
then
move
forward.
The
idea
here
is
that
I
want
to
try
to
start
cleaning
up
some
of
the
open
issues
that
we
have
and
just
going
through
and
just
trying
to
get
movement
through
the
open
issues,
we'll
go
ahead
and
start
with.
Is
there
any
new
members
who
want
to
introduce
themselves
to
the
team.
B
Oh
yeah
yeah,
I'm
new,
so
this
is
my
first
nginx
meeting,
so
I
I
contribute
around
the
kubernetes
release
engineering
release
team
meeting
and
I'm
the
release.
Note
shadow
for
1.22-
and
I
I
seen
this-
you
know
this-
this
email-
that
the
engineering
group
needs
some
help,
so
I'm
here
to
maybe
contribute
to
some
issues
and
help
the
community
out
in
general.
So
yeah
excited
to
be
here.
C
Awesome,
thank
you
for
being
here,
I'm
in
you
u2
as
well,
but
I
did
some
small
contributions
in
the
past
for
nginx.
I
think
was
my
first
project
that
I
did
something
at
the
kubernetes
a
long
time
ago.
Hi
my
name
is
carlos.
I
work
on
the
secret
release
as
a
branch
manager
and
also
in
cluster
api
and
engine
x.
Ingress
have
some
space
in
my
heart
forever
and
then
I
don't
like
to
get
this
project
abundant.
That's
why
I'm
joining
as
well
to
see
where
they
can
help.
C
D
Yeah
this
ajith
here
more,
a
user
looking
for
options
for
apache
and
web
services,
basically
and
also
load
balancing
I'm
at
a
startup.
We
are
an
iot
company
with
some
framework
and
we
have
the
front
end
for
our
visualization
end.
We
use
different
databases
and
we're
trying
to
present
we're
using
apache.
So
it's
more
I'm
going
to
be
the
consumer
rather
than
developing
this
area.
So
that
was
my
reason.
My
question
about
performance.
A
E
Hello,
my
name
is
christoph
I'm
from
budapest,
hungary,
my
company
uses
also
heavily
uses
nginx
ingress,
and
this
is
my
first
time
at
this
meeting
so
yeah
it's
good
to
be
here
and
I
try
to
catch
up
with
with
the
topics
and
everything
and
and
get
more
involved
as
possible.
So
thank
you
guys
for
for
having
me
here.
F
A
Well,
thank
for
joining
us
and
thanks
for
the
help
that
you've
already
been
giving
us
so
we'll
be
greatly
appreciated
in
the
future
as
well.
G
Yeah
yeah,
I
mean
one
it's
my
second
time
to
at
least
meeting
come
from
the
apache
ps6
community.
Api
six
is
a
api
gateway,
so
it's
also
based
on
engix
and
lula.
So
I'm
interested
to
contribute
to
this
project.
A
Okay,
then
go
ahead
and
get
started
running
throughs.
I
don't
know
why
I
just
muted
myself,
so
we've
got
some
previous
action
items
that
we've
been
working
through,
so
ricardo
has
been
helpful
in
the
transition
as
well.
So
we've
got
a
pull
request
out
there
for
mapping
out
how
the
architecture
works.
From
that
perspective,
we've
categorized
these
issues
really.
A
I
just
pulled
them
from
the
github
api
to
give
us
an
understanding,
an
idea
of
what
we're
looking
at
the
you
know
the
molehill
or
mountain
so
trying
to
understand
how
big
some
of
the
issues
are,
that
we're
working
through
I've
got
a
couple
of
open
things,
still
trying
to
understand,
investigating
decayed
version
versus
nginx,
the
case
version
and
the
supported
nginx
version.
So
if
somebody
wants
to
look
at
that
as
well,
that's
definitely
an
open
item
that
we
still
need
to
understand
how
we
would
start
looking
at
deprecation.
A
If
we
need
to
remove
that
tag
and
then
start
moving
through
because
about
25
of
the
things
that
are
out
there
are
bugs
or
features
so
about
half
of
everything
that
we've
got
our
bugs
are
featured.
So
I
want
to
get
through
some
of
the
older
things,
so
we
can
move
through
that
remove
those
and
move
that
and
move
that
label
and
then
go
from
there.
So
I've
got
the
all
of
the
issues
in
this
git
lab
are
in
this
excel
spreadsheet,
that
we
can
slice
and
dice
and
look
through.
C
A
So
I
was
looking
through
this,
so
alejandro
obviously
has
made
several
comments
on
some
of
these
from
the
older
ones,
but
just
wanted
to
go
through
because
it
they
do
get
stale
and
I
get
through
some
issues
on
that.
So
this
one
I
didn't
get
a
chance
to
read
through
just
yet.
But
this
looks
like
this
was
an
open
bug
and
I
don't
know
if
it
still
is
from
that
perspective.
So.
A
C
D
A
C
C
A
A
Obviously,
we
don't
have
enough
people
to
just
keep
assigning
these
out.
So
it's
just
this
is
the
just
the
conversation
of.
Is
this
still
an
issue?
Do
we
need
to
continue
to
walk
through,
but
this
one
looks
like
it's
a
documentation,
question.
C
But
what's
happening.
A
That
that
is,
that
a
kind
label
I'm
still.
A
Yeah,
let
me
go
look
at
the
the
labels
that
are
on
for
this
one.
This
is
the
joys
of
learning
as
new
people
right.
So,
if
anyone's
got
any
suggestions
on
that,
let
me
know.
C
A
A
A
This
one
looks
a
little
bit
more
complicated
because
it
would
be
easy
to
update
the
documentation
but
looks
like
it's
a
breaking
change,
because
we
want
to
change
the
the
annotation
instead
of
being
a
white
whitelist
or
a
blacklist
source
ranging
we
want
to
change
it
to
allow
listing
the
problem
is
that
it's
a
breaking
change
because
the
annotations
won't
be
back
supported,
so
don't
know
what
the
proper
way
for
us
to
move
forward.
With
this
I
mean,
if
we
we
do
it
from
a
breaking
change.
A
We
just
rev
the
version
up
because
right
now
we're
sitting
at
46,
and
this
is
all
in
terms
of
us
moving
towards
a
more
inclusive
language.
So
we
already
have
another
pull
request:
open,
that's
asking
for
another
annotation
from
a
block
list
and
we're
changing
the
verbiage.
So
I
think
if
we
were
to
just
rev
the
version
from
that
perspective,
making
sure
that
it's
known
in
the
change
log,
that's
a
breaking
change.
What
do
you
guys?
Think?
I
mean?
F
A
Totally-
and
I
know
we're
using
semantic
versioning,
so
I
don't
know
how
adolfo
or
alejandro
or
the
team
we're
using
changes
from
that
perspective
or
to
signal
that
it
was
a
breaking
change.
So
that's
something
too
that
we
need
to
discuss
as
a
project,
so
I
haven't
had
a
chance
to
get
that
follow-up
with
ricardo,
so
that
can
also
be
a
point
of
discussion
as
well.
If
we
just
rev
it
to
146.,
I
don't
don't
know.
C
A
That
was
the
other
thing,
as
part
of
the
discussion
with
everyone
else
as
well
is
just
how
we're
getting
into
a
better
cycle
of
pushing
out
changes,
because
the
only
reason
we
had
the
last
release
was
because
of
the
the
the
issue
with
the
local
host
problem.
So
we
just
need
to
get
better
understanding
of
how
we're
going
to
get
into
a
really
cycle.
C
A
A
C
A
C
A
A
A
A
A
A
So
that's
the
thing,
too,
is
that
these
are.
These
are
a
little
old
as
well
so
december,
2020.
C
D
A
A
C
C
G
A
A
A
So
that
was
the
that
was
all
the
either
sterile
or
the
rotten
tickets.
Does
anyone
have
before
we
move
into
bugs?
Let
me
just
check
the
mixture.
Are
we
good
on
time
because
I
know
we
scheduled
this
for
an
hour,
but
the
agenda
only.
Has
it
really
set
up
for
a
half
hour,
so
we've
still
got
time
we
can
start
moving
into
do
we
does
anyone
have
any
bugs
that
we
need
to
discuss?
From
this
perspective.
C
A
I
didn't
really
see
any
open
issues
from
that
perspective
that
were
at
least
I
again
there's
250
issues
and
I've
not
gone
through
all
of
them,
and
there
doesn't
seem
to
be
no
one's
screaming
about
which
ones
we
should
be
taking,
which
ones
we
shouldn't
be.
So
I
just
need
to
figure
out
from
that
perspective
with
you
know,
getting
more
support
and
trying
to
figure
out
which
ones
we
should
be
looking
at
from
the
community
perspective.
A
C
A
A
This
might
have
been
one
that
ricardo
was
looking
into
about
to
get
some
follow-up
with
with
him
on
this
to
see,
if
he's
actually
looking
into
this.
A
A
A
This
just
to
understand
how
we
can
support
this
and
being
able
to
have
a
cluster
to
replicate
this
issue.
C
C
A
C
A
A
A
A
Does
the
this
is
just
a
question,
and
probably
I
don't
know
if
anyone
on
it
doesn't
automatically
reload
if
the
secret
gets
updated,
if
you've
got
something
provisioned,
if
you've
got
a
service
provision
or
that's
using
a
secret
using
a
cert
from
a
secret,
does
it
automatically
provision
it
one?
If
you
update
the
secret,
I'm
guessing,
that's
the
assumption
here,
he's
assuming
that
there's
no
real
trigger,
as
I
would
think
yeah.
C
A
Well,
this
is
a
newer
comment,
but
yeah,
so
this
would
just
require
investigation
on
if
it
actually
does
that,
because
I
mean
this
would
make
sense
if
he's
got
newer,
pods
that
get
the
new
cert
and
the
old
ones
that
haven't
been
recycled
yet,
oh,
he
did
delete
everything
and
redeploy.
This
is
going
to
require
someone
to
do
some.
F
A
A
C
A
A
A
C
Yeah,
I
I
would
say
like,
if
is
all
the
version,
just
a
recommend
mentioning
that
meter
and
asking
like
if
this
is
still
an
issue
for
the
newer
versions.
C
Like
a
cousin,
maybe
41
yeah.
G
A
A
A
A
A
A
A
You
follow
up
with
ricardo
anyone
and
see
if
we
can.
A
A
A
A
A
A
I
think
from
that
perspective,
then
this
is
just
there's
a
fix,
but
there's
that's
not
a
real.
I
don't
want
to
say
a
real
issue.
It
is
an
issue,
but
this
is
one
I'm
just
going
to
say.
We
help
wanted.
B
B
A
A
Is
about
that
this
is
12.
yeah.
We
I
mean,
we've
been
through
a
good
number
of
issues
and
we
just
got
to
keep
working
through
them.
So
I've
got
time
scheduled
for
myself
throughout
the
week,
but
yeah
we
just
want
to
make
sure
we
keep
moving
things
along
so
yeah.
We
can
go
ahead
and
stop
now
for
everyone,
because
that
considerable
amount
of
people
have
already
dropped
off.
A
Awesome
thanks
everyone
for
joining
I'll
post,
that
all
the
meetings
are
posted
and
I'll
get
the
ticket
to
sign
out
and
update
some
of
the
other
things
as
well.
So
thanks
everyone.
Thank
you.
Bye.