►
From YouTube: Kubernetes SIG Network Bi-Weekly meeting for 20201217
Description
Kubernetes SIG Network Bi-Weekly meeting for 20201217
A
B
B
B
B
A
B
Awesome-
and
I
believe
that
concludes
our
regular
business.
I've
got
one
item
on
the
agenda.
I'm
a
little
disappointed
that
we
don't
have
martin
kennelly
from
intel
today.
I
know
this
time
of
year
is
sometimes
difficult
to
get
everyone
together,
but
during
the
multis
maintainers
meeting
last
week,
tomo
martin
and
I
had
a
pretty
good
conversation
about
service
abstraction
and
one.
B
Another
thing
is,
I
believe
you
know
I,
I
guess
one
kind
of
the
state
of
affairs
here.
As
far
as
I
understand
it
is
that
tomo's
previous
prototype
was
using
endpoint
controller,
but
we've
moved
on
to
end
point
slices,
and
so
that's
kind
of
the
next
detent
point
in
this
proof
of
concept
is
to
get
employees.
D
Yeah
so
so
the
previously
I
did
the
plc.
At
that
time
I
modified
the
upstream
kubernetes
code
to
modifying
the
endpoint
to
adding
the
modus
interface
ip
address
so
and
then
the
and
then
now
I'm
also
the
prototyping
or
the
next
version.
I
mean
that
they
are
separate
from
the
kubernetes
upstream
implementing
the
endpoint
controller
and
then
this-
and
this
is
the
actually
the
endpoint
controller
and
then
now
the
upstream
design
is
moved
to
use
endpoint
slice
instead
of
the
end
points.
D
D
So
at
that
time
the
we
need
the
sound
component
which
manipulate
ib
tables
to
implementing
service
abstraction,
so
that
this
is
the
pretty
missing
stuff
and
then
I'm
I
have
the
planning
and
the
architecture
stuff.
So
but
today
I
don't
have
the
time
yet
so
the
that
is
the
my
to
do,
but
before
that
now
I'm
working
on
the
modes
network
policy
stuff
so
that
so
the
the
service
abstraction
priority
is
next
of
the
network
policy.
That's
the
what
we
talked
about
in
the
motors
maintenance.
B
B
A
A
D
F
C
F
F
A
Here
for
the
future
was
that
we
could
try
to
get
labels
on
each
ip
address
in
pod
status,
pod,
ips
and
that
would
be
conveyed
from
cni
into
the
runtime.
And
then
the
runtime
would
just
send
those
labels
back
up
to
cube,
which
then
posts
the
api
server,
and
so
one
option.
There
was
that
if
each
of
the
ips
had
labels,
you
could,
for
example,
set
the
label
to
be
like
the
network,
attachment
definition
name
or
something
like
that,
and
then
you
could
have
services
that
had
a
pod
ip
selector
and
that
service
would
say.
F
Yes,
just
to
be
sure
that
that
would
mean
that
cni
would
have
to
contain
something
like
how
we
have
what
we
call
pod
agent,
like
that
actively
listen
on
what
happens,
because
a
new
prefix
can
be
for
added
to
a
network
at
any
point.
Yes,
so
the
network
assignment
or
address,
address
change
assignment
exchange
could
happen
at
any
time.
During
the
pod's
lifetime,
which
then
sort
of
I
mean
we
decided
in
columbus
that
the
address
assignment
has
to
be
taken
out
of
the
immutable
part
that
they
are
mutable.
A
This
would
be
one
way
to
maybe
do
it
in
a
cube
native
sort
of
way
that
might
even
allow
us
to
do
it
in
the
normal
kubernetes
endpoints
controller,
as
opposed
to
having
to
write
a
bunch
of
other
code
to
do
it
too,
but
you're
very
right.
That
we'd
need
to
add
some
kind
of.
I
mean
at
least
for
v6
dynamism
to
the
network,
plug-in
or.
F
Doing
some
slides
and
that
I
showed
with
class
r
when
I
have
discussions
with
them,
they're
not
ready,
but
I
should
be
able
to
they're
not
sort
of
completely
detail
and
talk
about
cni's
more
like
how
do
we
deal
with
the
orchestration
and
so
what
are
the
needs
for
vrfs?
And
how
do
we
handle
that?
I
should
be
able
to
go
actually
present
them
in
this
forum
sometime
in
towards
the
end
of
january,
if
you're
interested
yes,.
A
F
Also
looked
at
sort
of
different
ways
if
you
start
using
vrfs
in
a
container
or
inside
the
pod,
what
are
the
alternatives,
and
so
how
are
the
different
ways
of
doing
this
and
one
way,
and
actually
it's
the
one?
I
don't
really
like-
requires
change
to
the
cubelet,
but
there
are
other
ways
to
sort
of
have
some
sort
of
call
it
a
trampoline
that
starts
different
containers
for
in
different
having
different
default,
vrfs
and
sort
of
some
scheme
to
have
eth0
being
able
to
use
a
normal
loopback.
F
A
A
I
mean
I,
I
think
we
do
have
ways
to
go
to
get
things
to
be
more
dynamic
and
you
know,
like
I
said,
there's
a
lot
of
there's
work
going
on
in
a
couple
of
areas
to
make
that
happen.
I
think
you
know
it's
encouraging,
because
you
know
we
kind
of
had
a
lull
in
that
work
for
a
while,
but
you
know,
I
think,
we're
at
the
point
where
that
stuff's
getting
pushed
forward.
A
F
Is
that
the
problems
that
multi-homing
brings
it
looks
easy,
but
it's
not
and
sort
of
just
to
step
in
there.
If
we,
if
we're
really
going
to
push
for
it,
it's
better
to
sort
of
be
honest
and
say
try
to
avoid
if
you
can
and
sort
of
have
the
tools
ready.
So
so
we
don't
get
this
that
oh,
these
things
are
available
and
then
people
start
pushing
out
containers
or
pods
that
just
work
in
one
system.
F
A
F
Change
name
on
it,
some
at
some
point
change,
name
of
it
right
to
I
don't
know:
what's
happened,
something
more
with
the
overall
networking
and
I
like
what
you've
done.
I
mean
I,
I
look
at
ovn
and
sort
of
to
to
not
have
to
work
with
the
cubelet
and
with
the
cube
proxy
anymore,
a
relief
at
the
same
time,
if
everyone
is
going
to
do
their
own
control
component
for
kubernetes,
that's
not
good
either.
Then
we're
going
to
get
such
wide
divergence,
depending
on
which
network
you're
running
inside.