►
From YouTube: Network Policy API Meeting for 20230620
Description
Network Policy API Meeting for 20230620
A
Awesome
today
is
Tuesday
June
20th
2023.
This
is
a
meeting
of
the
Sig
Network
policy,
API
subgroup
to
Sig
Network.
This
is
a
cncf
sponsored
meeting
and
yeah.
So
please
be
nice
to
each
other
and
don't
use
any
horrible
language,
and
let's
have
a
good
meeting
today.
So
on
the
agenda.
There's
not
too
much.
Raul
I
was
on
vacation.
I
got
back
and
I
saw
your
PR
I
gave
a
review
today,
there's
just
a
little
couple
few
little
things.
A
So
if
you
could
just
get
to
those,
then
I'm
definitely
happy
to
merge.
It.
A
Yeah
no
problem,
thank
you
for
opening
up
PR
I
I
had
done
all
this
website,
stuff
kind
of
as
quickly
as
I,
possibly
could
to
get
something
done
so
I'm
glad
you're
looking
at
it,
I'm
really
happy
to
see
that
cool
and
then
so
in
you
also
added
a
question
to
the
agenda
about
north-south
traffic.
We
have
been
talking
a
bit
about
that
and
I.
Think
Surya
has
specifically
tried
to
address
the
egress
case.
A
The
North
traffic
here
so
maybe
start
there
with
a
little
bit
of
review
and
we
can
go
from
there
if
you
think
that
makes
sense.
Bro.
B
Yeah
that
sounds
perfect
thanks
for
linking
it.
A
Yeah-
and
so
just
you
haven't
been
here
in
a
little
while
no
worries
kind
of
to
catch-
you
up,
we've
started
like
really
ever
since
release
1.0.1.0
we've
tried
to
kind
of
start
modeling
ourselves
more
so
after
Gateway
API,
because
they
do
a
lot
of
awesome
things.
So
we
are
going
to
start
opening
end
peps
we're
calling
them
for
new
enhancements
kind
of
in
line
with
the
Gateway
API
gaps.
A
So
that's
kind
of
what
that
means,
so
we're
still
kind
of
figuring
it
all
out,
but
it
seems
like
a
good
way
to
standardize
adding
new
use
cases
for
later
API
releases.
B
Yeah
that
sounds
good
I'll
I'll
take
a
look
at
this
and
maybe
just
drop
comments
in
that.
If
I
have
any
thoughts.
D
C
Network
so
I
think
I'll
just
open
a
similar
PRS
array
has
here
right
because
I
know
we
try
to
figure
out
the
format
and
everything.
So
this
one
is
like
our
current
standard
right.
A
Correct
and
I
actually
left
a
comment
to
that
kind
of
saying,
like
we
probably
as
she
makes
this
just
because
she
was
the
first
one
to
open
one.
We
should
probably
have
a
template
like
just
a
simple
one
for
npeps,
and
then
you
can
follow
that
if
that
makes
sense-
or
you
can
help
us
here-
kind
of
make
the
template,
but.
C
A
Yeah
just
create
a
template,
make
sure
Siri
is
on
board
I,
don't
really
care
if
it's
done
by
you
or
her
she's,
not
here
this
week,
I
think
she's
at
Devcon,
so
yeah.
If
you
want
to
get
to
it,
first
no
problem
but
I
think
that's
the
best
way
to
do
it,
because
then,
basically,
we'll
kind
of
hash
out
any
design
questions
we
have
here
and
merge
it.
A
The
one
thing
I
do
want
to
figure
out
as
part
of
the
mpep
process
process
is
I,
don't
think
we
need
to
have
like
I
want
it
to
be
like
really
easy
for
submitters
to
open
right
like
we
don't
want
to
have
to
hash
out
everything
in
the
first
merge
of
an
npep
like
we
want
to
be
able
to
signify
that
you
know,
we've
all
reviewed
it.
We
think
it
makes
sense,
but
there
might
still
be
some
unanswered
questions.
A
A
Awesome
thanks
so
much
Nadia
cool.
What
else
did
I
have
on
here?
Are
there
any
other
questions
about
rules,
PR,
North,
South
traffic
control
in
general?
For
folks,
who
may
be
new
here,
I
think
I
see
some
new
names.
A
The
current
version
of
the
admin
or
policy
and
Baseline
Network
policy
does
not
reference
North
South
traffic
at
all.
It
only
focuses
on
East-West,
but
this
is
something
folks
are
gonna.
A
So
then,
we'll
have
kind
of
like
a
list
of
enhancements
that
we
want
to
have
in
before
we
get
to
Beta
or
even
a
V1
Alpha
One
Two.
If
we
feel
like
it
needs
to
be
there.
A
Sweet:
okay,
thanks
Nadia
thanks
Raul
for
opening
those
I
did
open
an
issue,
I
kind
of
talked
to
Yang
about
this
out
of
band
and
got
his
preliminary
approval.
A
Basically,
we
went
from
three
to
two
maintainers,
because
Abhishek
kind
of
had
to
step
away,
and
so
we'd
like
to
get
back
to
three
and
I'm,
proposing
Dan
Winship
just
because
he
has
kind
of
been
in
instrumental
in
in
all
of
this
since
the
beginning.
So
if
you
could
show
your
support
here,
I'll
kind
of
let
it
soak
for
a
week
and
if
there's
no
objections,
I'll
open,
a
PR,
adding
and
as
an
approver
I
think
it'll
help
us
get
stuff
done
a
little
bit
quicker.
A
C
Yeah
yeah,
that's
another
thing:
it's
like
we
have
the
Google
Doc
around
the
new
API
for
Dynasty,
right
and
I
thought.
Maybe
it
is
time
to
make
it
more
official
and
post
something
but
I'm
not
sure.
What's
the
Next
Step.
A
A
So
I
think
kind
of
in
line
with
what
we're
what
we've
been
doing,
it
makes
the
most
sense
to
open
an
n-pep
and
it
can
kind
of
just
be
based
off
Dan's
document.
If
that's
the
desire,
I
know
Yang
felt
strongly
about
this
and
he's
not
here
today,
so
it
would
definitely
be
good
to
make
sure
he's
he's
closely
involved
and
anyone
else
who's
involved
also
or
wants
to
get
involved
with
the
tenancy
discussion.
This
would
be
a
good
place
to
do
it.
A
Right,
no
I
totally
agree,
I
think
maybe
Nadia.
What
we
should
do
is
have
a
separate
PR
to
kind
of
write,
some
rules
for
what
npep
should
look
like,
and
then
we
can
build
this
sort
of
use
case
into
that
right,
like
we
can
have
a
slightly
different
template
or
something
for
and
peps
that
are
trying
to
change
something.
That's
already
there
versus
end
peps
that
are
introducing
totally
new
yeah.
C
C
Be
about
the
use
case
right,
but
that's
like
a
subgroup
of
the,
and
perhaps
we
expect
I
guess
so.
Maybe
we
can
well
let
people
open
they
didn't
more
or
less
free
format
and
then
create
some
subgroups
for
something
like
proposing
a
new
use
case
and
I
don't
know.
Maybe
this
tendency
API
will
be
an
example
of
proposing
a
change
to
the
existing
API.
Then
there
may
be
some
other
types
of
and
pubs.
I
guess.
A
Yeah
I'm
totally
fine
with
that
I
mean
it's
it's
an
open
slate
like.
We
should
definitely
always
look
back
at
what
gave
API
has
done.
I
think
they
have
a
couple
different
statuses.
Maybe
I
haven't
looked
in
a
while,
so
we
might
be
able
to
kind
of
take
a
version
of
that,
but
if
we
can
keep
it
similar,
I
think
at
the
end
of
the
day.
A
A
Cool
awesome
and
I'm
gonna,
we
don't
have
anything
else
on
the
agenda,
so
I'm
gonna
put
Raul
on
the
spot
a
little
bit
roll.
Do
you
know
anything
about
Google
kind
of
working
to
implement,
amp
and
still
am.
Is
that
effort
changed
at
all
I
know
we
have
an
issue
tracking
it,
but
a
long
time
ago,
I
thought
that
was
the
goal
so
yeah.
That's
there.
B
No
that
it's
it's
good,
that
you
bring
that
up.
That
was
something
we
were
discussing
recently
long
story
short,
there's
still
no
Super
Active
development
on
that
front.
But
while
we
were
talking
internally,
we
we
were
revisiting
some
of
the
points
that
are
open
in
that
in
that
issue
against
psyllium
I.
B
Think
one
of
these
psyllium
maintainers
commented
a
point
basically
saying
that
priorities
are
going
to
be
difficult
for
psyllium,
implement
and
I
I
think
we
were
wondering
if
anyone's
played
around
with
an
ebpf
version
of
admin,
Network
policy,
the
I,
think
some
of
the
concerns
around
it
were
that
perhaps
the
data
structures
that
maybe
this
is
just
a
psyllium,
a
specific
problem,
maybe
ebpf
itself
can
handle
this
just
fine.
The
concern
was
that
the
data
structure
used
in
psyllium
today
doesn't
lend
itself
to
priorities.
A
Correct
correct-
and
you
know
some
slam
folks
have
voice
concerns
about
this
before
to
me
out
of
band,
and
my
message
to
them
was:
please
come
to
the
Upstream
meetings
like
please
come
get
involved
like
if
this
is
not
possible
for
you
to
implement
come
say
so
so
that
has
yet
to
happen.
A
So
it's
my
message
is
still
the
same
right
like
I
would
love
to
hear
more
about
their
problems.
They
have
to
come,
get
involved
right
like
yeah.
That's
that's
on
them
as
to
whether
or
not
this
is
impossible
to
do.
An
evpf
I
haven't
tried,
but
if
that's
something
that
would
help
you
Raul,
like
I,
could
possibly
help
out
with
that
I'd
it'd
be
interesting.
For
me,
I'd
do
a
lot
of
BPF,
so
I
can
see
how
the
data
structures
are
being
used.
A
Currently
could
be
tough,
but
there
might
be
some
kind
of
design
change
that
could
make
it
a
bit
easier.
I'd
have
to
look
at
it
like,
like.
Obviously,
priorities
are
harder
to
implement
than
in
the
data
plane
than
you
know.
The
additive
policy
rules
that
we've
always
had
so
you
know
I,
don't
know
every
data
plane
struggles
with
it,
especially
when
we're
talking
scale.
A
B
A
No
totally
I
think
the
definition
of
scale
is
kind
of
relative,
though
right,
like
this
priorities
are
basically
like
what
people
want.
You
know,
they're,
not
the
best
in
the
data
path,
but
I
feel
like
it's.
What
most
customers
ask
for
it's,
what
most
customers
expect
and
whether
that's
a
good
thing
or
not
it?
You
know
it
is
what
it
is
right
and
I
think
us
as
API
designers
right.
We
want
to
have
an
eye
on
scale
but
at
the
same
time,
we're
more
concerned
with
what
people
want
and
what
end
users
want.
A
I,
also
think,
as
we
keep
making
more
noise
Folks
at
psyllium
and
other
places
may
be
more
inclined
to
implement
and
try
and
prioritize
this.
So
our
goal
from
this
group
has
just
been
like
getting
talk
submitted.
You
know
pushing
the
API
to
later
stages
and
hopefully
getting
more
uptake
from
influenters.
B
Yeah
I
I
will
check
in
with
I
know
our
team
talks
to
the
psyllium
open
source
as
well
I'll
just
check
in
and
see
if
We've
brought
this
up,
if
we
can,
whether
we
can
get
traction
on
the
open
source
side
of
things.
A
Yeah
and
I'm
happy
to
reach
out
with
them
again.
You
know
like
I.
Would
love
love,
love
for
them
to
come
here
and
get
involved,
it's
kind
of
where
it's
at,
but
I'm
not
going
to
reach
out
every
day
and
ask
them
yeah?
A
Definitely,
but
no
I'm
happy
to
to
see
you
back
here
and
yeah,
that's
kind
of
where
we're
at
so
in
some
of
those
efforts
we
are
trying
to
do
a
maintainers
track.
Talk
for
this
subgroup
and
kubecon
North
America,
Nadia
and
folks
have
also
submitted
a
talk
on
AMP
or
involving
amp,
and
then
we
have
another
separate
talk
about
AMP,
so
hopefully
will
be
three
separate
talks
concerning
amp
and
the
network
policy
API
to
kind
of
help
us
spread
knowledge
about
it.
So
that's
our
end
goal.
A
C
D
D
You
know
sure
yeah
do
you
have
that's
a
comment
on
I'll
get
those
addresses
as
soon
as
possible
and
then
you
know,
I
think
that
one
should
be
able
to
to
merge
I
think
we
discovered
the
small
issue
on
the
the
example
specs
right,
so
I'll
get
it
fixed,
I.
Think,
probably
today
and
I
can
we
can.
You
can
take
a
look
at
it
again,
but
that's
basically
all
from
my
side
and
okay
and.
A
No
worries
about
me.
Yeah
example:
no
worries
about
the
example
fixes
Yang
Raul
that
actually
has
a
a
patch
to
move
those
examples
around.
So
I
asked
him
just
to
fix
it.
It
was
a
small
six.
D
All
right
and
I
also
wanted
just
to
update
that
the
implementation
and
interest
moving
moving
good
overall,
so
I
think
I'm
should
be
opening
in
PR
for
entry
support.
Maybe
in
one
or
two
weeks,
I
guess.
A
Amazing
yeah,
that's
great
news:
Surya
is
working
hard
on
the
conformance
test,
so
as
you
kind
of
spec
out
that
PR,
let's
make
sure
you
two
are
talking
and-
and
you
are
trying
to
maybe
run
some
of
those
conformance
tests,
at
least
potentially
yeah
yeah.
But
that's
great
news
thanks
Yang,
that's
really
awesome.
A
The
other
thing
I
think
before
you
got
here
that
we
were
talking
about,
is
I.
Think
Nadia
is
going
to
open
an
end
pep
for
us
to
talk
more
about
how
we
represent
tenancy
kind
of
coming
from
Dan,
stock
and
I
know.
You
were
super
interested
in
that,
so
just
keep
an
eye
out
for
that.
We're
still
kind
of
figuring
out
the
whole
npep
template
and
process,
but
I
think
that's
going
to
be
coming
here
in
the
near
future.
D
No,
that's!
That's
all
for
myself.
A
Cool
well
thanks
for
stopping
by
everybody,
I,
look
forward
to
seeing
you
all
in
two
weeks
and
in
the
meantime,
just
find
us
some
slack
Community
thing
or
have
any
questions
thanks.
So
much
have
a
good
one.