►
From YouTube: Kubernetes SIG Network Bi-Weekly Meeting 20200331
Description
Kubernetes SIG Network Bi-Weekly Meeting 20200331
A
B
B
B
D
B
F
F
B
F
B
G
B
E
F
E
F
B
E
E
H
H
F
H
B
B
Why
we?
We
might,
we
might
turn
on
the
state
we
match
on
new
when
we
send
it
to
cube
services.
But
if
there's
no,
no
sorry,
that's
external
services
right
here
right,
but
there's
nothing
in
cube
services
that
says
allow,
and,
at
the
end
of
the
day,
the
forward
policy
is
dropped,
so
it
falls
out
the
bottom
and
gets
dropped.
B
F
B
B
F
F
I
F
B
B
G
H
D-Net
is
where
the
packets
enter,
but
I
have
problems
where
the
packets
end
up
in
the
node
that
doesn't
do
the
dna.
It
just
receives
something
because
it's
the
same
thing
but
more
clear,
because
you
have
no
traversing
in
dna
tables
at
all.
You
just
get
the
packet
that
should
be
routed
to
a
to
a
pod,
but
you.
B
I
think
that
is
the
real
answer
is
like
turning
it
onto
setting
it
to
drop
means.
You
have
to
add
rules
for
every
pod
in
the
allow
chain
right
see
what
docker
did
in
that
like
it's,
it's
a
problem,
okay
anyway,
this
is
on
antonio.
This
is
this
issue.
Let
me
know
if
you
want
cover
on
it
next,
so
we've
got
two
issues
that
are
opened
that
are
discussing
this
destination
versus
source
model
and
how
we
route
stuff.
B
B
I
I
B
I
I
B
F
B
What
is
the
logic
for
why
we
copy
them
to
each
other
or
no
well?
Why
why
it
fails?
I
mean
where
is
the
program
I
the
problem?
The
problem
is
deep
down
in
cubelet,
which
reads
from
the
api
server
an
object
that
has
host
ips
set
and
then
it
rebuilds
status
and
doesn't
set
host
ips,
and
so
it
starts
throwing
errors
that
the
object
in
the
cache
doesn't
match
the
object
that
it's
trying
to
write
and
and.
F
B
F
B
K
B
B
B
L
I
just
looked
at
that
one,
that's
on
me.
Apparently
there
was
up
here
I
needed
to
put
in.
I
just
have
to
go
figure
out
what
it
is.
I
guess
I
was
focused
on
docs
and
I
wasn't
focused
on
even
though
there's
no
code
changes,
I
guess
we
have
to
go
change
it
somewhere
to
say
data
instead
of
alpha,
so
they
don't.
B
J
B
G
B
Oh
boy,
all
right
what
else
node
ipam
to
support
multiple
cluster
sizers,
so
the
api
part
of
this
went
in,
but
not
the
implementation,
part
of
it
and
ordinarily.
We
wouldn't
do
that,
but
antonio
suggested,
and
he
was
right.
We
can
build
the
external
implementation
for
this
and
prove
that
out
with
the
api
built
in,
so
I'm
going
to
move
that
into
alpha,
because
it
is
congratulations
to
the
folks
who
worked
on
that.
B
I
F
B
B
I
M
M
L
So
this
is
the
one
that,
after
we
discussed
it
in
cloud
provider,
then
the
question
was
like:
oh
should
we
be
talking
about
this?
You
know
like
this.
Is
I
think
andrew
psycham
said.
Maybe
we
should
discuss
this
insig
network
if
it
touches
any
of
the
things
that
they're
discussing
and
if
we
think
it
does
not,
then
that's
fine,
but
I
wanted
to
make
sure
we
had
a
chance
to
weigh
in
on
it
this
route
controller,
updating
routes
with
when
the
node
ips
change.
B
B
B
I
B
B
B
B
I
Yeah,
I
did
everything
except
the
writing
functions
to
parse
the
the
regular
expressions
thing,
because,
like
each
time,
I
thought
about
it.
You
know,
if
we're
going
to
do
this,
like
it's
not
at
all
specific
to
the
unit
test.
We
just
want
to
have
like
a
general
like
you
know,
we
would
want
to
be
doing
this
everywhere.
Right.