►
From YouTube: Kubernetes SIG Windows 20170627
Description
Kubernetes SIG Windows 20170627
A
Hello,
everyone-
this
is
another
meeting
for
sig
windows
for
the
kubernetes
project,
from
give
a
couple
of
updates
where
we
are
on
the
project
and
then
I'll
open
up
the
floor
for
discussion,
given
in
the
last
couple
of
weeks
who
haven't
made
a
tremendous
amount
of
progress.
The
the
one
good
thing
doesn't
have
to
report
is
the
node
port
is
working
very
well.
A
So
so
that's
a
net
positive,
so
we're
able
to
get
the
routing
and
all
the
networking
infrastructure
set
up
for
not
port
and
the
team,
namely
Bob,
is
working
right
now
to
establish
some
of
the
other,
more
complex
networking
artifacts,
and
only
the
ability
to
put
multiple
containers
in
a
pod.
The
ability
to
address
the
pod
is
a
single
IP,
that's
possible
and
a
couple
of
other
things
along
those
lines.
A
We'll
also
had
a
couple
of
other
folks
express
interest
in
joining
our
team,
as
developers
I've,
given
them
some
of
the
ramp
up
documents,
including
access
to
documentation,
as
well
as
the
contributors
guide
for
for
kubernetes
in
general,
I'm,
not
sure
if
they
will
end
up
coming
and
contributing
but
I've.
Given
them
all
the
details,
the
need
to
to
get
started
to
deploy
the
solution
start
filing
some
bugs
and
then
can
help
them
start
fixing
this
bug.
So
they
can
slowly
inordinately
get
introduced
to
the
project
and
start
contributing.
A
A
B
Hello,
this
is
Alan
from
Quebec.
We
finished
our
investigation
about
multiple
containers
per
pod.
There
are
a
few
bad
news,
and
some
good
news,
unfortunately,
is
the
Windows
networking
stock
is
today.
You
cannot
have
the
equivalent
of
the
network
namespace.
Oh
the
battening
space,
which
are
currently
used
for
creating
containers.
B
They
are
as
isolated.
The
only
problem
is
you
get
a
network
on
a
namespace
per
container,
unfortunately,
from
other
investigation
cannot
use
multiple
container,
which
shared
the
same
network.
Namespace
I,
don't
know
if
they
plan
to
update
this
in
the
future,
but
from
our
investigation
is
I,
think
it
was
introduced
in
Vista
and
we've
got.
Two
used
was
introducing
this
cup
for
PPM's
networking
to
segregate
the
network
between
multiple
VPN
interfaces.
Oh,
we
played
the
role
with
some
ideas
and
we
could
probably
mimic
the
behavior
of
the
networking
space.
B
A
B
B
A
A
For
that
one,
it's
just
for
the
infra.
Ok,
so
essentially,
what
you're
saying
is
the
couplet
needs
to
call
the
cni
interface
every
time
a
container
gets
created,
not
just
a
single
time
for
the
pod
and
then
once
you
do,
that
you'll
be
able
to
create,
in
your
networking
force
interface
that
you
created
as
a
shared
interest
rate
across
all
the
containers
in
the
pod,
and
that
could
become
the
single
rideable
interface
for
extended
transactions.
That.
B
C
B
Well,
we
also
need
to
create
like
Appeals,
you
can
see.
I
mean
we
just
note
that
the
concepts,
though
we
didn't,
have
any
PLC
to
see
if
it's
actually
working,
if
we
actually
have
it.
Oh,
but
still,
if
you
have
a
part
of
the
code
which
is
only
windows,
specific
I,
don't
know
if
you
can
push
that
to
the
common
code
in
the
cupola
itself,
we.
A
Can
definitely
engage
with
the
signals
folks
and
and
talk
about
this
so
once
we've
done
a
POC
have
some
architecture
on
how
this
will
work.
Who
can
engage
both
the
networking
folks,
as
well
as
sig
note,
present
to
them
or
they're
planning
to
do
and
have
their
feedback
before
you
see
down
into
the
footing
limitation.
So
at
the
toc
level,
if
we
agree
between
as
what
we
need
to
do,
then
we
can
get.
You
know
approval
from
the
greater
community
and
in
terms
of
what
the
best
way
to
or
if
our
implementation
is
sufficient.
There.
B
A
B
Should
I
can
give
you
like
a
quick
short
list
of
the
ideas
on
what
happen
that
is?
Okay,
oh
I
can
hold
it.
Let
me
know,
cancel
the
tour
isandro
Michael
on
you
and
you
can
guys
go
go
for
so
they
mail.
Oh,
the
other
thing
is
even
if
we
get
the
mail
update,
we
can
still
use
obvious
and
again
with
the
other.
Salts
network
means
basic
stuff,
so
we
can
deter
implementation
with
the
obvious
bridges.
So
it's
not
a
huge
issue
for
us.
Okay,.
A
You
know
this
is
little
bit
update.
Alessandra.
Thank
you
for
thank
you
for
for
sending
that.
Thank
you
for
so
for
investigating
this,
and
for
and
letting
us
know
all
the
things
I've
gone
on
here.
I
love
to
you
know
we'll
continue
on
this,
both
on
the
Microsoft
front
end
and
with
you
guys
and
see.
If
we
can
make
some
progress
here
and
find
the
solution
that
works
for
everybody,
so.
D
To
chime
in
on
the
multiple
containers
per
pod,
my
impression
from
some
of
what
Microsoft,
but
it
build
last
month,
was
that
they're
aware
of
that
limitation,
and
it
sounded
like
they're
trying
to
address
it
for
the
next
Windows
10
and
Windows
Server
updates
that
are
coming.
This
fall
so
I
shared
a
link
to
a
presentation,
and
it
says
something
about
initial
support
for
sharing
network
interfaces
between
containers.
D
A
Yeah
Jason
Jason
from
Microsoft
awk
about
this
extensively
and
they're.
You
know
the
limitations
and
timeline
for
one
day
will
deliver
them.
They've
never
been
super
clear
about
it,
just
because
sometimes
they
don't
even
know,
but
they
are
aware
of
the
problem.
So
now,
if
you
can
give
them
more
specifics
in
terms
of
what
what
we
what
happened
here
and
what
we
need,
maybe
they
can
give
us
a
little
bit
better
timeline
understand
one
day
when
our
delivered
this.
B
Is
we
could
probably
implemented?
Probably
I
know
if
we
have
two
people
to
do
it,
because
we're
still
straight
a
bit
thin,
because
we
have
to
release
obvious
2.7,
but
it's
definitely
doable
with
proposal.
We
have
a
camp.
So
that's
why
I
need
to
think
with
other
Sundra
to
see
if
we
should
invest
a
lot
in
into
that
idea.
B
A
E
I've
been
on
some
other
stuff
recently,
but
I
have
been
working
on
the
young
boring
document
getting
that
pored
over
to
something
that
we
can
have
public
for
the
community
to
update
and
and
use
for.
You
know
getting
on
board
and
just
kind
of
lightly,
investigating
the
D
multiple
for
container
for
positing
and
and
I'd
I'd
love
to
be
involved
with
in
any
the
conversation
or
show
me
what
you
have
and,
and
maybe
I
can
move
forward
with
it
as
well.
I.