►
From YouTube: Kubernetes SIG Windows 20180710
Description
Kubernetes SIG Windows 20180710
A
A
We
were
expecting
some
changes
around
implementing
DNS
through
CNI
and
mod
on
and
Alan
you're
going
to
be
working
on
that
and
then
I
had
sent
out
a
link.
You
know
it's
a
high-level
proposal
of
of
what
features
would
be
available
for
for
GA
and
what
would
be
in
alpha
and
beta
afterwards
and
so
I
guess,
let's
start
with
with
the
DNS.
B
C
A
B
A
Okay,
I
did
figure
out
that
we
can
still
deploy
when
CNI
using
ACS
engine.
If
you
want
to
play
this
on
Azure,
if
you
basically
go
in
there
and
set
the
in
the
before
you
pass
into
ACS
engine,
there's
an
Orchestrator
option
where
you
can
tell
to
use
cube
net
and
that
will
actually
go
ahead
and
use
your
wind
C&I
code
on
the
windows
nodes.
A
A
A
A
And
I'm
sort
of
an
expert
based
there
is
no
we're
still
working
on
the
upstream
testing.
There
was
a
CNI
problem
that
we
were
hitting
with
the
azure
CNI,
so
I'm,
working
with
without
Elena
and
and
others
to
get
that
resolved,
because
that
was
causing
a
pretty
high
failure
rate
and
their
conformance
tests.
A
A
C
So
novo
for
the
DNS
we
fight
it,
we
out
the
configuration.
So
it's
everything
this
for
inverter,
we
updated
the
empty
you,
so
you
can
no
longer
need
to
go
inside
that
container
and
lower
than
tu
is
done
automatically
via
the
configuration
as
well.
Okay,
good
I'm,
still
working
on
the
hyper-v
one
for
writing.
All
free
I
mean
maybe
half
of
water
water.
One
are
interested
on
1803.
We
couldn't
fetch
the
enabled
extension
on
the
a
channel
switch.
C
D
So
it's
1803
when
you
try
to
enable
destination
it.
Actually,
it
doesn't
say
that
it
gets
in
a
ballistic,
says
that
it's
enabled
on
false
and
that
we
couldn't
find
a
way
to
see
if
they
enable
it's
running.
Okay,
even
though
it
is
running
it,
it's
enabled
everything
works,
but
you
cannot
see
it
from
my
channels
that
enable
the
extension
enabled
okay.
E
A
E
A
response,
but
that
should
help
with
a
lot
of
networking
problems
and
then
on
ACS
engine
I
know
Madan
likes
the
or
checked
in
some
code
pradesh.
You
were
the
first
pod
scheduled
on
a
Windows.
Node
has
no
connectivity
so
that
that
should
be
fixed
with
the
next
ACS
engine
binary
release
or
if
you
build
it
from
source
now,
that
should
also
not
be
an
issue
anymore.
Oh.