►
From YouTube: Kubernetes SIG Network Bi-Weekly Meeting for 20230316
Description
Kubernetes SIG Network Bi-Weekly Meeting for 20230316
A
True
sweet,
so
this
is
the
March
16th
kubernetes
Network
meeting.
We
adhere
to
the
cncf
code
of
conduct
tutorials
down
to
Bill
freely.
We
record
these
meetings
and
post
them
on
YouTube
for
your
records.
If
anybody
has
a
last
minute
agenda,
let's
go
ahead
and
add
those,
since
our
agenda
is
quite
light
and
I
also
promise
to
not
end
the
meeting
before
it's
over.
A
C
A
E
We
could
quick
run
through
the
Caps
dashboard
and
see
what
actually
made
progress.
Now
that
the
code
freeze
has
finished.
F
E
D
E
So
the
way
we
usually
run
through
this
is
from
the
right
to
left,
so
looking
for
things
that
we
removed
gates
for
I,
don't
know
that
we
did
any
gate
removals
this
time.
The
one
that
we
flagged
was
Network
policy
Port
range.
D
D
A
E
I'm,
weird
all
right,
never
mind,
I
see
it
I
see
it
we're
viewing
and
direct
okay.
So
did
we
remove?
Oh
those
are
Gates
removed,
sorry
Gates
merged
gate
not
removed,
so
the
third
from
the
right
did
we
move
any
Gates?
No,
that's
tagged
as
28
internal
traffic
policy
is
28.
grpc.
Did
we
remove
the
gate
for
that?
E
F
E
Yeah
grpc
GA
in
27
great
so
it
is
ga
I
must
have
moved
that
one
when
the
pr
went
in
mixed
protocols.
We're
touching
next
in
28,
terminating
endpoints
are
tracking
28.
E
E
Right
scrolling
down
in
the
ga
column,
we've
got
mixed
protocols,
we've
got
tracking
terminating
endpoints
and
we've
got
IP
ranges.
Those
are
all
tagged
for
28,
so
nothing
to
do
in
the
ga
column.
Let's
look
at
beta,
gated
and
merged
expanded
DNS
config.
Did
we
touch
that?
No
that's
tagged
for
28s,
okay,
proxy
terminating
endpoints.
We
decided
to
move
to
28
right.
I
K
I
mean
we're
we're
definitely
to
let
updates
in
this
cycle
are
such
that
we
are
opening
it
up
to
let
custom
heuristics
in
I
hope
that
allows
us
to
go
ga
in
the
next
cycle,
we'll.
E
See:
okay,
I
just
milestoned
it
for
28,
it's
not
showing
here!
Well,
it's
not
showing
on
my
screen,
but
I
did
Milestone
it.
Okay,
then,
let's
look
at
what
what
was
Alpha
and
went
beta
this
cycle?
Multi-Cluster
cider,
is
not
going
beta
yet
right,
Antonio,
because
we're
yeah.
F
E
Okay,
I
Milestone
it
for
28.
admin,
Network
policy
support,
isn't
release
cycle,
locked
minimizing,
iptables,
restore
input,
size
Dan
did
that
move
I
forget
did
that
gate
change.
E
To
Beta,
yes,
I,
just
looked
at
the
gate-
I,
oh,
that's
it
becomes
ownership
cleanup
hold
on
into
my
eyes:
IP
tables.
Yes,
we
did
move
it
to
Beta,
so
I'm
going
to
grab
I'm
going
to
draw
it
on
my
screen
here
and
move
it
into
the
Beta
column.
Excellent,
clean
up,
iptables
chain
ownership
also
moved
to
Beta.
Congratulations
and
let
me
touch
both
of
those
to
Milestone
them
to
28..
E
E
Yeah
I'm
gonna
try
not
to
break
the
release
team
before
the
release.
After
we
cut
the
release,
we'll
come
back
to
this
one
more
time
and
update
Milestones
Reserve
node
ports
for
dynamic
and
static
allocation.
That
did
we
update
that
to
Beta.
E
Okay,
so
I
already
updated
I
wish
there
was
more
metadata
here.
I
probably
should
comment
on
each
of
them,
but
I
can't
comment
from
the
dashboard
okay.
So
then,
let's
look
at
pre-alpha
and
things
that
went
into
Alpha,
multiple
server
sliders
know
one
half.
F
F
E
All
right!
You
get
your
promotion
transient,
node
predicates
wow.
There
were
too
many
caps
around
the
service
controller.
We
did
update
this,
but
we
went
straight
to
Beta
right.
F
E
We
went
straight
to
Beta,
what's
the
gate
name
on
it,
it's
called.
E
Okay,
I'm
pretty
sure
we
moved
that
straight
to
Beta,
so
to
bait
it
with
you,
okay.
What
else
did
we
move
to
Alpha
no
host
IPS
did
not
make
it
dual
stack.
Node
IP
handling
did
move
into
Alpha
right
yeah
and
yes,.
B
Go
ahead,
I
was
gonna,
say,
there's
an
update
to
the
cap.
To
we
didn't
do
everything
we
were
supposed
to
do
for
Alpha.
So
there's
a
an
enhancements
PR
to
to
update
the
cap
to
indicate
what
we
actually
did
do.
E
Me
I've
done
it
before
and
gotten
yelled
at
so
it
wasn't
me:
okay,
yeah,
Cube
proxy,
improved
Ingress
connectivity,
reliability,
which
one
was
that.
E
Yes
and
that
didn't
go
in
so
that
stays
pre-alpha
and
we
didn't
do
anything
with
prefer
local,
so
that
stays
pre-alpha,
okay
and
then
quickly
scanning
the
other
ones.
Was
there
anything
else
that
we
did
that
went
forward?
G
Kpng
sorry,
if
I
sound
like
crap
by
the
way,
I'm
almost
sick,
kpng
Auto
closed.
G
E
Go
hey
so
I
can
reopen
it.
I,
don't
think
the
intention
was
to
close
it,
although
we
do
need
to
figure
out
exactly
what
our
strategy
is
for
resolving
it.
C
B
E
E
D
A
D
Wheat
I
didn't
get
time
to
actually
go
through
a
lot
of
these.
We
do
have
a
lot
of
items
with
needs
triage,
so
I,
don't
know
what
the
overall
plan
is
to
get
them
untagged
or
if
we're
gonna
keep
them,
we
could
probably
start
with
the
top.
If
that
works
for
everybody.
That's
you.
E
We
should
look
at
them
if
they
still
say
needs
triage.
Okay,.
D
B
Yeah
so
I
left
this
as
needs
triage,
just
so
that
you
know
other
people
would
look
at
it
while
they
were
skimming
through
bugs.
But
basically
you
need
to
figure
out
how
to
make
health
and
and
metrics
work
correctly
in
dual
stack
proxies
where
we
currently
only
have
one
Health
server
and
one
set
of
metrics
and
both
sub
proxies
are
writing
over
the
same
fields
and
I.
Don't
actually
know
for
sure
what
the
best
answer
is.
If
you
scroll
down
to
the
last
comment
and
mention
that.
F
D
B
D
F
D
The
same
node,
what
do
we
want
to
do
with
this?
Should
we
accept
this,
or
does
someone
want
to
try
to
triage
this?
A
little
bit
more.
E
D
F
I
found
this
straight
in
another
bag.
So
basically,
when
you
set
a
service
with
published,
not
ready,
addresses
the
condition
which
one
is
ready
is
true,
so
you
have
great.
The
three
wants
us
through
and
the
API
doc
says
that
ready
can
never
be
true.
If
service
is
true
or
terminated
it
through
I,
don't
remember
so.
The
API
docker.
A
F
F
E
C
E
Like
I
I,
I
trust,
you
know
the
people
here
who
are
filing
bugs
to
know
if
they're
real
bugs.
H
G
G
H
K
The
okay,
so
my
understanding
of
this
I
I,
dug
into
it
a
bit
is
this-
is
more
of
an
API
Machinery
bug
than
anything
tied
to
Gateway,
API
or
say
Network,
so
we
may
I,
don't
know
it
may
be
something
where
we
want
to
remove
Sig
Network,
my
understanding
of
the
actual
underlying
bug
there's
been
threads
in
slack,
both
in
Gateway
API
and
the
API
Machinery
Channel
around
this,
and
it
it
generally
just
seems
that
it's
not
possible
to
use
the
client
go
fake
package
with
these
custom
types.
K
That's
my
understanding
of
it
today
and
the
documentation
suggests.
A
K
E
K
Yeah
I
agree:
I'm
fine,
you
know
if
Shane
or
I
take
it.
I
know
we're
we're
both
on
the
threads
in
slack,
so
I
I
don't
care.
If
either
one
of
us
are
assigned,
we
can
help
make
sure
someone
on
a
piano
machinery.
G
D
D
K
This
is
this.
Is
me,
I
really
need
to
Loop
in
someone
from
six
scalability
I.
This
has
been
on
my
list.
I
can
probably
triage
accept
it
it's
confusing
at
at
best.
You
know
it's
not
I.
Don't
know
that
a
bug
is
the
correct
term
here,
because
it
it
works.
It's
just
a
confusing
bit
of
code,
so
yeah
I,
I
I've,
been
meaning
to
follow
up
just
been
underwater.
D
Sounds
good
should
we
remove
the
flag
yeah.
D
E
Let's
and
let's
leave
this
see
if
Lars
wants
to
follow
up
on
it,
we
can
revisit
next
time
all.
D
D
G
C
G
G
The
next
one
I
think
I
just
need
to
Market
is
not
accepted.
I
am
oh,
is
this
the
one
I
think
it
is?
Oh.
E
This
one
we
need
to
do
some
follow-up
on
oh
yeah,
yeah
I.
Remember
this
one,
oh
yeah,
sorry
I
thought
this
was
assigned
to
me.
I
was
doing
some
follow-up
on
this
to
trying
to
figure
out
what
the
implications
of
changing
this
would
be,
but
with
code
freeze,
I
haven't
had
any
time
in
the
last
month.
E
Been
reopened,
it's
the
arm
wrestling
match.
At
this
point,
we
have
sort
of
agreed
that
this
is
a
logical,
heuristic
right,
Rob.
K
Yes,
I,
don't
know
if
you're
intending
to
share
a
slack
by
the
way,
but
yeah.
K
No
worries
so
yes
that
this
is
something
that
I
think
we
we
need
to.
K
Agree,
one
of
the
things
that
we've
been
doing
with
hints
is
trying
to
open
it
up
so
different
different
people
can
bring
their
own
heuristic
I'm,
not
saying
that
needs
to
be
how
we
solve
this,
but
we've
at
least
opened
the
door
that
there
can
be
any
number
of
ways.
K
The
last
time
we
we
looked
into
it.
It
was
really
difficult
to
decide
what
specific
variation
of
this
we
wanted
to
support.
I
know
we
don't
want
to
bring
back
all
the
topology
keys,
but
it
is
difficult
to
decide.
Okay,
do
we
want
prefer
Zone
prefer
region?
Do
we
want
require
Zone?
Do
we?
You
know,
I,
think
the
thing
that
we
want
to
expose
just
prefer
zone
or
or
that
that
equivalent,
but.
D
E
I
agree:
I
agree.
My
feeling
at
this
point
is
now
that
we've
got
the
heuristic,
the
The
annotation
renamed.
It
would
be
reasonable
to
add
a
you
know:
closest
First,
if
possible,
pick
a
good
name
heuristic
and
implement
it
as
prefer
same
node
prefer
same
Zone,
prefer
same
region
yeah,
so
I
guess
we
can
triage
accept
this.
C
J
C
J
J
Classic
you
know
finally
got
merged
for
Wanda
27,
which
is
awesome,
and
then
the
question
came
up.
Okay,
do
we
cherry
pick
it
and
say
cloud
provider
said
well
send
Sig
network
if
you
scroll
all
the
way
to
the
bottom,
you'll
see
that
Cal
and
Tim
are
the
ones
who
weighed
in
and
said
yes,
this
can
go
in
since
Cal
and
Tim
are
the
ones
who
vetted
this.
How
about
we
make
sure
they're?
Okay
with
the
Cherry
picks,
also
not
breaking
the
world
and
I
said
I
am
happy
to
go
to
Sig
network.
E
Okay,
I'll
have
to
remember
what
this
looked
like.
This.
J
Is
for
when
node
IPS
change
colon
the
thing
you
think
won't
happen,
but,
alas,
it
does
sometimes.
E
C
J
It's
it's
totally
fine
if
we
just
go
back
a
few,
but
I
was
just
looking
myself
at
numbers
of
how
many
people
run
old
things
and
spoiler
alert
people
run
them.
So
you
know,
however,.
I
J
I
think
so,
I
don't
think
the
church
deadline
for
two
four
is
over,
but
anyway
I.
Don't
I.
Don't
want
to
litigate
that
here
I'm
just
like
hey,
if
it
makes
sense
to
cherry
pick
any
of
this
to
some
of
them.
It
would
be
awesome
if
the
people
who
understand
whether
or
not
if
it's
a
good
idea
can
get
some
eyes
on
it.
In
the.
I
F
That's
it
it's,
you
know
the
the
thing
is
this
owners,
they
changed
the
the
mechanism,
so
you
need
someone
from
that
specific
owner
file
since
I,
don't
know
which
person
because
no
longer
Cascades
the
the
rights
from
the
top
to
to
this
folder.
J
E
As
many
as
many
CRS
as
I
looked
at
in
the
last
week,
I
have
no
memory
of
this.
One
I'll
have
to
go.
Look
at
it,
I
mean
I.
Don't
have
any
objection.
You
know
I've
seen
no
indication
that
it's
a
problem
right.
So
it's
not.
D
Does
anybody
have
any
last
minute
items
to
add
in.
E
Yes,
I
will
not
be
there,
but
you
guys
should
have
a
traditional
Cygnet
lunch
and
have
a
have
a
beer
and
think
of
me.
I
I
I
J
C
I
I
D
Thick
cheese
pie,
okay,
yay.