►
From YouTube: Network Policy API Bi-Weekly Meeting for 20211206
Description
Network Policy API Bi-Weekly Meeting for 20211206
A
B
A
A
So
that's
kind
of
the
first
thing
next
thing
is
cmp.
We
are
pushing
to
kind
of
get
another
review
this
thursday
in
the
upstream
meeting,
I
believe-
and
hopefully
after
that
we'll
either
get
a
blessing
or
a
strike
down
to
keep
moving
forward
and
actually
get
that
kept
or
the
first
draft
of
it
merged
and
start
working
on
the
alpha
version
of
that
api
implementation.
Wise,
that's
what
I
basically
had
for
the
group
is
there
anything
else
you
all
would
like
to
discuss
while
we're
here.
C
A
B
B
You
know
like
fine
comb
that
and
then,
like
probably
like
detail
out
all
the
other
details
once
we
have
that,
I
think
we're
going
to
we're
going
to
present
it.
Probably
one
of
these
meetings
right,
okay,
but
I
mean
so
that's
that's
that's
where
we
are
at
for
fqdn
policy
right,
I
mean,
but
there
isn't
much
progress
on
service
icon
selector,
as
of
now,
okay,
probably
like,
if
any
other
community
member
wants
to
take
it
up
stab
at
it.
I
think
that's
also
works
for
us.
A
That
would
be
awesome.
I'm
gonna
make
a
little
spot
in
our
agenda
for
open
action
items
that
people
could
check
out
or
I'll
make
them
as
issues
and
signature
policy
api.
As
like
good,
first
issues,
do
you
think
this
fqdn
document
is
ready
for
some?
Would
you
like
some
external
review
like?
Would
you
like
me
to
check
it
out
or
anyone
else
who
comes
by.
B
B
A
A
Awesome
yeah
I'll
give
that
a
look
then
before
our
next
meeting
in
two
weeks
I
just
was
trying
not
to
review
it
until
you
all
had
taken
a
stab
at
updating,
but
because
you
have
updated,
that's
awesome,
sweet
and
I
put
that
in
the
agenda.
So
if
anyone
comes
by
and
wants
to
check
it
out,
they
can
do
so
cool
thanks
for
working
on
that.
I
think
there's
a
lot
of
people
who
also
would
like
to
see
that
something
like
that
upstream.
A
So
I'm
interested
to
see
what
you
came
up
with
yeah
and
if
you
want
to
give
it
a
presentation.
Just
add
yourself
to
the
agenda.
Feel
free
we've
been
really
open
lately,
probably
due
to
it
being
the
end
of
the
year
and
people
trying
to
cram
everything
in.
But
I
don't
want
this
meeting
to
die
out.
I
know
it's
been.
It's
been
tricky
for
me
to
keep
it
going
on
my
own,
so
I'm
always
looking
for
help
and
for
people
to
talk.
B
C
Okay,
well,
I
could
promise,
probably
in
february
like
a
presentation
of
sort
of
my
ideas,
what
I
think
should
go
into
kubernetes
and
how
we
should
treat
policies
and
sort
of
what
we
need
a
new
ipi
towards
these
cni's.
It's
a
sort
of
logical
firewall,
another
how
that
should
work.
I
just
need
to
finish
papers
around
it
once
that
is
done.
I
have
no
problem
sharing
that
these
we
will
start
working
on
it
and
during
I
mean
right
before,
where
we
need
to
get
something
working
and
then
we'll
present
it
and
open
up
the
project.
C
A
A
C
A
C
It
another
fun
discussion
that
needs
to
come
up
on
the
sick.
Networking
soon
has
nothing
really
to
do
with
this,
but
I
mean
multinetworking
has
sort
of
become
the
fact
to
accepted
right
and
now
some
people
say.
Oh,
I
want
to
be
able
to
put
labels
on
the
on
the
endpoint.
It's
like
no
like.
We
need
to
get
the
networks
in
first
yeah.
They
need
to
be
visible
and
that's
part
sort
of
to
to
make
it
just
not
something
hidden
under
annotations.
Not
to
do
that.
That
will
be
a
long
and
interesting
battle.
A
C
Campaign,
you
can
definitely
handle
the
networks
and
so
on,
but
it
needs
to
come
in
first
because
as
long
as
the
cube
proxy
is
there,
no
one
is
going
to
want
to
do
anything
of
these
changes,
even
if
it's
not
adding
functionality
in
the
queue
proxy
just
telling
it
to
not
care
about
things.
No
one
wants
to
do
that
right
and
shouldn't.
C
A
B
C
A
B
Andrew,
so
I
have
one
question
right
I
mean
so
I
haven't
been
to
the
last
sig
network
meeting.
So
so,
where
are
we
at?
Regarding
the
selectors
like
multi,
selectors
extension
right,
I
mean
that
we
were
actually
trying
to
propose.
Is
it
via
some
kind
of
enum
that
we
are
trying
to
introduce
right
and
then
extend
it
to
part
selectors
in
features
like
service
selector
inside
the
second
selector,
and
so
on?.
A
A
Yeah
so
at
this
point
it's
basically
an
enum,
but
we've
defined
a
new
class,
a
new
type
called
workload
selector,
and
it's
not
like
what
we
had
originally
talked
about
to
teach
with
the
hard
coded
possible
enums
for
each
selector.
It's
a
little
abstract
in
the
sense
that
whatever
type
of
workload
selectors
in
here
are
enums
they're,
actually
just
supported
selectors,
so
pod
selector
is
the
only
one
currently
and
in
the
future.
B
A
A
Yeah,
so
we
did
make
a
note
of
that.
It
will
be
interesting
to
see.
I
think
what
sig
network
says
to
this
sort
of
a
proposition,
because
it's
a
little
different
from
anything.
That's
been
brought
up
before,
so
it
should
give
us
the
energy,
hopefully
it'll,
quickly
tell
us
whether
they
think
this
is
crazy
or
not,
but
it
seems
to
me
it
seemed
to
make
the
most
sense
to
us.