►
From YouTube: Network Policy API BI-Weekly Meeting for 20211129
Description
Network Policy API BI-Weekly Meeting for 20211129
A
Awesome
so
today
is
november
29th,
not
the
28th
2021.
This
is
a
meeting
of
the
sig
network
policy,
api
subgroup
to
sig
network.
This
is
a
cncf
certified
meeting,
so
please
be
nice
to
each
other
and
try
and
use
good
language.
You
are
being
recorded,
so
just
be
aware
of
that.
So
let's
go
ahead
and
have
a
good
meeting
for
today,
not
much
on
the
agenda.
A
I
took
a
look
at
issues.
There
wasn't
anything
new
since
our
last
time
there
was
that
one
issue
outstanding,
but
I
gave
it
a
comment.
It
was
a
problem
with
the
cni,
specifically
calico,
not
anything
for
us
to
handle
the
only
major
thing.
Oh
by
the
way,
I
will
share
the
agenda
because
I
did
reach
out
and
ask
for
the
agenda
to
be
put
in
the
calendar,
invite
and
I
think
it
just
got
lost
in
the
weeds.
So
I'll
ask
you
that
again.
A
The
only
thing
I
had
on
the
agenda
was
around
cmp.
The
plan
is
still
the
same
and
next
upstream
meeting
I
believe
we
are
going
to
present
it,
hopefully
for
an
almost
final
set
of
approvals,
but
before
we
do
that,
I
just
wanted
to
make
sure
I
was
reading
through
it
today
and
it
seemed
like
the
priority
section
still
needed
a
little
bit
of
work.
A
B
B
Described
it
in
the
prior
sig
network
meeting
and
we
had
invited
people
to
look
at
it,
so
they
actually
got
an
entire
month
almost
to
look
at
it,
but
I
don't
think
we've
had
any
comments,
so
I
don't
know
if
you
want
to
poke
before
next
signature
community
meeting,
which
is
actually
this
thursday
yeah.
I
will
poke
today.
A
A
A
A
So
I
guess
we
could
call
it
upstream
validation
about
what
a
network
policy
should
do
and
this
validation
has
actually
been
tested
out
with
a
couple
different
cni's
and
matt
gave
us
the
go-ahead
to
import
this
into
sig
network
policy
api.
I
just
don't
really
know
exactly
how
I
should
do
that.
I
didn't
know
if
anyone
knows
of
any
prior
art
in
kubernetes,
where
a
repo
kind
of
wraps
another
repo,
would
I
just
import
it
as
a
directory
or
is
there
some
other
way,
fancy
get
provided
way
to
do
it.
C
A
No,
no
you're!
All
right,
I
was
just
asking
the
group.
I
talked
to
matt
fenwick,
the
owner
of
psyclonus,
and
he
gave
us
to
go
ahead
to
import
his
repo
into
signet
or
policy
api.
I
just
don't
know
the
best
way
to
do
that.
Do
I
literally
just
bring
in
his
repo
as
a
new
directory
and
signature
policy
api,
or
is
there
some
fancier
way
to
nest
a
repo
in
another
repo?
I
know
there's
a
way
to
like
do
a
simulink,
but
I
don't
think
that's
what
I
want
to
do.
A
A
A
No,
we
would
have
to,
I
think
the
general
gist
would
be
to
deprecate
his
repo,
his
personal
repo
and
just
track
it
all
upstream,
rather
than
have
a
fork,
I
mean
if
he
wants
to
maintain
a
private
fork,
he's
more
than
welcome,
because
it
is
his,
but
I
think
he
was
all
right
with
with
maintaining
it
fully
upstream.
So
so,
in
that
sense,
we
wouldn't
have
like
a
simulink
to
his
repo
it
would,
it
would
fully
be
tracked
in
our
upstream
repo.
B
A
B
A
Do
it
like
that
cool?
Well,
I've
been
trying
to
find
time
to
do
this.
It's
been
a
slow
process
been
pretty
busy.
So
it's
on
the
list.
Otherwise,
before
you
got
here
absheck
we
were
just
talking
about
there's
some
small
things
we
want
to
do
to
up
to
cmp.
But
besides
that,
we
just
want
to
poke
sig
network
to
get
some
reviews
before
next
thursday,
which
is
the
next
sig
network
meeting.
A
Yeah
we
actually
have
an
old
a
whole
suite
of
older,
oh
conformance
tests.
I
know
we
have
e2e
tests,
obviously
conformance
tests.
I
would
have
to
go
check,
but
I
don't
think
so
off
the
top
of
my
head
when
you
say
conformance
test
for
network
policy.
Do
you
mean
like
like
how
would
that
work
right?
Because
network
policy
isn't
implemented
in
core,
so.
D
Validation,
I
I
think
I
guess
it
would
be
attempting
to
validate
some
base
expected
behaviors.
I
I
mean
it's
a
little
bit
of
potentially
uncharted
territory,
but
this
is
something
that
I
guess
we've
been
talking
about,
even
in
cluster
network
policy.
It's
just
like
if
we
want
to
say
that
a
cni
is
quote
properly
implementing
network
policy
or
cluster
network
policy
it.
You
know
it
makes
sense
to
have
a
suite
of
tests
that
they
have
to
pass
of
sort
of.
You
know
if
I
deploy
this
pod
and
deploy
this
yaml.
D
E
D
Hand
in
hand
with
the
tests-
I
guess
there's
I
guess,
there's
no
like
enforcement
mechanism,
but
I
guess
there
would
be
some
way
of
being
able
to
say
so
and
so
cni's
are
passing
our
conformance
tests
right
having
like
a
dashboard
or
something
and
saying
oh,
hey
so
and
so
cnn.
Maybe
you
should
go
see
why
your
latest
release
is
failing
or
something
like
that.
A
So
I
think
cyclonus
that
was
one
of
the
use
cases
for
cyclonus.
So
if
you
look
at
the
repo
I
had
posted
in
the
chat
there
actually
is
a
few
cni's
running
cyclonus
like
in
the
vein
of
of
conformance
tests
posted
that
there
I
think,
that's
the
right
link,
so
that
might
be
a
good
way
to
maybe
look
at
running
those
upstream,
I'm
not
really
sure
I'd
have
to
look
at
it.
It's
a
good
point,
though,.
A
D
A
But
they
are
running
like
psyllium
is
running
this.
It
looks
like
so
I
I
might
go
look
at
how
it's
implemented
in
psyllium
ci,
and
that
would
help
me
understand
a
little
bit
more.
I
could
also
have
matt
come
here
and
and
give
a
quick
demo,
because
we
do
have
a
lot
of
newer
people,
so
he
would
I'm
sure,
do
that.
D
Yeah,
I
guess
I'm
a
little
bit
fuzzy
on
what
it
means
to
be
a
running
cyclonus.
As
a
cnn,
like
my,
I
recall
a
demo
that
I
think
matt
gave
a
while
back
which
it
seemed
more
like
from
the
perspective
of
an
application
developer
where
it
was
like
these
are
the
animals
that
I
have
you
know.
What's
what's
the
expected
behavior
between
these
two
pods,
that
that
seemed
to
be
what
cyclonus
was
doing
is?
Is
there
something
else?
That's
I
guess
more
helpful
for
cnn.
I
agree
last
time
at
ransom.
F
A
A
A
I'm
thinking
we
might
want
to
look
at
splitting
this
meeting
up
into
bi-weekly
as
well
just
kind
of
following
the
vein
of
what
sig
network
does.
Does
anyone
have
a
problem
with
that
or
or
think
it's
a
good
thing
or
not?
I
just
I've
felt
recently,
like
we've
all
been
busy
with
other
things
and
haven't
really
been
moving
stuff
along
as
quickly
as
possible.
So
I
don't
want
to
have
an
unnecessarily
unnecessary
meeting.
A
A
A
Awesome:
okay!
Well,
if
there's
nothing
else
folks,
I
really
appreciate
your
time
today
and
we'll
get
some
time
back.
I
will
reach
out
to
casey
davenport
and
look
at
bumping
this
through
every
other
week.
Should
we
follow
this
run
on
the
same
weeks
as
sig
network,
or
should
we
run
on
off
kilter
weeks?
What
would
work
better
for
all
of
you.