►
From YouTube: Kubernetes SIG Windows 20171212
Description
Kubernetes SIG Windows 20171212
A
A
That's
gonna
give
us
a
demo
of
Aviano
vs
using
sig
windows
against
1.9,
so
the
last
week
we
had
a
tremendous
presence
at
the
kuba
con
conference.
There
pretty
much
a
lot
of
the
folks
on
the
call
now
Patrick
Robert
myself,
a
few
more
other
folks
who
Ticket
Master
were
there
and
we
did
have
a
meeting.
An
unofficial
meeting
with
about
40-plus
members
of
the
community
excitement
was
really
high.
A
Getting
Windows
Server
containers
into
the
kubernetes
ecosystem
as
a
beta,
our
documentation
is,
is
close
to
to
be
to
being
complete
and
we're
also
featured
that
a
couple
of
the
keynotes
who
are
dimensioned
the
excitement
and
as
well
as
the
features
coming
out
of
adam
our
sig.
We
actually
also
have
a
blog
post
that
will
likely
get
released
sometime
this
week.
A
It's
basically
going
to
highlight
some
of
the
features
that
you
have
around
networking
or
cni
plug-ins
config
map,
secret
volumes,
the
cube,
ADM
work
and,
and
all
of
that
so
overall
you
know.
There's
a
lot
of
features
are
coming
in
and
we
also
have
a
lot
of
work
cut
out
for
us
before
we
go
GA.
A
lot
of
customers
actually
asked.
A
We
need
to
figure
out
and
deploy
a
CI,
CD
and
end-to-end
test
pipeline
for
Windows
Server
containers
so
can
actually
catch
regressions
and
make
sure
that
our
code
is
also
well
tested
and
then
the
last
part
is
kind
of
producing
a
lot
of
documentation
around.
You
know
how
do
you
get
sick
windows
and
windows,
server
containers
on
different
cloud
providers
on
bare
metal,
everything
from
build
instructions?
Step-By-Step
deployment
as
well
as
you
know,
completing
some
of
the
cni
work.
A
That's
in
the
pipeline,
so
you
guys
are
well
aware
the
flannel
PR
it's
still
pending,
so
so
we're
hoping
that
that's
gonna
get
completed
then
from
the
ovn
obvious
thumbprint.
There's
a
couple
of
things
that
are
gonna
come
in
the
first
one
is:
we
are
gonna,
have
support
for
kubernetes
network
policies
as
well
as
a
novia
novia
solution
without
overlays,
so
the
scrubby
CNI
without
amélie's.
So
so,
overall,
there's
a
tremendous
amount
of
things
happening
and
continuing
to
happen
on
the
networking
stack
as
well.
A
As
you
know,
a
few
other
things
that
were
kind
of
tighten
up
the
the
overall
feature
from
from
the
seek
perspective
now,
with
respect
with
1.9,
have
some
unfortunate
news.
There
is
a
PR
that
Wenning
not
too
long
ago.
The
broke
cube
proxy
on
Windows
and
Patrick
I
see
CG
on
the
on
the
channel
in
slack
on
this
as
well.
A
So
essentially,
the
the
bug
is
preventing
cube
proxy
from
from
starting
up
in
in
kernel
space,
and
we
do
have
a
fix
that
this
thing
worked
on
and
Bob
is
validating
the
fix,
but
you
know
we're
running
up
against
the
wall
for
this
and
I
honestly,
don't
know
if
they're
gonna
allow
this
to
be
cherry
picked
or
not,
but
as
soon
as
I
have
more
details,
I'll
a
lab
did
the
sig
channel
as
well.
Ok,.
B
So
I
took
a
look
at
that
because
we
originally
opened
the
issue
prior
to
cube
Con
and
I
thought
that
George
and
Microsoft
already
had
a
PR
out
for
it
was
that
not
the
full
issue
yeah?
No,
that's
the
peer
that
hasn't
merged
in
correct
okay,
so
it's
in
master,
Bernard
and
great
upgrade
no
I
know
it
wasn't
merged
all
week.
Yeah.
A
A
So
have
the
release,
manager
and
Tony
on
there
on
the
thread,
so
he's
the
one:
that's
tracking
all
these
things:
okay,
so
basically
their
their
reply.
Literally
he
just
I'm
talking
to
him
right
now,
he's
saying
that
he
shouldn't
hold
the
1.9
train,
but
he
says
if
it's
ready
to
merge
before
the
train
leaves
he'll,
allow
it
so
he's
saying
if
we
can
get
him
merged
by
end
of
today,
he'll
he'll
get
it
in.
So
can
we
open
a
trick?
You
guys
scared
with
Madden
as
well.
A
D
A
D
D
D
B
D
A
A
A
B
B
D
A
So
so
I
didn't
have
any
slides
last
week.
I
could
be
gone
so
so
I
didn't
let
you
know
that
the
discussion
we
had
was
more
of
an
open-ended
discussion
who
had
you
know
talking
to
people.
I
opened
up
a
road
map
document,
the
one
that's
linked
on
sip
windows,
it's
one
of
the
print
documents
and
then
we
just
walk
people
through
that
and
talk
to
them.
There
was
nothing
specific
to
that.
A
E
A
F
So
for
this
deployment
we've
seen
a
lot
of
deployments
using
dot
providers
for
this
one.
We
chose
to
do
it
locally
on
premise,
so
I
have
here
four
nodes
running
on
my
laptop
I:
have
two
linux
nodes:
Ubuntu
1604
and
two
windows
nodes,
one
window
stable
version
and
the
other
one.
It's
Windows
latest
version,
one
709.
F
You
know
had
the
nodes
I
deployed
kubernetes,
one
that
9.0
beta
2
as
the
classical
deployment
I
have
the
tunnel
between
the
hosts
of
the
cluster
using
unit
type
and
I
have
no
pots
created
at
the
moment.
I
have
here
prepared
or
religious
a
few
Jason
and
Yammer
files
in
the
pods
I'm
just
gonna
go
ahead
and
create
the
Apache
service.
First.
F
F
E
F
F
D
F
A
F
F
F
F
F
G
A
F
It's
a
bit
weird!
Okay,
you
cannot
do
invoke
web
requests
and
access
the
local
host
from
any
containers
inside
the
pod
and
to
show
that
as
well.
Since
there
is
only
one
endpoint
created
for
the
pod,
there
will
be
only
one
port
inside
of
yes,
so
this
is
the
port
which
will
correspond
to
all
the
containers
running
inside
that
pod.
So
this
is
the
port
per
pod.
F
D
D
A
F
Another
cool
thing
that
you
are
able
to
do
so
you
can
create
as
well
VMs
so
I
have
here.
A
VM
I
created
an
open
to
1604
inside
hyper-v
and
I
attached
it
to
the
little
switch
on
which
open
V
switch
is
running
then
I
added
the
port,
then
I
could,
at
the
port
obvious
and
put
it
inside
of
Ian's
controller.
So
I
have
the
IP
from
inside
the
cluster
eyepiece
I
have
from
inside
the
VN
access
to
the
cluster
resources.
So,
for
example,
I
can
pick
the
master,
node
and
I
can
as
well.
F
F
F
F
F
D
D
F
F
A
D
So
basically,
whatever
change
you
made
is
directly
on
on
top
of
that
node
similar
for
DMS,
the
jnanis
request
will
never
get
out
if
it's
used
from
us,
so
it's
basically
a
distributed.
E&Amp;S,
you
don't
need
another
process
which
actually
gets
the
request
and
response,
and
so
on.
It's
just
another
floor
rule
applied
on
top
of
that
controller.
It
will
catch
the
DNS
requests
and
just
being
pushed
directly
back.
It's
similar
what
we
do
for
DHCP
as
well,
although
kubernetes
dozens
use
DHCP,
but
this
term
is
use
case
for
Apple
stock,
for
example,.
A
Very
cool,
alright,
so
running
close
to
to
time
as
well.
So
we'll
have
to
hear
more
about
the
network
policies
next
week
a
link,
so
we
can
do
follow-up
on
that
Robert.
We
didn't
have
that
email
from
from
Chris
on
you
know
the
pod,
selectors
and
labels
I
did
not
forget
about
that.
We'll
discuss
it
possibly
next!
Next,
next
meeting,
like
you
know,
it's
not
gonna,
be
an
easy
problem
to
solve.
So,
let's
figure
out
to
do
this
right.
F
D
F
I'm
excited
already
so
I
create
the
policy.
I
couldn't
think
I
deleted,
it
I
can
think
again,
I
created
it
I
couldn't
think
again
and
I
deleted
it.
That
could
be
again.
The
pod
and
cool
thing
is
that
this
does
not
the
coop
Roxy.
So
the
only
thing
that
it
requires
on
the
windows,
node
is
the
oven
controller.
D
A
These
awesome
to
see
you
know
obviously
great
progress
across
the
board
for
both
with
audacity
and
without
especially
the
support
for
network
policies.
So
I
will
get
the
documented
and
make
it
out
to
folks
I
will
thank
you.
Everyone
for
attending
and
I
will
see
you
guys
in
a
couple
of
weeks.
Patrick
will
follow
up
on
the
Q
proxy
PR
in
this
lecture
now,
so
you
mentioned
that
George
would
be
so
so
follow
up
that
there.