►
From YouTube: Network Policy API Bi-Weekly Meeting for 20211025
Description
Network Policy API Bi-Weekly Meeting for 20211025
A
Awesome
hello:
everyone
today
is
october
25th
2021,
coming
up
on
halloween.
This
is
a
meeting
of
the
sig
network
policy,
api
sub
group
to
sig
network.
It
is
a
cncf
certified
meeting,
so
let's
please
be
nice
to
each
other.
You
are
being
recorded
and
yeah.
Let's
have
a
good
day
today,
so
not
much
on
the
agenda.
I'll
share
the
agenda.
A
I
see
there
are
two
folks
who
I
don't
recognize
here
so
do
either
of
you
all
want
to
kind
of
give
a
little
intro
while
you're
here
what
you're
interested
about
network
policy
etc.
No
pressure.
B
I'll
start,
my
name
is
mark.
I
work
at
google,
along
with
satish,
I'm
going
to
be
working
on
a
network
policy
project
with
him
in
this
upcoming
quarter.
C
Hi
everyone
hi,
my
name,
is
sugang.
I
also
come
from
google
kubernetes
engine
and
I
work
with
mark.
We
are
in
the
same
team,
and
I've
been
here
once
maybe
a
couple
weeks
ago.
A
Oh
yep,
right
sorry
about
that
great
awesome.
Well,
thanks
y'all
for
hopping
in,
I
think
for
today
the
agenda's
pretty
open
one
is
some
of
we
can
give
a
little
backstory
and
feel
free
to
ask
any
questions
right
now,
one
of
the
big
major
initiatives
that
I've
been
part
of
with
abhishek
and
sanjeev
and
a
few
others
has
been
and
satish
has
been
cluster
network
policy.
A
So
that's
been
taking
up
most
of
my
time,
but
we
have
another
few
initiatives
in
the
pipeline,
such
as
network
policy
status,
which
I
think
we
need
to
figure
out
to
help
vinay
also
from
google,
with
setting
up
service,
selectors
and
different
types
of
extensions
to
network
policy.
A
A
I'm
gonna
take
that
as
a
no
do
you
know
what
you're
going
to
be
working
on
with
satish
at
this
point,
is
it
going
to
be
network
policy
v2,
or
are
you
both
focusing
on
the
expansion
of
selectors.
C
D
Hey
andrew,
so
I
wanted
to
get
more
people
involved
in
our
group
because
we're
trying
to
push
through
a
couple
of
kept,
so
sudan
is
going
to
be
involved
in
some
of
these
efforts.
A
Yeah
no
worries
they'd.
Mark
insurance
gave
a
brief
intro,
which
I
appreciate
and
yeah
I'm
excited
to
have
more
people
here.
We
need
help.
We
need
people
to
keep
pushing.
I
was
just
saying
today:
we
don't
really
have
anything
on
the
agenda
unless
you
have
anything
to
add
vinay.
I
was
just
kind
of
giving
an
overview
of
what's
going
on
yeah.
D
So,
as
I
told
you
right
now,
last
week
had
taken,
we
had
a
thursday
friday
off,
so
I
didn't.
I
was
planning
to
convert
those
dots
like,
as
we
talked
in
the
last
meeting,
into
board
docs
and
get
some
consensus
yep
the
user
story,
so
the
first
step
is
to
make
them
a
publicly
readable
and
commentable
document
and
anyone
who
wants
to
join
and
feel
we
have
a
draft
version.
D
So
please
add
your
name
to
the
document
of
the
place
where
we
dissolve
major
items
and
then
we
can
start
the
cap
and
start
resolving
the
rest
of
the
comments
on
the
github.
A
Sounds
good
yeah
whenever
you
ge,
I
had
already
given
it
an
initial
look
for
nay,
but
whenever
you
get
a
chance
to
give
it
a
poke,
feel
free
to
poke
us
in
the
channel.
Just
so
I
see
it
and
know
to
go
back
again.
A
We
had
the
same
thing
we
were
off
on
friday,
so
I
I'm
kind
of
catching
up
behind
you
great
yeah.
The
other
main
thing
that
I
really
still
I
know,
you've
kind
of
been
a
part
of
we've
talked
about
it
now.
A
couple
times
is
the
status,
the
ongoing
work
with
status.
So
that
would
be,
I
think,
a
good
one
for
someone
newer
to
hop
in
on
and
start
helping
out
with.
A
D
A
Right
exactly
and
I
think
what
if
we
could
answer
some
of
the
questions
that
are
laid
out
on
that
cap
it'd
be
easier
for
us
to
look
at
expanding
selectors
for
network
policy
and
also
expand
selectors
for
cluster
network
policy
in
the
future,
so
it's
kind
of
like
future
proofing,
the
design
of
the
api,
especially
if
we
can
figure
out
how
to
lump.
A
I
don't
want
to
say
versioning
how
to
lump
feature
support
into
the
status
so
yeah
that's
just
kind
of
a
brief
overview
of
what
we're
doing
for
the
newer
folks.
We
also
have
a
repo
that
has
not
been
being
used
very
much
sig
network
policy,
api.
A
Let
me
get
the
link
and
I
would
love
to
I'm
super
open
anyone
who
wants
some
of
their
first
upstream
contributions
if
they
want
to
add
documents,
if
they
want
to
add
you
know,
have
good
ideas
of
what
information
we
can
put
there,
I'm
open
to
anything
having
to
do
with
network
policy
considering
putting
cyclonus
there,
which
is
a
cool
tool.
A
Let
me
link
kind
of
around
network
policy
from
matt,
femwick
and
engineer
over.
I
think
at
vmware,
so
yeah
just
kind
of
opening
up
the
floor
there
for
the
newer
folks.
E
A
Think
it
needs
someone
owning
it
and
driving
it.
Prasada
nadim
from
juniper
at
first
had
some
really
good
ideas.
A
Cmp
got
stuck
for
a
while
they
kind
of
stopped
to
wait
on
cmp,
and
I
haven't
heard
from
them
since
so
there
is
no
one.
Currently,
I
think,
we're
driving
that.
So
I
can't
even
give
a
time
to
completion.
E
A
I
see
security
or
native
kubernetes
security,
really
falling
with
network
policy
really
falling
into
the
limelight
in
the
next
year
or
two.
So
from
our
side,
like
I
said
I,
I
was
we're.
E
A
And
in
the
past,
we've
had
a
bunch
of
good
ideas.
You
know
we
have
people
come
in
kind
of
start
it
and
then
it
it
it
trails
off
and
that's
what
kind
of
keeps
happening.
That
was
a
reason
we
made
the
signature
policy
api
repo
to
kind
of
preserve
any
work
that
gets
done.
So
that's
where
we're
at
all
right,
but
I'd
say
my
main
focus
right
now
in
my
in
my
upstream
contribution
time
is
still
on
cmp,
and
so
we've
just
been
updating
the
kept
for
that
trying
to
get
it
pushed
forward.
A
Yeah,
that
was
just
it's
actually
a
pull
against
the
same
old
cap
that
sanjeev
had
put
up.
So
we've
just
been
collaborating
on
the
kept
by
opening
up
vrs
against
abhishek's
branch.
It's
a
little
bit
easier,
but
I
think
we're
pretty
much
moved
towards
conclusion
there,
hopefully
in
the
next
week
or
two,
none
of
the
cmp
folks
are
here
today
so
yeah.
A
Out
or
for
now
the
priorities
you
know
were
true,
I
think
we've
agreed
on
keeping
it
simple.
You
can't
have
to
so
priority.
Conflict
resolution
is,
is
essentially
you
can't
yeah.
You
can't
have
two
priorities
or
two
cmp
instances.
A
Cool,
hey
satish.
I
saw
you
just
hopped
on
dude.
I
posted
this
pr.
Sanjeev
put
up
the
other
day
for
the
enhancement
on
cmp
kept
feel
free
to
give
that
a
review.
If
you
want,
I
already
did,
but
it's
not
too
big.
F
Sure,
thanks
andrew
I'll,
take
a
look
at
that.
So
is
there
a
is
the
link
published
in
the
notes.
F
So
we've
actually
sanjeev
rahul
and
me
actually
caught
up
last
week
and
we
have
reached
a
common
agreement
on
like
having
multiple
applies
to.
So
I
think
that's
already
this
also
yeah
there's
nothing
of
nothing.
A
Cool
so
we'll
just
keep
working
on
cmp
abhishek
and
sanji
aren't
here
today,
but
I
know
their
abstract
was
on
vacation
last
week,
so
I
know
they're
actively
going
to
be
back
on
it
this
week.
A
Okay,
are
there
any
other
questions
for
today,
if
not
we're
all
going
to
get
a
bunch
of
time
back
all
right
sounds
good.
Yeah,
awesome,
okay!
Well,
hey
thanks!
Everybody!
Please!
Let
me
know
vinay
satish.
If
there's
anything
we
need
help
on
and
if
anyone
has
ideas
for
how
we
can
spice
up
the
network
policy
api
repo,
please
let
me
know
that'd
be
a
really
great
way
to
get
involved
or
if
you
have
an
intern
or
something
that'd
be
a
great
place
for
them
to
start.
A
So
that's
all.
I
have
thanks
everyone
so
much
for
a
good
meeting
today
and
we
will
sync
up
next
week.
Take
care
bye,
take
care,
bye,.