►
From YouTube: Network Plumbing WG Meeting 2018-03-29
Description
Kubernetes Network Plumbing Working Group meeting 2018-03-29
A
A
Let's
see,
Doug's
not
around
for
the
spec
updates,
but
as
requested
last
time
he
did
update
the
spec
for
with
sections
and
multiple
attachments,
as
well
as
the
default
network
part.
So
if
anybody
wants
to
go
review,
those
sections
and
comments
that
would
be
good,
I
took
a
look
at
them
and
reworded
them
slightly
and
I.
Think
Doug
did
a
pretty
good
job
to
start
with
those,
but
obviously,
if
we
can
tighten
up
some
of
the
wording,
that
would
be
good.
A
A
A
B
So,
regarding
the
about
the
IP
requests,
I
think
so
the
IP
address
is
managed
by
the
IPAM
CNI
Praveen,
and
then
some
of
them
is
not
the
cannot
set
the
IP
address
so
I'm.
Just
imagine
that
we
set
the
IP
request,
prestige,
CB
or
something
like
that.
At
that
time
we
it's
hard
to
identify
the
failure
route,
calls
or
something
like
that.
So
they
especially
the
from
CNI
specification
point
Oh
bill
D.
B
There
is
no
IP
field
which
will
be
effective
for
all
items,
CNI
that
there
is
nothing
like
that,
so
there
I'm
just
thinking
this
the
I.
We
should
not.
The
IP
request
failed
in
the
meta
prep,
this
multiple
network
interface,
meta
proggy,
and
then
these
will
be
done
in
the
item.
Cni
configuration
site.
Of
course
this
will
be
inside
the
multiple
network
made
a
problem
as
the
part
of
other
stuff.
B
That's
the
one
comment
and
there,
on
the
other
side,
the
Mac
request
is
so
currently
the
CNI
probably
is
going
to
support
the
meta
problem
which
the
some
adding
the
functionality
inside
the
CNI
workflow,
such
as
port
map,
or
something
like
that
so
dia.
We
we
could
at
changing
the
IP
request,
as
the
ADIZ
meta
probably
notice
that
the
this
meta
problem.
That's
that
my
idea,
yeah.
A
The
only
issue
there
is,
if
it's
a
generic
change,
the
MAC
address
of
the
interface
plug-in,
we
weren't
quite
sure
if
there
were
some
problems.
That
would
happen
if,
like
the
IP
address
was
assigned
and
everything
else
if
there
were
problems,
would
happen
after
that,
when
the
MAC
address
was
changed,
I
see.
B
A
B
I'm
I
was
I
agree
with
the
about
the
at
for
some
cases.
For
example,
some
Sdn
cases
which
uses
the
same
open,
be
switching
or
something
like
that.
At
that
time,
the
Assam
Sdn
would
like
to
specify
their
MAC
address,
as
well
as
the
attaching
the
floor.
So
at
that
time,
dia
we
we
couldn't
do
that,
so
they
are
from
so
the
yeah.
Maybe
the
D
in
this
case
well
yeah,
it's
very
hard
to
identify
yeah
I,
agree,
yeah.
A
You
might
just
have
to
not
set
a
specific
MAC
address
for
configurations
that
you
know
wouldn't
be
able
to
work
with
it.
So
I
mean,
for
example,
DHCP.
The
server
might
identify
the
client
via
the
MAC
address,
and
so,
if
you
run
DHCP
first
and
then
change
the
MAC
address
later
renews
may
not
work
properly,
but
you
might
just
we
might
just
have
to
say.
Well,
if
you
want
to
do
this,
don't
do
it
yeah.
B
A
And
there
was
also
the
question
of
capabilities
from
last
time,
and
I
did
bring
that
up
in
CNI
meeting
as
well,
and
there
was
general
agreement
that,
yes,
we
should
add
some
de-facto
capabilities
for
or
for
mac.
Address.
Requests
like
there
already
are
for
IP
addresses
and
then
specify
capability
bits
for
the
plugins.
So
what
would
happen
there
would
be
if
you
know
that
your
plug-in
does
allow
any
of
these,
then
it
in
the
configuration
the
CNI
config,
whether
that's
in
the
network
definition
itself
or
in
a
file
on
disk,
would
set
that
capability.
B
A
That's
probably
good
we
had
in
CNI
meeting.
We
had
talked
about
adding
these
to
the
spec,
but
then,
of
course,
it
would
require
plugins
to
actually
be
updated
to
honor
them
and
yeah
kubernetes
does
lag
a
little
bit
behind
the
CNI
reference
plugins,
and
so
it
would
be
a
little
bit
before
it
would
be
able
to
be
used
all
the
way
through.
But
maybe
we
should
keep
the
sections
in
the
spec
and
update
the
cni
stuff,
and
then
you
know,
I
mean
any
of
the
other.
Plugins
could
work
with
them.
A
I,
don't
think
it
would
be
too
much
effort
to
add
the
support
to
the
various
plugins
miss
long
as
the
capability
bit
is
there.
The
runtime
would
check
for
the
capability
and
the
config
and
then
if
the
capability
was
not
present
and
there
was
an
IP
or
Mac
request,
then
it
would
error
that
network
out
so
I
feel
like
it
would
be
pretty
easy
to
figure
out
when
an
error
happened.
As
long
as
the
meta
plug-in
did
the
right
thing
with
the
capabilities.
A
All
right
other
than
that
there
wasn't
much
else
in
the
agenda
for
this
week.
I
expect
it
will
probably
have
a
lot
to
talk
about
in
45
minutes
if
people
want
to
hang
around
otherwise
so
probably
more
stuff.
In
two
weeks,
once
more
people
have
had
time
to
look
at
the
spec
and
come
back
from
the
face-to-face,
so
were
there
any
other
bits
or
agenda
items
that
anybody
anything
else
people
want
to
bring
up.