►
From YouTube: Kubernetes SIG Network Bi-Weekly for 20201111
Description
Kubernetes SIG Network Bi-Weekly for 20201111
A
B
Oh,
I
do
have
regular
business
for
the
srov
network
operator
proposal
as
a
project.
I
did
sync
with
zheng
he
and
punk,
and
the
the
blocker
here
was
to
vote
on.
This
was
what's
the
plan
for
separating
out
the
openshift
bias
that
it
currently
has
with
the
need
for
the
upstream
compatibility
with
the
vanilla
kubernetes,
and
they
have
assured
me
that
the
that
there
is
functionality
that
does
currently
work
with
vanilla
kubernetes.
B
So
I
think
that
that's
a
very
well
technical
known,
so
I
would
propose
that
we
go
ahead
and
vote
on
accepting
the
srov
network
operator
as
part
of
the
network
plumbing
working
group.
So
I
guess
I
would
ask
if
there
is
anyone
who
has
any
concerns
that
would
cause
them
to
vote
no,
and
we
can
discuss
those.
B
C
So
I've
been
attending
regularly
the
network
kubernetes
network
and
resource
management
meeting.
It
is
basically
the
srv
device
plug-in
cni
meeting
we've
there's
a
couple
of
the
projects
like
the
operator
and
then
there's
some
of
the
ones
smaller
ones
like
the
user,
space,
cni
and
appnet
that
I
kind
of
poke
out
a
little
bit
here
and
there.
So
this
was
more
of
just
a
reminder
to
the
group
that
we
have
meetings
outside
of
this
meeting.
B
Hey
billy,
that
being
said,
something
that
I
I
still
have
a
to
do
that
I
need
to
make
some
pull
requests
against
the
community
repo
for
membership
and
all
of
that
good
stuff,
so
I'm
behind
there,
but
something
that
we
had
put
into
the
governing
stock
was
a
like
suggestion,
saying
you
know:
if
we
have
external
meetings,
we
should
give
the
connection
info
and
stuff
like
that.
How
about
having
those
as
part
of
the
community
repo?
B
Does
anyone
that's
what
would
be
my
suggestion
or
I'd
happy
happy
to
take
other
people's
suggestion,
and
then
I
guess
my
follow-up
is:
is
it
cool?
If
I
reach
out
to
you,
of
course,
maybe
the
you
have
all
the
info
right
here
in
the
agenda.
So,
okay,
I
don't
need
to
reach
out
to
you.
No
well
one,
of
course.
C
C
Yes,
and
I
guess
along
those
same
lines,
I
do
believe-
and
I'm
I'm
stretching-
I
don't
have
any
of
this
in
front
of
me
that
part
of
the
you
know
the
when
we
approved
all
the
legal
stuff
on
how
we're
going
to
run
network
plumbing
working
group
was
that
if
you
have
the
outside
meetings
to
report
back
in
like
what's
going
on,
is
it
enough
to
have
this
agenda
document
where
we
have
that
type
of
information,
or
is
there
more
of
a
formal
process
of
reporting
back
to
this
meeting
on?
What's
going
on?
B
C
C
B
B
I
did
put
a
mail
out
to
the
list,
but
we're
gonna
cancel
the
next
session,
which
would
be
on
tuesday
next
week,
due
to
thanksgiving
and
tomo
will
not
be
able
to
make
it
so
and
he's
been
kind
of
leading
that
discussion
about
what
we'll
cancel
that
one
next
week.
So
the
next
one
will
be
on
december,
the
8th
at
10
30
a.m.
If
you
there's
information
for
it
in
the
mailing
list
or
if
you
have
any
other
questions,
feel
free
to
reach
out
to
me.
A
However
long
cni
has
really
been
around
and
so
we're
trying
to
roll
a
lot
of
that
up
into
some
of
those
discussions
very
early
stages.
I
know
casey
calendrello
has
some
ideas.
I
don't
actually
know
all
of
what
those
are,
but
he's
kind
of
putting
together
some
stuff
going
to
start
some
discussions
with
other
stakeholders
as
well
in
the
cube
and
other
communities
around.
What
should
that
look
like?
I
suspect
it's
going
to
be
less
exec
based
and
probably
more
some
kind
of.
A
You
know
rpc
or
something
like
that.
We've
done
some
grpc
pocs
for
cni
before,
but
it's
going
to
be,
those
discussions
will
be
starting,
probably
in
earnest
or
very
early
next
year.
I
don't
think
that
there
will
be
anything
immediately
coming
out
of
those,
but
since
so
much
of
this
group's
work
is
with
cni
and
a
lot
of
the
reference
software
that
we
do
is
heavily
involved
with
cni.
B
Cool
that's
awesome.
I
am
really
also
happy
to
see
that
this
note
that
it
has
some
similarities
to
people
talking
about
a
quote:
unquote:
networking
api
for
kubernetes,
because
that
is
sort
of
a
hot
topic
and
at
least
from
my
standpoint,
it's
nice
to
see
the
cni
maintainers
talking
about
it,
because
we
do
have
a
standard
that
we
work
with
today.
So
this
is
awesome.
I
will
definitely
be
passing
this
along
to
tomo,
who
will
probably
read
the
agenda
before
I
can
talk
to
him
but
cool
thanks
again.