►
From YouTube: Multi-Network community sync 20230222
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
Right
all
right,
welcome
everyone
of
the
multi-network
community
meeting
sync,
today's
22nd
February
and
today
on
our
agenda,
is
to
go
over
the
results.
I
think
I
want
to
now
stop
the
survey
for
for
the
the
naming,
I
think
and
then
next
continue
over
the
discussion
from
last
week
that
we
had
on
the
API
any
other
agenda
items.
Please
add
yourself
on
the
list.
If
you
want
to
discuss
something
else,
all
right
so
on
the.
B
A
A
C
A
Right
so
basically,
we
had
37
responses.
Let
me
close
this
now
and
basically,
what
we
are
having
is
our
pod
network
is
the
winner
with
24
choices.
First,
choices
for
from
everyone
in
the
who
take
part
in
this
basically
I
think
the
second
most
popular
was
I.
Think,
okay,
that
that's
six
with
some
secondary
and
third,
the
tra's
choices,
but
I
think
the
clear
winner
is
the
Pod
Network,
and
this
is
what
we're
gonna
go
with.
This
is
not
I
will
make
copy
of
this
and
put
it
in
the
dock.
A
So
we
have
it
like
a
a
kind
of
proof
and
some
data
behind
the
choice,
but
what
I
want
to
say
I
think
there
was
some
doubts
on
the
name:
it's
not
like
it's
set
in
stone.
If,
in
few
months
we
would
decide
that
the
name
still
doesn't
fit.
We
can
redo
the
process
right
now.
What
we
at
least
have
a
name
that
we
want
to
name
it,
and
we
know
we
have
a
reference
and
we
know
what
it
is.
A
A
C
A
B
A
A
It
will.
It
is
nicely
explaining
that
what
we
will
not
do
basically
will
not
change
existing
behavior.
All
the
existing
money
first
will
work,
as
is-
and
this
is
very
nicely
explicitly
defined
here.
Thank
you
for
that
Telma.
So
please
read
through
this.
This
is
kind
of
nice
yeah,
the
Pod
network,
Tommy,
you
were
mentioning
yeah
I
will
I
will
grab
the
text
later
on
and
just
everywhere,
where
the
network
is
mentioned.
A
I
will
just
just
change
that
to
the
Pod
name
pod
Network
later
on,
but
I
think
last
week
we
ended
on.
Do
we
have
a
notes
on
what
we
ended
on?
Okay,
I?
Don't
think
we
have
anything,
no
not
mentioned
all
right.
So
last
week
we
decided
DNS.
Config
is
something
that
might
be
completely
defined
somewhere
else
and
should
not
be
here.
If
anything
we
can
like,
maybe
in
future,
do
something
about
this,
then
we
talked
about
ipam
to
have
two
types.
A
This
is
the
kubernetes
type
and
internal,
and
this
is
in
line
with
what
we
have
today
in
KCM,
where
either
the
KCM
has
an
iPhone
controller
that
will
handle
your
Dynamic
assignment
or
the
other
option
is
a
cloud
and
it's
not
fully
similar,
but
basically
what
it
means
the
icon
inside
KCM
will
not
do
anything
right.
It
will
just
be
disabled.
So
that's
what
this
flag
kind
of
is
four
as
well
here
to
kind
of
had
similar
functionality.
So
this
is
something
as
well.
A
We
may
be
in
the
future,
apply
to
the
default
Network
right
since
we
will
have
this
same
object
should
exist
as
well
for
the
default
Network.
Maybe
instead
of
modifying
it
through
KCM,
this
guy
can
as
well
change
some
of
those
things
as
well.
Some
behaviors
so
keep
in
mind.
Whatever
we
do
here
for
the
additional
Network
eventually
should
be
applicable
for
the
default
Network
we
have
today,
yes,
Tom.
B
Yeah
and
let
me
clarify
that
absolutely
the
album
time
is
now
the
string
and
then
the
the
U
Define
in
the
external,
the
kubernetes,
but
as
you
mentioned,
if,
if
there's
some
crowd
provider
provides
some
stuff
at
that
time,
this
may
takes
the
another
value
than
the
kubernetes
external.
Is
that
correct
or
the
crowd
is
the
part
of
the
external.
A
I
would
say
the
cloud
would
be
part
of
external
right,
because
I
don't
want
kubernetes
means
I
am
leveraging
it's
similar
to
what
it
how
it
behaves
today.
Kubernetes
means
the
kcm's
icon
controller,
takes
over
and
handles
the
whole
ipam
assignments
for
the
nodes
for
that
for
the
default
network.
But
then,
if
you
put
a
cloud
basically,
the
cloud
name
is
very
I,
find
it's
unfortunate.
I
think
it
was
added
because
it
was
requested
by
Cloud
providers.
Mostly,
that's
why
the
name
stuck,
but
what
basically
it
means
is
I,
don't
want
kubernetes
to
do
this.
A
Yeah,
basically,
yes,
I
would
yeah
that's
what
it
is.
It's
an
enumerate
in
case.
Maybe
there
will
be
some
other
kind
of
types,
but
this
is
a
flag
that
controls
the
core
of
apis
right,
so
basically,
the
kcm's
API
controller
to
enabled
or
disabled
for
this
network,
and
this
kind
of
indirectly,
as
well
means
that
you
know
what,
with
this
cap,
I
want
to
have
the
the
icon
controller
to
support
this
network
as
well.
So
basically
it
could
handle
the
iPhone
for
us
when
it's
specified
as
kubernetes.
B
B
The
Network
I
mean
that
the
in
cluster
another
ice
rate
Network,
as
well
as
which
is
the
crowd
provider,
provide
Network.
At
that
time,
the
some
Network
May
consuming
the
wellbot
for
isolated,
In,
classical
Network
and
the
other
case.
Sometimes
they
for
AWS
based
Network.
They
may
use
it
the
AWS
iPhone
cloud
or
some
their
body
which
provides
by
the
AWS
at
that
time.
B
C
A
B
B
But
now
the
kubernetes
introduces
one
well-known
level
to
specifying,
and
then
the
weekend
contains
the
various
values.
Not
only
the
the
empty
empty
is
for
the
KCM,
and
then
the
user
account
putting
any
values
to
specifying
some
of
the
stuff,
and
then
they
Implement
data
implementation
is
using
these
values.
I
mean
at
the
in
the
about
us
proxy
case,
depress
adding
the
value
in
the
model
proxy
and
the
KP
energy
case,
putting
it
in
the
KPLC.
B
A
This
is
I
would
say
they
use
external
here.
I
I
wouldn't
want
to
expand
this
enumerator
to
implementation.
Specific.
No,
that's
not
the
point.
The
point
here
is
either
it's
it's
very
high
level.
It's
now
there
should
not
be
and
will
not
be
any
implementation,
specific
Flags.
So
basically
this
says:
if
you
want
to
use-
let's
say:
let's:
let's
put
it
on
example
of
multiples
right.
If
I
want
to
use
this
with
motors
right,
I
would
put
and
I.
Let's
say
you
just
want
to
use
a
whereabouts
with
motors.
A
So
I
will
use
my
external
stuff
here
and
then
in
my
where
is
it
in
my
params
ref
I
will
reference
my
network
attachment
definition
which
inside
has
the
whereabouts
defined
in
it
and
how
it's
configured
right
or,
let's
imagine
a
bit
of
different
situation.
I
have
a
I
use,
I
use
kubernetes.
So
what
it
means
is
with
kubernetes
and
in
my
draft
I
I
I
kind
of
propose.
What
would
it
mean
if
it
was
kubernetes,
then
what
I'm
doing
is
I'm
leveraging
kubernetes
existing
parameters?
A
So
basically
my
implementation
looks
and
it's
aware
of
okay
for
this
network.
It's
it's
a
kubernetes,
so
I
have
to
look
at,
for
example,
on
the
Node
similar
as
it's
a
nice
look
today,
for
what
is
the
posts
either
for
this
node?
So
I
will
again
see
and
I
will
look
at
that
note
again
and
look
okay.
What
is
the
cni
for
this
network?
What
is
the
podside
apologies?
What
is
the
port
side
there
for
this
network?
A
Oh
it's
this
and
I
know
the
value
is
there
or
I
will
expect
the
value
being
there,
because
my
iPhone
controller,
the
the
kubernetes
KCM
icon
controller,
will
populate
that
value
and
set
it
up
for
me.
So
basically,
that's
what
I
mean
by
a
difference
between
a
kubernetes
versus
external,
is
that
clear,
I
think
we
have
a
bunch
of
hands
a
pair.
D
D
Then
so,
when
we're
looking
at
these
things,
so
do
we
still
assume
that
we
have
a
bullets,
specific
Network
definitions
on
whether
we
refer
from
here
or
is
this
the
thing
because
different
vendors
will
have
different
networks
right,
that's
true,
yeah!
So
so
this
doesn't
become
more
like
a
view
of
of
that
Network,
and
that's
probably
where
you
set
the
date,
but
I
mean
some
of
them
needs
to
be
said.
Like
you
have
item
here,.
A
A
D
A
D
Of
well
I
said
that
you
can
still
sort
of
say
we
have
status
obvious
later
on
right.
That
returns
exactly
or
something
look.
You
could
do
the
same
thing
with
returning
a
topology
and
something
is
built
up
to
help.
People
understand
the
debug,
because
you
get
a
lot
of
very
optional
parameters
in
here
like
have
routes,
oh
well,
that
that
only
makes
sense
to
set
it
for
certain
topologies
and
so
on.
A
I
think
it
because
it
will
boil
down
to
how
it's
implemented.
This
will
represent
that
no.
This
is
this
will
state
that
okay,
there
is
a
default
Network,
a
pod
Network
and
some
other
ones,
and
this
this
is
what
the
subject
will
give
you
information
about
and
then
very
high
level
stuff,
like
okay,
who's,
doing
iPhone
for
it
for
now,
and
maybe
some
other
will
get
you
those,
but
for
now
we
know
it
will
Define
who's
doing
icon,
for
it
is
it
is
it
based
on
the
internal
kubernetes,
stuff
or
or
external?
D
A
B
A
A
A
What
it
means
is
the
the
existence
of
the
field
will
be
more
meaningful
for
your
implementation.
Only
at
that
point
what
it
had.
You
have
two
additional
values
in
configuration
where
okay,
it
means
external,
so
I
I
mean
this
network
has
to
have
an
iPad.
So
my
implementation,
no
I,
have
to
do
icons,
do
something,
or
there
is
nothing
in
iPad
means.
My
implementation
should
do
nothing
because
I,
don't
even
specify
external
means.
I
should
not.
C
B
So
so
the
let
me
cry
for
what
are
you
thinking
about
the
if
the
empty?
This
is
the
empty
at
that
time,
that
this
means
the
kubernetes
or
external
appam.
Do
not
care
about
the
IP
address,
not
the
mentioning
the
radio,
2
Network
or
some
stuff.
So
this
means
that
this
network
may
be
used
for
layer,
2
or
sometimes
they
are.
This
IP
address
will
be
assigned
in
the
the
hcp
or
truck
other
than
the
the
other
day.
B
E
It
where
I
see
it
going-
and
this
gets
back
to
my
example-
of
using
dark
of
a
podman
to
get
the
points
across
the
API
server
needs
to
be
pointed
to
the
name
that
you
can
find
in
whatever
we
do
the
conflict
on
disk
CID.
Whatever
we
decide
to
do
for
implementation
specific,
but
down
here,
these
parameters
might
specify
a
static,
IP
or
a
static
Mac
that
might
be
used
by
the
IPM
to
feed
DHCP
so
that
the
dacp
server
will
give
you
a
well.
The
IP
address.
That's
provisioned
for
this
specific
application.
E
Its
parameters
to
the
the
apis,
the
the
implementation,
specific
network,
name
that
you
specify
here
name
opaque
whatever
ID
I.
Don't
you
you
ID
I,
don't
care
what
we
end
up
doing
to
identify
it,
but
at
the
end
of
the
day
we
have
to
specify
Foo
and
then
provided
parameters
that
are
food.
Specific
right,
which
happened
to
touch
on
what
trauma
was
just
talking
about
right.
E
A
Yeah,
that's
I,
I
agree,
but
that's
the
thing
right:
you're
talking
about
cni
and
you're
thinking
about,
let's
say
a
basic
whereabouts
or
static
icon,
where,
yes,
those
has
to
be
supplied
information
about
the
decider
that
I'm
to
use
directly
to
cni,
and
if
that's
your,
that's
that's
one
of
the
implementation
Michael,
that's
not
the
only
one,
yeah
okay!
So
so,
basically,
it's
up
to
your
implementation.
A
No
okay
I
will
grab
the
IP
from
there
and
basically
in
case
like
Bluetooth,
they
don't
care
about
any
of
this
and
they
assume
that
we're
going
to
have
a
cider
defined
inside
the
cni
and
the
cni
configuration
and
that's
up
to
the
implementation,
of
course,
because
that's
what
it
is.
But
what
I
want
to
say
is
the
first
path
should
be
enabled
for
multi-networking
as
well.
That's
what
I'm
getting
at
right,
so
I
don't
have
to
specify
the
cider
in
conflicts.
A
I
can
grab
it
from
the
node
object
and
if
I'm
happy
with
that,
then
I
can
use
extra
internal
rather
than
sorry.
Internal
I
can
use
the
kubernetes
option
rather
than
external,
because
then
I
save
myself
with
a
headache
of
okay
I
need
to
specify
decided.
You
know
the
configurations
and
with
this
I
don't
I
just
have
it
automatically.
Of
course,
in
the
future
approach
like
whereabouts
can,
instead
of
expecting
the
the
conf,
the
configuration
should
be
inside
the
the
cni
config
file.
A
Maybe
it
can
grab
it
from
the
node
as
well,
and
that
would
be
awesome
right,
because
then
it
can
just
grab
it
and
feed
it
from
the
nodes,
a
podside
that
basically
rely
on
the
same
thing
right.
So
that's
that's
where
this
is
filled.
This
field
is
supposed
to
be.
What
is
the
word
is
b
kind
of
another
place,
but
allow
the
same
functionality
that
the
KCM
has
for
the
who's
doing
the
icon.
Is
it
me
or
or
or
not-
and
this
is
the
only
kind
of
functionality
for
the
skill.
F
Hey
guys,
so
my
question
is
related
to
the
iPhone
type.
So
far,
what
my
reading
is
is
only
two
types,
external
or
kubernetes
external
means
cloud
provider
will
bring.
Your
own
will
bring
their
own
ipam.
Is
there
a
the
customer,
won't
Define
what
ipam
like?
If,
if
I
need
different
different
type
of
ipams
for
different
type
of
networks
that
is
not
defined
here
right,
it's
just
simply:
either
external
or
kubernetes.
That's.
A
F
F
A
So
we
have
we're
going
to
talk
about,
but
basically
there
we're
gonna
get
there,
there's
a
Firearms
reference
of
a
field
and
that's
how
you
will
link
some
custom
implementation,
specific
field
to
okay,
this
guy,
this
network
uses
external,
but
then
informal
implementation
I
want
to
use
Foo
and
for
this
other
network
I
want
to
use
bar,
and
that
will
be
specific
to
your
implementation.
How
you
handle
this
sounds.
A
I
think
I
think
that's
I
would
say
so
I'm,
not
sure
what
is
the
default
today
in
KCM
for
the
default
Network
I
will
have
to
I.
Will
I
will
really
into
this
and
see
what
what
they
default
to
I?
Don't
think
they
that
they
do
ex
like
nothing
as
well.
If
you
don't
specify
anything,
I
I
have
to
look
into
that.
What
KCM
has
one
more
note
on
this
one,
something
that
we
might
something
that
might
be
interesting:
dual
stack
and
V6,
because
I
think
we
keep
making
this?
A
This
will
be
an
enhancement
towards
this
would
be
enhancement
versus
what
we
have
today
in
KCM,
because
KCM
does
one
globally
right.
It's
either
V4
or
either
external
inter,
but
this
will
be
an
ability
for
us
to
now
to
iPhone,
4
or
icon
6,
and
then
I
have
a
separated
capability
to
and
to
kind
of
Define
fine,
fine
grain
of
who's
doing
which,
which
family.
E
A
This
will
give
us
as
well
some
level
of
control,
whether
as
launcher
as
well
of
dual
stack,
that
can
be
an
indicator
or
not,
but
basically
having
those
split
you
can
specify
I
want
to
have
four,
only
six,
only
or
both
or
neither
right.
So
basically,
that
gives
us
as
well
this.
This
combination
of
possibilities
for
for
that.
C
F
C
A
Then
you
would
have
to
have
four
and
six
in
your
in
your
custom.
Object
split
as
well
right
once
you,
because,
if
you,
depending
on
what
you're
doing,
but
let's
assume
what
can
I
do
right,
I
can
do.
I
will
look
at
this
field
as
well
myself
in
my
implementation
and
then
see
who's,
doing
which
part,
and
then
let's
say
six
is
a
DHCP.
A
C
F
A
F
A
What
no
because,
then
you
what
you
with
this
approach,
you
would
say
there
is
a
pod
Network
before
and
what
network
V6,
because
that's
what
it
refers
to
and
then
that
speaks
the
purpose
right.
I
want
to
have
a
network,
that's
either
before
either
V6
or
dual
stack
or
an
item,
so
that
wouldn't
work.
No,
so
your
implementation
will
have
to
because
your
implementation
has
to
support
dual
stack
as
well.
That's
what
it
boils
down
to,
because
kubernetes
supports
the
world
stack,
that's
where
that's
why
it
has
to
be
combined
in
one.
A
C
F
Sorry
sorry
so
then,
in
that
case,
do
we
want
to
have
I
agree
with
that?
One
crd,
which
will
tell
me
whether
it's
V4,
V6,
dual
stack
or
single?
So
how
we
are
writing
is,
should
we
not
bind
the
param
ref,
along
with
the
ipam
type,
that
this
is
my
vehicle,
and
this
is
my
param
ref
for
V4.
This
is
my
V6,
and
this
is
my
parameter
for
V6.
A
A
It
can
have
like
a
different
configurations
of
whether
I
use
a
vxlan,
because
my
implementation
supports
vxlr,
supports
L2
or
anything
else,
so
I
can
have
all
those
other
combinations.
So
this
object
can
not
only
say
about
ipam,
it's,
it
can
Encompass
platter
around
different
things:
okay,
so
so,
and-
and
there
is
a
kind
of
considering
we
are
linking
to
an
a
kind
of
secondary
or
also
other
custom
parameter.
D
A
A
Think
I
agree,
but
then
that's
a
different.
That's
not
the
I
want
to
push
back
on
that,
because
that's
not
a
topic
for
multi-networking,
that's
topic
for
just
kubernetes
and
how
iPad
is
supported
in
kubernetes
in
general,
yeah,
but
and
and
and
basically
what
I
would
say
is
if
we're
going
to
change
how
ipam
is
done
in
in
the
on
the
default
Network
in
the
default
stuff.
A
D
That
is
not
true.
That
is
absolutely
not
true,
because
the
networking,
as
in
kubernetes
today,
lives
in
a
sandbox
and
there
kubernetes
is
able
to
say
these
are
the
rules.
What
do
you
do
in
multi-networking?
Is
that
you're
inviting
the
rest
of
the
world
in
and
then
sort
of?
You
cannot
hide
from
it.
I'm
not
saying.
A
That
I
don't
know,
but
but
this
is
what
I
wanted
to
say
is.
This
is
some
discussion,
because
we
cannot
have
everything
at
once
right.
This
is
what
I'm
trying
to
get
to
maybe
as
well.
What
we
can
do.
This
is
something
that
we
can
postpone
later,
because
then
we're
going
to
have
more
means
to
how
to
describe
it
and
Define
it.
What
you're
saying,
but
for
now,
let's
try
to
introduce
something
that
is
in
parity.
What
we
have
to
take
kubernetes
all
right.
We
are
already
enhancing
it
a
bit,
but
then
we
can.
A
D
A
D
A
That's
what
I'm
saying
it's
completely
transparent
for
the
API
should
I
see
it.
No,
it's
based
on
my
implementation
and
if
my
implementation
handles
the
whole
ipump
story
and
it
will
just
provide
and
fill
in
all
the
API
standards
required
So.
Eventually,
what
you're
saying
should
be
impose
enforce
a
specific
type
of
eye
pump.
I
said
no,
because
kubernetes
doesn't
do
it
today,
either
either
so
for
now,
no
I
would
say
we
should
not
impose
any
specific
restrictions
on
this,
because
anyone
can
do
whatever
right.
We
have.
We
have
the
ATP.
B
Double
I
have
the
this
is
not
the
question
of
just
the
impression
about
this
design,
so
the
one
thing
so
there,
this
design
seems
to
be
the
inconsistent
I
mean
that
the
two
eye
pump
design,
but
the
one
louds
I
mean
that
the
for
both
address
family
I
think
in
this
design
and
in
additions
So.
Currently
we.
A
A
A
So
and
that's
fair
because
for
default
Network
today
we
don't
support.
No,
we
do
support
single
stack,
but
basically
because
you
can
specify
one
one
IP
family
right,
so
you
can
do
one
or
the
other
or
both.
So
basically,
we
would
be
able
to
represent
the
other
possibilities.
Is
that
we
do
have,
let's
say
dual
stack,
but
one
is
external
One
internal.
We
do
not
support
this
in
in
the
default.
Network
I
agree
with
you
on
that.
But
then
this
is
an
implementation
piece
that
that
implementation
just
doesn't
support
that
combination
right.
B
I'm
not
talking
about
the
implementation,
I'm,
just
think
the
talking
about
the
the
usability
perspective
that
this
design
is
not
the
matched
with
the
current
part.
So
currently
the
user
is
looking
the
IP
address
by
the
one
single
the
IPS
field,
and
then
the
the
user
is
identifying
the
like
the
using
the
go
rank
to
to
4026
and
then
they
get
there.
This
addresses.
C
B
A
No,
this
is
going
to
change
right,
keep
in
mind,
this
wouldn't
change,
because
this
just
Define
who's
doing
stuff,
not
how
it's
done
again.
So
basically,
if
this
one
says
kubernetes
on
PO,
this
is
the
today's
example.
This
is
the
default
Network.
What
if
you
have
a
dual
stack
cluster,
what
it
means
is
populate
the
Pod
cider
with
uip
file
which,
to
the
with
two
IPS
one
for
each
button,
that's
what
it
means,
and
basically
it's
still
the
same.
There
is
no
change
on
that.
B
A
D
A
We'll
get
there
all
right.
Moving
on
on
the
next
build,
it's
an
old,
selector
I.
This
is
a
old
comment,
a
pair,
that's
what
I'm
bored
before
before
this
one.
There
was
a
node
interface.
The
the
initial
dock
has
a
reference
with
this
crossed
out
an
art
interface.
Matcher
was
a
basically.
It
was
implementation
specific,
so
it's
like
in
in
the
cnis
like
ipvlan
or
Mike
villan.
Those
would
have
a
I
think
they
call
it.
Unfortunately,.
A
So
no
it's
it's
it's
small
on
to
kind
of
identify.
So
basically
this
is
not
valid
anymore.
That's
what
it
is
all
right,
so,
basically
this
field
and
we
can
get
rid
of
it.
Basically,
this
is
another
way
on
maybe
one
or
two
multiple
ways,
because
we
said
the
network
can
be
selectively
available
in
your
cluster
and
I
think
this
is
something
that
we
would
want
to
handle.
This
is
something
that
we
would
want
to
have.
A
I
saw
this
as
in
a
phase,
two
I
recently
did
review
for
the
our
requirements,
so
selective,
selective
availability
of
a
network
is
a
is
a
phase
two.
Should
we
then
get
rid
of
this
field
and
talk
about
it
then
so
I
think
this
is
this
is
this
is
scheduled
for
our
face
to
any
any
objection
to
getting
rid
of
this
now
and.
D
A
All
right
moving
on
then
param's
reference
I
think
this
is
everyone's
I
think
the
name
is
similar.
I
copied
the
name
from
Gateway
API
I
think
they
use
parameters.
Param
surf
I
I
need
to
double
check.
I
might
be
mistaken.
I
need
to
update
this
field,
but
basically
the
the
behavior
is
similar
to
what
was
introduced
in
Gateway
apis
I'm,
assuring
one
of
you
following
that
one.
A
But
what
it
means
is
just
a
reference
to
a
implementation,
specific
parameters
and
I.
Imagine,
for
example,
this
could
reference
a
network
attachment
definition
from
Motors
to
kind
of
kind
of
marry
those
two
together
right.
So
basically,
this
just
references,
who's,
doing,
ipam
and
and
basically
is
being
referenced
around
in
the
core
apis.
But
then
this
guy
references
a
network
attachment
definition
which
does
the
full
implementation
and
piping
into
the
port
right.
A
I,
don't
think
there
is
any
any,
and
this
is
optional,
of
course,
because
if
you
have
an
implementation
that
just
very
basic
I
just
do
ipam
I
I
do
only
one
type
of
piping
configuration
into
pods
I,
don't
need
any
configurable
configuration,
then
I
don't
need
this
object
and
I
just
need
a
reference.
Okay,
this
I
just
need
the
split
between
which
network
is
what
and
and
that's
it,
how
it's
implemented.
There
is
no
addition
parameters
to
it,
for
the
customer
or
for
the
user.
Basically,.
D
D
A
Any
other
comments
on
the
param
surf
because
before
I
move
on
no
okay,
so
so
that's
that's.
Okay,
I
will
just
update
the
comments
on
this
provider.
Provider
is
and-
and
take
me,
let
me
know
if
that's
needed
and
we
can
get
rid
of
it
or
not.
But
this
the
idea
behind
this
is
to
specify
who's
implementing
this
network.
I'm,
not
sure
how
my
this
is.
A
This
is
copied
from
Ingress
Ingress
has
a
providers
as
well,
and
this
is
where,
where
this
was
kind
of
copied
off,
so
imagine
Ingress.
There
are
multiple
implementers
for
Ingress
object
and
I
can
specify
who's
doing
it
right.
So
the
similar
kind
of
patterns
here
in
the
network
I
can
have
multiple
implementers
for
a
network,
and
this
one
will
Define.
Okay,
who's
who's
who's.
Implementing
this
so
I
have
ability
to
split
between
if
I
can
have
like.
A
A
This
is
this,
is
this
is
point
to
the
implementer,
so
it
can.
The
name
is
just
the
string
all
right,
so
it
can
be
any
name
you
steam
right.
It
can
be,
let's
say
some
event
like
domain
name
like
I,
don't
know:
gka
dot,
IO
and
slash
Foo
to
indicate
that
I
am
the
provider
for
this
network
right,
so
it
can
be
any
type
of
string.
That's
what
that's
the
point
of
it!
A
It's
not
pointing
to
a
specific
cni
here,
because
it
doesn't
indicate
that
it's
just
who's
who's
going
to
implement
this
right,
so
that
I
can
differentiate
between
two
implementers.
If
I
had
that
such
such
configuration
in
my
cluster
and
imagine
in
the
future,
maybe
that
that
will
be
the
future
right
where
you
can
have
a
cluster
which
will
have
multiple
Network
providers
and
each
implementing
it
and
that's
how
they
would
differentiate
right,
yeah.
D
So
so
so
the
way
we
do
is
things
like
we
put:
we
have
an
implementation,
specific
Network
definition
that
also
sits
in
in
this
is
not
an
API
with
a
crd
that
and
then
at
some
point
want
to
point
to.
I
can
of
course
do
that
from
the
parents.
Ref
no
problem,
and
this
would
then
just
say
which
network
type
it
is
in
reality
right.
A
Not
exactly
because
param
surf,
yes,
I
could
identify
this
via
okay.
Does
this
network
references
my
object
or
not?
That's
that's
fair,
but
what,
if
I,
don't
use
any
additional
configuration
right,
I?
Don't
care
about
parents,
my
limitation
is
very
straightforward:
I
don't
need
any
additional
configuration.
This
object
is
sufficient.
D
Do
whatever,
in
my
system,
there
are
crds
once
the
implementation
series
that
represents
all
networks
and
from
here
I
want
to
reference
that
right,
I
can
see
it
made.
I
can
see
in
our
system.
We
do
that
from
the
parent
thread
and
sort
of
that's
I,
put
also
in
sort
of
what
you
reference
like
the
research
with
type.
But
this
with
the
provider.
I
could
not
say
a
reality,
Network
implementation
provider
and
we
will
have
our
own
networks
called
Kno
of
all
things.
No,
that's
not
that's
the
network
operate
about
so,
but
yeah.
A
A
I
I
I'm
just
I'm,
just
showing
you
examples,
but
this
can
be
various
whatever
the
string.
Your
implementation
provides
and
basically
I
would
follow
here.
The
same
idea
that
Ingress
has
right
or
Gateway
I'll
actually
look
into
those.
Maybe
I
need
to
look
at,
maybe
Gateway,
maybe
the
gate,
the
new
Gateway
API.
There
was
discussion
on
this.
Maybe
they
take
it.
I.
B
Questions
the
so
the
so
so
the
if
so,
I
and
so
so.
Well,
maybe
the
provider
May
is
the
the
be
optional,
but
I
I
have
that
type
of
question.
If
the
of
the
this
is
the
no
value
at
that
time,
the
what
does
it
mean
and
then
also
the
if
provider
is
the
empty
string,
not
the
No
No
value
is
that
the
have
a
different
meanings
of
the
stuff,
or
so,
you
should
add,
should
add
the
some
non-empty
string
or
no
provider.
B
B
A
E
A
E
A
A
E
I
just
want
to
make
sure
it's
unambiguous,
oh
I,
I
see
I,
see
yeah
that
everyone
has
to
play
by
the
same
rules
and,
if
we're
all
looking
at
all
these
things,
thinking
we're
the
only
Network
implementation
on
the
Node.
If
we
are
the
only
Network
implementation,
then
it's
easy,
but
if
there's
overlapping
and
I've
just
picked
out
of
the
Calico
and
flannel
just
to
pick
on
a
few
things,
they
can't
both
think
that
they
own
this
object
because
it
might
not
be
addressed
to
them
quote
unquote
addressed
I.
A
A
This
isn't
a
higher
level.
This
is
on
the
level
of
objects
not
on
cni,
so
keep
in
mind
Michael.
This
is
this
only
level
of
objects,
so
my
reference
and
template
here
is,
let's
say:
Ingress,
which
has
similar
field
and
basically,
if
it's,
if
you
consider,
if,
if
we
consider
I
added
this
as
optional
well
to
allow
coexistence
of
multiple
implementations
in
a
cluster
and
if
we
deem
that
this
is
unnecessarily
complicated,
let's
just
remove
the
speed.
A
That's
that's
the
reason
this
field
is
here
to
kind
of
allow
coexistence
of
multiple
implementations
in
the
cluster,
but
if
that's
completely
over
completely
over
complicated
and
then
let's
get
rid
of
them
to
what
Perry
was
saying
that
okay
is
what
object
I'm
referencing,
if
it's
my
implementation,
then
I
would
use
it.
If
it's
not,
then
just
there's
enough
right.
It
can
be
indirectly
through
parents.
F
C
A
Provider
here
so,
let's
say:
I
have
Network,
let's
maybe
give
different
reference
maltus
versus
Calico
right.
So
basically,
what
it
means
is:
okay,
this
spot
Network,
this
specific
one
is
implemented
by
cardio
and
it
handles
the
whole
thing
and
then
Bluetooth
doesn't
care
about
this
object
and
doesn't
touch
it.
On
the
other
hand,
there
may
be
other
pod
network
with
voltus
defined
in
it,
and
basically
that
means
that
kaliku
will
not
touch
it
and
Motors
will
do
it
and
this
happens
within
the
same
process.
A
That's
the
point,
so
we
have
two
implementations
in
the
cluster
that
can
could
at
least
on
the
API
level.
Keep
this
mind.
This
is
API
because
the
the
implementation
level
that's
completely
different
story,
because
Motors
takes
over
the
whole
cni
and
that
may
kind
of
interfere
with
your
Calico
to
attention
and
that's
a
completely
different
story,
whether
those
implementation
can
even
coexist,
and
but
that's
completely
out
of
the
scope
of
us
here.
This
is
enabling
API
for
that
capability.
A
Exactly-
and
this
is-
and
this
is
up
to
implementations-
because
that's
that's
not
because
right
now,
as
you
know,
there
is
apis
and
the
cni
is
kind
of
the
just
the
one
entry
right.
So
this
doesn't
talk
about
coexistence
of
implementations
at
all.
It's
just
enabling
the
apis
and
I
agree
with
you.
We
have
only
single
cni
call
today,
which
can
have
only
single
configuration
which.
E
A
Right
so
I
think
we're
beginning
to
implementation,
but
let's
stick
it
keep
it
on
the
API
level.
This
is
what
what
it
would
provide
the
question
to
all
of
you
is:
do
we
need
it
or
should
we
remove
it
right?
That's
what
that's!
What
the
question?
Okay,
I,
think,
folks.
We
are
at
a
very
long
time.
Tomorrow
you
had
a
hand,
you
have
other
questions.
Yep.