►
From YouTube: Kubernetes SIG Network meeting for 20230831
Description
Kubernetes SIG Network meeting for 20230831
A
Hello,
everyone
and
welcome
to
the
August
31st
edition
of
the
Sig
Network
meeting
as
usual.
This
meeting
is
governed
under
the
kubernetes
code
of
conduct,
which
basically
boils
down
to
be
nice
to
one
another.
So
please
do
be
nice
to
one
another.
We
ask
that
if
you
have
something
to
say,
please
do
use
the
raise
hand
feature
in
Zoom
anytime.
You
want
to
interject
or
ask
questions
well,
I
see
possibly
some
new
faces,
so
I'll
give
a
couple
seconds.
A
A
Meeting
hello
ram
ram,
says
hello
in
chat
so
because,
because
it's
a
light
agenda
do
feel
free
to
put
something
on
it
in
the
meantime,
here
I'll
start
sharing.
A
Bit
all
right,
so
we
have
triage
and
then
I
just
have
one
little
bit
again.
If
you
want
to
add
something
at
the
end
to
that,
please
do
feel
free.
Otherwise
we
can
make
it
a
short
meeting
so
for
triage,
I
wanted
to
started
with
the
stuff.
That's
unassigned
or
inactive
and
I
found
these
two,
which
is
actually
unusually
low
amount.
If
anybody
has
any
particular
issues,
you'd
like
to
throw
into
triage,
do
link
them
in
the
doc
be
happy
to
look
at
specific
ones.
A
Yeah
I
saw
this
one.
Pod
sitter
should
be
added.
A
And
it
looks
like
last,
we
saw
James
was
trying
to
get
Jay
in
here
and
a
couple,
others
that
might
be
able
to.
C
A
A
Okay,
all
right,
then
I
guess
we'll
I'm
wondering
what
exactly
he's
looking
for
from
Sig
network
but
I
mean.
Obviously
he
I'm
not
really
wondering
that.
But
okay,
I
guess
I'll
just
kind
of
follow
up
on
this
one.
Then
I
haven't
seen
a
whole
lot
of
Windows
stuff
come
through.
So.
B
A
Okay,
I'll
follow
up
on
that
one
then,
and
then
the
only
other
one
that
I
saw
that
was
unassigned
was
removing.
Oh,
when
colel
again,
okay,
I
didn't
removing
the
dependency
of
hns
and
wind
kernel.
C
proxy
test
by
replacing
with
mock
calls
current
tests
and
wind
kernel.
Cou
proxy
are
dependent
on
Windows
H&S
environment.
A
lot
of
this
is
Greek
to
me.
The
tests
expect
hns
to
be
present
and
are
executed.
B
E
A
D
A
Price
yeah,
so
the
only
thing
I
had
to
bring
up
today
was
this
document
which
I
shared
before
just
want
to
share
it
again
for
anybody
who
hasn't
seen
it,
but
basically
it
used
to
be
sub
project
leadership,
we're
calling
it
sub
project
ownership.
Tim
has
taken
a
big
long
kind
of
review
of
this,
and
we've
made
quite
a
few
changes.
A
Thank
you
for
everybody
who
has
shared
feedback,
I
think
we're
getting
there's
a
few
kind
of
bigger
questions,
but
I
think
ultimately
we're
getting
close
to
kind
of
documenting
this
as
something
close
to
what
we
want
for
the
Sig
going
forward.
I
think
the
major
effect
that
this
is
intended
to
have
right
now
is
to
kind
of
reinforce
that
we
want
to
recognize
people
for
their
kind
of
community
building
and
project
management
skills,
in
addition
to
the
historical
Le
technical
skills.
A
So
all
three
of
those
we
just
kind
of
have
more
of
an
emphasis
together
going
forward
if
you
have
any
more
comments
and
stuff
on
this
I
linked
it
in
the
notes.
But
basically
this
document
is
open
for
some
more
comments.
I
imagine
it'll
be
after
cucon
before
we
go
much
further
with
it.
So.
A
It
doesn't
include
a
list,
but
it
does
now
reflect
that
some
are
big,
some
are
small
and
they
have.
Some
of
them
have
different
like,
for
instance,
some
of
them
might
be
small
enough
that
they
don't
really
need
certain
things
like
they
don't
need
a
whole
lot
of
community
buildup
or
project
Outreach.
We
we
have
made
that
those
kind
of
Reflections
we
could
list
them,
though
that'd
be
fine.
F
Yeah
I,
don't
know
I
mean
like
I
I.
Think
of
you
know,
for
example,
two
that
I'm
involved
in
like
I
could
say
that
there's,
for
example,
things
related
to
endpoint
slices
service
Discovery,
whatever
whatever
you
want
to
call
it,
that
that
category
of
things
is
really
small
and
stable
and
almost
nothing
is
changing,
but
it
could
technically
be
called
a
sub
Project
based
on
the
categorization
I.
A
I
see
DNS
could
too
and
DNS
could
follow
in
a
similar.
F
Yeah
and
then,
and
then
also
I,
would
say,
Gateway
is
also
obviously
a
sub
project,
but
it's
you
know
operating
at
a
different
kind
of
scale
or
momentum
right
now,
at
least
so
it's
trying
to
understand
like
what
similarities
there
are
between
those
and
what
differences,
I
guess.
A
F
Yeah
yeah,
that's
that's
kind
of
what
I
was
trying
to
because,
like
there,
you
know,
kubernetes
org
already
has
a
term
called
sub
project
that
traditionally
has
meant.
You
know
a
a
different
repo
with
different
leadership
with
well
sub
leadership,
Etc,
and
this
I
think
is
extended
the
term
sub
project
to
mean
more
than
that
I
think
in
Sig
Network,
which
is
not
necessarily
a
bad
thing.
It
just
just
would
be
good
to
understand
the
difference
between
what
it
means
in
like
Pro
organization,
wide
I
guess
and
what
the
differences
are.
A
F
F
And
I
I
think
it's
really
useful.
To
kind
of
you
know,
write
down,
I
think
some
of
us
who
have
been
involved
in
Sig
Network
for
a
while
have
an
understanding
of
who
the
experts
are
in
different
areas
right,
but
that's
not
obvious
to
to
many
people
and
I
think
it's
very
helpful
to
formalize.
That
and
say
you
know.
Actually
this
person
is
effectively
leading
this
area
or
set
of
people.
So
I
think
that
that
is
a
really
good
goal.
C
Community
and
being
the
person
who
knows
about
endpoint
slices
is
is
very
different
from
running
the
Gateway
project.
Right
like
sub
project
or
or
you
know
in
my
case,
like
you
know,
we've
talked
about
you
know:
I'm
I'm,
the
Q
proxy
guy,
but
I
don't
want
to
run
Cube
proxy
as
as
a
project
where
I'm
like
recruiting
people
and-
and
you
know,
leading
meetings
and
stuff
like
that.
I
just
want
to
you
know,
fix
Cube
proxy
and
that's
very
different
than
starting.
F
C
A
Summary
yeah
and
it
makes
sense
we
don't
want
to
try
to
push
anybody
to
do
anything.
They
don't
want
to
do
either.
That's
not
the
the
goal
here.
So
that's
why
I
continue
to
try
to
gather
feedback,
and
this
has
been
a
slow
roll
because
I,
probably
just
pissed
people
off.
If
I
tried
to
push
it
too
fast
right,
we
got
to
get
it
kind
of
right
for
every.
A
Thank
you
for
that
feedback.
I
got
it
all
commented
here.
I'll
continue
to
think
about
that
and
continue
to
update
this
doc.
Anybody
else
who
hasn't
seen
the
doc
or
just
has
some
more
thoughts.
Now.
Please
do
go
to
that
doc.
It
should
be
available
to
anybody
to
at
least
suggest
and
comment
would
appreciate
more,
but
not
trying
to
go
fast
with
it
again,
because
it's
needs
to
be
done
right
and
that's
it
for
today.
A
Unless
anybody
has
any
last
minute
things,
this
can
be
a
really
really
short
one,
maybe
the
shortest
one.
In
a
long
time
so
give
a
couple
seconds,
and
then
we
can
decide.
F
D
F
F
Yeah
yeah,
I
I'll,
add
to
the
agenda,
but
yeah
good,
good
reminder:
it's
coming
up
awfully
quick,
yep,
good
call
and
and
even
code
freeze
is
prec
coupon
this
time,
so
there's
less
than
a
month
between
kept
freeze
and
code
freeze
this
time.
So
it's
a
pretty
pretty
quick
schedule.
This
time
when
is
coming,
C
free,
I
want
to
say
November
one.
C
G
Okay
kind
of
in
line
with
that,
we
have
a
bunch
of
what
we're
calling
NPS
in
the
network
policy,
API
subgroup
that
are
kind
of
up
for
review
right
now,
not
his
time
box,
obviously
as
he
keps,
but
you
can
find
them
there
and,
if
you're
interested
about
some
of
the
new
features
coming,
please
please
go
check
them
out.
We're
looking
for
more
review
from
everyone
so
and
if.
A
E
E
D
G
D
And
and
what
times
are
you
hand
I
mean
when
when
did
you
expect
to
have
the
so
you're
asking
for
review?
So
when
is
the
deadline
for
the
reviews
in
the
M
peps?
We
have
no
many.
G
We
have
no
de
lines,
and
maybe
that's
like
a
good
thing
to
actually
do
like
in
our
npet
process.
Right
now,
we've
tried
to
keep
it
like
really
lightweight,
and
we
understand
people
are
kind
of
in
and
out
so
we
haven't
put
any
deadlines
on
them
like
I've,
just
been
shepherding
them
along
manually,
but
maybe
that's
something
we
should
start
doing
from
now
on.
Our
like
rough
goal
is
pushing
towards
beta
essentially
for
admin
Network
policy,
so
maybe
I
need
to
put
a
deadline
on
that.
D
G
Yeah
we're
we're
still
really
small,
and
thankfully
we
actually
have
some
talks
at
cucon
coming
up,
so
I'm,
really
hoping
that
we
get
some
more
voices
and
more
help
after
that,
which
is
why
I
haven't
been
quick
to
push
deadlines,
because
you
know
our
Core
group
of
three
or
four
are
all
going
to
plus
one,
but
like
it'd,
be
great.