►
From YouTube: Network Plumbing WG Meeting 2018-11-08
Description
Kubernetes Network Plumbing Working Group meeting for 2018-11-08
A
All
right
we
are
recording
this
is
the
orc
plumbing
working
group
meeting
for
Thursday
November,
8th
2018,
as
always,
if
you
don't
happen
to
have
the
link
to
the
agenda,
I
will
toss
that
in
chat
function,
I
added
a
whole
bunch
of
other
stuff,
but
other
than
that
it
might
end
up
being
a
not
full.
Our
meeting
today,
which
is
good
all
right,
all
right,
so
fun
Europe
all.
C
Current
meeting
time
is
not
particularly
friendly
to
Asia
timezone,
European
time
zone
or
even
really
Eastern
time
zone
in
particularly
so
I'm
I'm
wondering
if
you
know,
I
I,
don't
see
a
lot
of
people
from
Pacific
time
zone
joining
regularly
anyway.
So
I
was
wondering
if
it
would
make
sense
for
us
to
change
our
time
to
make
it
more
friendly.
For
you
know
some
other
people
maybe
to
join.
C
D
D
Probably,
but
so
to
me,
you
have
the
several
meeting
as
this
notes.
Oh
ok,.
E
A
A
C
A
All
right,
let's
see
what
we
think
all
right
sounds
good.
Thanks
all
right.
Next
topic,
I
basically
gave
up
on
the
kubernetes
community.
Pr
I
just
went
off
and
created
my
own
github
org
for
this
group
and
created
a
repo
for
the
specification
and
dumped
the
specification
in
four
different
formats
into
that
repo,
so
I.
My
intent
here
is
that
that
repo
will
hold
the
official
versions
of
the
specs
will
still
work
on
the
spec.
A
You
know
as
a
Google
Doc
and
then,
whenever
we
get
to
a
point
where
we
actually
want
to
make
an
official
release
of
the
spec
I
guess,
then
we
will
dump
it
into
that
repo.
We
could
also
put
other
things
there.
I
mean
it's
a
non-commercial,
github
repo,
so
I
don't
think
we
can
make
private
repos
or
some
of
that
other
stuff
that
actually
costs
money,
but
we
could
also
host
code
there.
A
So
some
of
the
other
things
I
was
thinking
of
were,
and
unfortunately
Corral
is
not
on
this
call,
because
it's
probably
pretty
late
for
him,
but
perhaps
the
admission
controller
that
does
some
of
the
minimal,
minimal
verification
of
the
configuration
Jason.
That
could
potentially
go
into
that
that
organization
in
a
new
repo
they're,
basically
just
a
place
to
host
some
of
the
components,
specifications
and
bits
that
we
develop
in
this
group.
So
I.
G
A
Yeah
and
I've
sent
out
some
invites
on
that,
just
so
I'm,
not
the
only
person
who
is
responsible
for
that
particular
group.
I.
Think
a
number
of
people
on
this
call
have
gotten
those
invites
to
that
organization.
It's
not
meant
to
be
an
exclusive
github
org,
but
you
know
for
the
moment
we
need
at
least
some
administer
so
we'll
just
kind
of
ride
with
it
as
is
and
see
where
we
get
with
that
and
I
think
that's
about
it.
A
So
if
anybody
wants
to
do
some
PRS
against
that
repo
to
put
that
information
in
that
would
be
good
and
actually
come
to
think
we
should
probably
just
have
a
new
repo
in
that
organization
that
contains
most
of
the
you
know:
kind
of
management
and
administration
documentation,
rather
than
trying
to
stuff
that
into
the
multi
network,
spec
repo
in
that
org.
If
nobody
else
gets
run
in
PR,
I
will
probably
slowly
get
there,
but
that's
about
it
for
that.
A
E
So
let
me
apologize,
I
haven't
had
a
chance
to
do
very
much
on
that
I
have
actually.
There
was
some
feedback
about
tidying
up
afterwards.
Please
I
wrote
some
code
for
that:
I
tested
it,
it
didn't
work
and
then
I
got
dragged
on
to
another
project.
Okay
right,
so
let
me,
let
me
say:
okay
I'll
get
something
that
is
ready
for
review
within
the
next
two
weeks.
So
for
the
time
we
have
the
next
meeting,
so
I'll
fight
my
way
out
from
what
the
other
things
I'm
doing.
I
just
get
my
thanks.
E
A
Awesome
things
all
right
and
I
think
you
know
upstream
in
the
cni
maintainer.
His
meetings
were
generally
positive
on
that
we
just
wanted
to
see
some
of
that.
Those
kind
of
small
updates
first
so
I
didn't
want
to
just
kind
of
leave
that
plugin
in
limbo
I
wanted
to
make
sure
that
we
kind
of
kept
moving
that
forward.
So
thanks
for
that
sure
all
right.
F
C
A
You
know
I
think
we
also
needed
some
framework
and
code
to
be
written
for
that
which
that's
gonna
still
work.
Outstanding
I
had
thought
that
maybe
Michel
Cambria
could
help
out
with
some
of
that
I
notified
him
of
this
call
a
little
bit
too
late
for
him
to
join
I.
Think
but
we'll
see
what
he
says
on
that
I
didn't
want
to
say.
You
know
just
kind
of
drop
it
in
his
lap
if
he
had
other
things
to
do
at
that
point.
C
A
A
Nope,
and
here
he
is
devil,
I'll
join
in
just
a
second.
A
The
thing
that
brought
that
back
into
my
mind
was
the
Malta's
interface
request,
interface
thing
and
some
of
the
changes
that
told
me
I'd
done
the
Montes
to
bring
it
more
into
confirm
its
with
the
spec,
and
if
there
was
some
kind
of
nice
framework
that
at
least
verified
some
of
these
things,
then
that's
true.
You
know
that
would
be
good
too,
to
have
to
make
sure
that
implementations
like
multi-sourcing
idea
or
anything
else
that
happens
to
implement
the
spec
would
be
able
to.
You
know,
determine
that
they
actually
conformed
to
it.
Yeah.
A
A
All
right
next
up
was
I
just
kind
of
tossed
this
one
on
I'd
done
a
little
bit
of
thinking
about
it,
and
this
is
one
of
the
items
from
the
v2
considerations
document
and
it's
decided
to
kind
of
toss
out
a
proposal
for
it.
The
issue
is
around
the
kubernetes
runtimes
specific
or
pods
specific
config
options
that
it
has
built-in
support
for
and
those
two
things
are
at
this
point,
the
bandwidth
shaping
annotation
that
you
can
put
on
a
pod
as
well
as
the
port
mappings,
and
what
kubernetes
does
or
the
runtimes
actually
do.
A
Is
they
translate
that
into
some
CNI
runtime
config
and
they
can
get
passed
to
the
network
plug-in?
There
was
a
issue
with
Malta's.
We're
are
not
an
issue
necessarily,
but
a
PR
firm
Altis
that
took
these
options
and
passed
them
to
all
of
the
plugins
for
all
of
the
network.
Attachments
and
I
wasn't
sure
that
that
was
necessarily
correct,
since
you
may
or
may
not
want
the
same
bandwidth
shaping
on
every
single
network
attachment.
A
So
I
decided
to
throw
out
this
proposal
to
say
that
these
options
that
cube
passes
should
be
specific
to
the
default
cluster
Network,
because
that's
kind
of
how
they're
treated
today,
if
you
don't
use
a
CNI
delegating
plugin
like
Malta's,
but
then
recognising
the
need
for
something
like
that,
potentially
for
the
secondary
side
card
networks
and
additional
attachments.
Perhaps
who
should
add
some
support
for
that
to
the
extended
format?
Network
attachment
selection,
annotation,
similar
to
how
we
have
interface,
Mac
and
some
of
the
IP
stuff
as
well.
F
Yeah,
this
makes
sense
to
me
just
one
question:
do
we
want
to
gather
all
this
stuff
under
some
key?
That's
specific
to
you,
know
extensions
or
something
like
that
or
just
have
it
flat.
Inline
like
you
got
yeah.
A
The
we
could
put
it
under
some
other
key.
It
would
mean
a
well
yeah
two
options
there.
We
could
put
all
of
them
under
one
key
since
they're
all
sort
of
things
that
apply
to
a
given
attachment
or
we
could
keep
tossing
them
into
the
the
top-level
annotation
I
think
either
one
is
probably
okay.
Are
you
imagining
right
now
that
there's
a
fixed
set
of
these
well?
Currently,
there
is
at
least
according
to
the
spec
I.
Think
all
of
their
values
are
reserved.
A
F
A
F
A
A
Implementations
that
write
keys
other
than
those
defined
in
the
specification
must
use
reverse
domain
name:
notation,
eg,
org
food
bar
key
Dame,
to
name
non-standard
keys,
so
yeah
it
does
allow
non-standard
keys
in
the
selection,
but
I
I
think
your
point
like
is
well
taken
that
there's
probably
other
things
we
would
add,
and
so
maybe
we
should
put
them
into
a
sub
key
I.
Don't
have
strong
feelings
on
that,
though.
A
F
A
Doesn't
really
matter
whether
it's
a
sub
level,
you
know
underneath
the
mean
or
whether
it's
directly
in
the
top
level.
Basically
the
plugin
would
just
pluck
that
subject
out
of
the
top
level
one
and
pass
it
directly
in
you
mean
flatten
it
into
the
rest
of
the
well
I
mean
what
would
happen
is
if,
in
the
example
that
I
have
listed
in
the
agenda
doc,
for
example,
port
mappings,
you
know
as
a
it
would
be
a
top
level
key,
and
then
it
has
a
map
below
it.
A
That
entire
thing
would
probably
be
translated
to
just
a
string
interface
and
go,
and
then
you
could
just
take
that
entire
key
and
shove
that
into
the
runtime
config
of
the
cni
Jason
that
gets
sent
to
the
plug-in
so
I.
Don't
think
it
would
be
a
big
change
at
all
for
it.
It
could
just
get
lifted
and
shoved
in
without
too
much
difference,
and
if
we
put
it
into
a
sub
key
same
thing,
you
just
go
one
level
down
to
the
sub
key
and
then
pull
out
port
mappings
bandwidth.
Whatever.
F
A
H
G
I
mean
I
like
where
Mike
is
coming
from
that
you
know
if
these
were
ever
growing
and
be
kind
of
nice
to
wrangle
them
up,
but
it's
already
difficult
enough
to
type
in
the
json
annotation
that
I
like
not
having
to
type
in
another
level
of
T,
so
I
kind
of
like
that
part
of
it
so
yeah,
I'm,
okay,
to
have
it
written
up.
Thank
you.
Dan.
G
Yeah
this
was
just
a
quick
one
to
say:
whoever
is
going
to
puke
on.
We
should
try
to
meet
up
I
believe
we'll
have
one
more
meeting.
Hopefully
tell
me
our
next
meeting
is
on
Thanksgiving.
G
A
Actually,
we
we
should
have
one
the
week
before
cube,
come
okay,
we'll
have
one
the
week
before
cubic
on
awesome.
Alright,
the
next
meeting
would
usually
be
in
the
22nd,
but
that's
a
national
holiday
for
the
US
for
anybody
who's
not
from
the
US
on
this
call,
and
then
the
meeting
after
that
would
be
the
6th
and
then
that,
following
weekend
and
the
week
after,
that
is
cube,
gun
all
right.
So.
A
The
week
before
coop
con
get
canceled
for
the
sake
of
people,
traveling
yeah,
that's
true,
I
mean
I
think
we
should
probably
hold
one
on
the
6th
anyway
for
anybody
you
can
make
it
not
have
heavy
agenda
topics,
but
it
just
at
least
some
quick
coordination
and
mm-hmm
solidification
for
anybody.
Who's
going
to
keep
Khan
alright
to
wrap
up
topics
right.
G
Try
to
think
about
this
a
bit,
and
you
know
we
can
try
to
find
a
spot
because
it
would
be
really
nice
if
nothing
else
to
be
able
to
shake
some
hands
and
say
thanks
to
everyone
for
all
the
work
that
they've
put
in
on
this
over
the
last
year,
but
it'd
be
kind
of
nice.
If
we
can,
we
could
go
over
v2
considerations,
again
kind
of
look
at
like
you
know
some
ballpark
roadmap
and
stuff,
like
that.
I
think
it
would
be
really
great
yeah.
A
F
Wednesday
is
the
conference.
You
know
confab
I
mean
in
the
evening
I
mean
I.
You
try
running,
try
something
during
the
day
during
this,
the
yes
sessions
time,
yeah,
probably
Wow.
Okay
I
have
examined
the
sessions
in
detail.
Someone's
gonna
have
to
put
up
a
doodle
poll
or
something
to
find
a
time
that
works,
but
at
least
bad
Doug.