►
From YouTube: Kubernetes SIG Network meeting 20210225
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
A
To
add
your
name
to
the
attendees
list,
which
we
use
as
a
criteria
for
becoming
a
member
maintainer,
is
there
anyone
who
would
like
to
propose
a
candidacy
for
member
maintainer
or
any
new
projects.
A
All
right,
in
that
case,
that's
great.
Let's
move
it
right
on
adrian.
You've
got
the
first
one
about
multi-smooth
network
point
working
group.
B
Yeah,
so
it's
just
you
know,
checkup,
to
see
on
the
state
of
things
like
a
while
back
when
we
started
moving.
All
of
the
project
like
multus
was
also
a
candidate
to
move
to
the
metroplying
working
group,
and
I
know
that
there
was
an
update
from
intel
that
it
was
a
proved
to
be
moved
to
a
public
govern
like
a
comma
like
a
community
governance.
B
D
Hey
this
is
dave.
I
worked
at
the
on
the
orchestration
team
at
intel,
so,
yes,
the
last
update
I
gave
I
think
I
had
mentioned,
that
we
were
priming
multis
to
move
and
in
terms
of
the
the
boilerplate
stuff
that
we
had
to
get
through
in
terms
of
our
own
internal
processes,
so
that
that
has
been
complete.
D
There
is
one
outstanding
issue
internally
that
we
have
to
resolve
first
before
we
actually
move
it,
but
I
it
won't
be.
It
won't
be
too
long.
It's
more
of
a
case
of
organizationally
speaking.
D
The
group
we're
in
is
is
part
of
a
bigger
group
and
there's
discussions
going
on
there
at
the
moment
and
just
in
terms
of
the
dependencies
in
terms
of
where
multis
is,
even
even
with
the
redirects
or
the
auto
redirects
from
github
and
stuff,
like
that,
they
should
cover
everything,
but
there's
still
some
some
testing
in
a
different
org
at
the
moment.
I'm
waiting
for
feedback
on
that
before
I
can
actually
move
it
over,
and
this
was
this.
D
Was
this
wasn't,
I
suppose,
part
of
the
the
solution
to
move
it
initially
when
I
prepared
the
update,
so
this
only
came
in
recently
enough,
when
I
say
recent,
as
in
start
to
month,
end
of
january
type
of
thing
so
yeah,
it's
still
in
our.
We
still
plan
to
move
this
over.
B
Let's
see
great
thanks
for
updating
and
do
you
know
which
what
what
would
be
the.
D
D
It
will
be
the
the
network
plumbing
working
group
yeah.
I
think
there
as
a
as
a
stop
gap
anyway.
It
would
be
great
we
got
in
under
cncf.
I
think
it's
a
it's
a
much
easier
ask
on
this
group
here
to
take
it
into
the
network
from
working
group
and
then
take
it
from
there
to
cncf,
if
possible.
A
Awesome
yeah
thank
you,
dave
and
I
definitely
agree
on
that
process.
You
know
I
at
least
from
my
standpoint,
and
I
certainly
would
love
any
help
on
this
one,
but
I
think
the
steps
the
way
I
see
it
would
be
multis
comes
to
network
plumbing
working
group.
I
think
that
we
should
go
through
the
steps
for
a
network
plumbing
working
group
to
have
some
official
capacity
within
the
cncf.
A
I
had
gotten
some
initial
information
on
that
from
some
people
internally
at
red
hat
that
are
involved
with
our
open
source
and
standards
type
of
operations,
and
it
doesn't
seem
difficult
but
need
to
follow
up
on
that
and
then
after
that,
then
we
can
look
into
having
it
moved
into
the
cncf
under
an
official
capacity
of
having
it
there,
which
to
me
would
be
the
ultimate
goal,
I
think,
would
be
very
nice,
so
dave
thanks
a
bunch
for
continuing
on.
A
I
definitely
understand
that
internal
processes
take
time
I,
as
far
as
I'm
aware,
there
haven't
been
any
problems
with
the
community
contributing
code
to
multis
and,
of
course,
while
I
look
forward
to
having
multis
officially
under
this
open
governance,
I
would
definitely
be
interested
with
working
with
anyone
who's
interested
in
contributing
maintaining.
A
We
can
definitely
use
a
helpful
hand,
definitely
open
to
getting
more
in
there
and
and
from
my
own
perspective,
you
know.
Intel
has
very
much
been
in
alignment.
There
so
definitely
feel
free
to
bring
up
any
issues
here
in
the
meanwhile
and,
of
course,
at
the
multis
maintainer
meetings
which
happen
every
other
week.
In
the
same
time,
slot
that's
a
different
zoom
call
but
feel
free
to
join
adrian.
The
next
one
is
whereabouts,
basically
same
same
kind
of
question
regarding
whereabouts.
B
Yeah
and
same
kind
of
question-
and
of
course
I
want
just
to
like
give
some
some-
you
know
some
some
kind
words
on
whereabouts
because,
like
we,
we
found
it
extremely
useful
for
our
like
both
internally
and
we're
actually
basing
some
of
our
reference
implementation
for
secondary
networks
with
the
whereabouts
ipam
to
enable
like
rdma
networks.
B
So
I
mean
big
up
for
I
mean
for
this
project.
We
found
it
like
extremely
useful.
We
actually
also
developed,
like
a
network
operator
which,
like
sort
of
enables
like
rdma
and
other
stuff
in
kubernetes,
so
we
are
using
whereabouts
as
as
ipam
for
secondary
network.
So
so,
first
of
all,
you
know
great
project,
so.
A
Adrian,
thank
you
so
much.
I
appreciate
that
a
lot
and
yeah.
That's
awesome.
That
really
makes
me
happy
to
hear
yes,
definitely
still
planning
to
move
it
to
network
plumbing
working
group,
and
we
have
already
voted
to
accept
it,
and
the
main
thing
that
I
need
to
do
is
one
of
my
co-maintainers.
A
I
need
to
get
him
to
go
through
the
process
to
to
join
the
work.
I
really
rely
on
his
help
and
anyways.
I
don't
wanna,
cut
him
off
or
shortcut
the
official
processes
here,
so
I
just
need
to
get
my
act
together.
I
mean,
I
know
it's
not
a
heavy
lift
to
join
and
become
a
maintainer,
and
I
know
everyone
will
appreciate
his
contributions
as
well.
A
So
yes,
absolutely
that
is
the
plan
and
it'll
be
nice
to
have
that
discussion
here.
I
also
am
planning
probably
to
have
regular
updates
for
whereabouts
during
the
the
multi-cni
maintainers
meeting.
It
doesn't
have
quite
as
many
issues
or
pull
requests
to
have
to
review
as
multis
does
so.
Hopefully,
it
gets
covered
fairly
quickly
in
there,
but
yeah.
Also,
I'm
super
happy
to
have
any
contributions
in
that
realm
as
well
and
yeah.
A
I
am
I
mean
I
really
want
to
help
prolong
the
lifespan
and
lifestyle
whereabouts
and
I
think,
having
it
in
the
group
is
gonna
definitely
help
out
there.
So
thank
you
for
the
reminder
as
well,
because
it'll
be
nice
to
to
have
that
to
have
that
officially
under
the
rooftop.
A
All
right,
any
other
comments
there
or
the
next
one
is
for
a
tomo
update
on
cube
cuddle
partner.
C
Yep
so
I
put
the
cubecutter.net
in
the
network
prompting
repository,
so
they
are
it's
just
the
cable
cutoff
plugin
which
showing
the
network
document
definitions
ip
address
like
the
cube
cutter
pot
output.
So
maybe,
if
you
go
to
the
repository,
you
can
see
the
sample
output
there.
So
so
the
this
is
pretty
immature
stuff
just
added
the
stuff.
So
please
use
that
and
then
the
feedback
is
pretty
welcome.
That's
it.
A
Cool
thanks
tom,
oh
one
idea
I
possibly
have,
and
I
don't
think
this
would
be
urgent,
but
the
idea
of
having
in
our
reference
deployments
something
that's
like
a
all
the
bells
and
whistles
kind
of
deployment
where
we
have
just
like
a
suite
of
our
tools
installed
like,
for
example,
multicni.
A
Maybe
you
whereabouts,
cute
cuddle,
podnet,
a
net
attached,
f,
ignition
controller,
something
like
that
and
one
place
that
I
see
that
it
could
be
handy.
As
I
know,
tomorrow,
you've
talked
about
kind
of
improving
our
public
materials
that
we
have.
You
know
in
terms
of
a
website
in
terms
of
having
some
kind
of
videos
available
for
introductory
material,
but
something
that
could
kind
of
show
people
all
the
tools
at
once.
I
do
realize
that
maintaining
something.
C
Yeah,
maybe
the
I
yeah,
maybe
kinds
of
the
not
not.
Maybe
it
may
not
the
reference
the
deployment
style.
I
mean
that
the
yummy
file,
because
there
are
some
of
them,
the
cni
router
barrage
or
the
some
cubical.net
of
course
is-
is
just
they
put
in
the
binary
stuff,
but
also
yeah.
Maybe
we
could
thinking
about
that.
So,
let's,
let's
continue
to
the
discussion
about
that.
A
Yeah
agree:
I
totally
see
what
you
mean:
it's
not
necessarily
all
stuff
that
runs
in
cluster
for
sure,
so
yeah,
a
good
consideration.
Yeah
yeah.
C
Of
course,
the
maybe
that
this
should
be
with
like
the
same
timing
at
the
youtube,
the
video
training
or
some
stuff.
I
think.
A
Yeah-
and
you
know
what
it
makes
me
realize
is,
you
know:
it'd
be
really
nice
to
have
some
like
newbie
materials,
for
something
like
multis,
that
you
know
it's
just
that,
but
it
might
also
be
nice
to
have
something.
That's
like
shows
kind
of
the
constellation
of
the
projects
that
we
have,
because
we
do
have
a
you
know,
while
a
related
set
of
projects,
but
a
pretty
diverse
set
of
projects
in
their
own.
A
A
All
right
cool,
thank
you!
Tomo
I've
got
the
next
one
and
I
just
wanted
to
note
that
on
the
tuesday
call,
so
if
you're
not
familiar
tuesdays
opposite
the
week,
so
we
have
this
meeting.
A
We
have
a
additional
discussion
which
is
currently
focused
on
the
network
policy
implementation
and
we've
been
having
a
great
discussion
there.
A
However,
I
brought
up
dynamic
attachments
this
last
tuesday
and
had
a
really
nice
conversation
with
pair
and
abdullah
about
that
and
abdullah
mentioned
that
he
would
potentially
give
another
demonstration
of
cactus,
which
is
the
column
fork
of
voltas
that
performs
dynamic
attachment
so
that
maybe
some
of
his
experience
that
he's
gained
with
this
type
of
architecture,
we
could
feed
back
in
to
to
multis
itself
and
potentially
to
the
spec.
A
A
So
I
just
wanted
to
mention
that
bring
up
that
additional
discussion.
One
thing
that
I'm
happy
to
say
is
in
this
additional
discussion.
You
know
we've
really
been
keeping
to
a
lot
of
the
technical
nuts
and
bolts,
and
I
realized
that
there's
some
amount
of
overhead
in
this
meeting.
That
is
bureaucratic,
and
I
I'd
at
least
liked
voice
that
any
technical
topics
are
still
absolutely
allowed
and
encouraged
in
this
call.
A
A
All
right
I'll
send
it
over
to
you.
Gary
you've
got
some
updates
on
the
container
registry.
E
Sure,
hey
doug,
so
this
is
not
something
I
personally
have
a
whole
lot
of
visibility
or
context
on.
So
this
came
from
martin
canelli
who's
he's
out
of
office
today
he
said
he
had.
He
was
involved
in
some
discussion
on
this
around
this
a
few
weeks
back
and
he's
just
wondering
if
there's
any
any
update
on
on
this
move
to
a
vendor
neutral
registry.
C
So
let
me
let
me
answer
this
stuff,
so
yeah
at
the
last
minute,
the
network
prompting
working
group.
We
are
the
right,
the
decide
to
choosing
the
github
container
registry,
something
let
me
let
me
check
the
your
github
content
registry.
C
Is
that
used
in
the
our
next
prices
to
a
container
registry,
so
the
I
the
so
they
are
regarding
so
about
the
amounts
mult
network
for
sip
table
implementation.
I
put
the
I
changed
the
ci.
I
mean
that
the
github
actions
to
put
the
latest
container
image
to
the
this
stuff,
so
that
the
I
in
the
agenda
I
put
in
a
two
places.
Two
urls
one
is
the
source
code
repository
and
then
another
is
the
containers
registry
as
as
a
part
of
the
packages.
C
So
they
are,
you
can
do
the
same
things
in
the
other
implementation,
so
they
are
so
for
each
repo
repository
owner
can
changes
the
this
stuff.
So
that
is
the
the
current
status.
E
Cool
thanks
tomo
is
there
is
our
plans
in
to
get
the
some
of
the
other
projects
moved
over
for
this?
Where
we're
hosting
our
container
images.
C
So
I'm
so
prepared
for
srb
things.
The
my
co-worker
is
the
likely
to
moving
this
stuff,
so
they
he
he
should
work
on.
That.
B
I
think
we
are,
I
mean
for
the
resource
management
working
group,
which
is
like
the
subset
of
the
survey
project.
I
mean
I
think
we
are.
We
are
aiming
to
move
to
this,
so
I
mean
this
is
discussed
in
like
in
in
our
bi-weekly
meetings.
So
I
will
add
it
to
our
next
agenda,
to
I
mean
make
a
game
plan
for
it.
B
I
know
that
we
want
to
do
a
first
release
for
the
survey
network
operator,
so
it
would
be
a
first
candidate
to
just
push
an
official
image
to
be.
You
know
a
released
image
to
to
gita
ripple.
So
it's
definitely
like
something
which
we
are
planning
to
do.
E
Cool
thanks
guys,
that's
all
I
had
to.
A
Awesome
thanks
gary.
This
concludes
what
we've
got
officially
on
the
agenda,
but
the
floor
is
open
and
the
world's
your
oyster.
Any
topic
is
good
to.
A
A
All
right,
there
are
no
other
topics
in
this
case.
I
appreciate
the
efficiency
of
the
call.
That
being
said,
hope
to
see
some
of
you
on
the
additional
discussion
meeting
and,
if
not
I'll
catch
you
all
on
in
two
weeks,
which
will
be
march
11.