►
From YouTube: Kubernetes SIG Windows 20180911
Description
Kubernetes SIG Windows 20180911
A
Right
thanks
around
for
joining
this
September
11th
for
the
weekly
sig
windows.
Sync
up,
so
I've
got
a
few
status
updates
that
I
put
on
the
agenda.
If
anybody
has
anything
else,
I
just
go
ahead
and
either
add
them
or
just
drop
a
drop.
A
note
in
the
chat
window
and
I'll
be
sure
to
to
get
to
you
in
a
minute.
A
So
I
think
the
first
thing
I
wanted
to
to
talk
about
was
actually
the
road
map
over
on
not
on
Trello,
so
I
haven't
been
I've,
been
trying
to
update
that.
Basically
before
we
start
each
milestone,
and
so
I
thought
it
would,
since
we're
in
code
freeze
for
12
I
thought
it
would
be
good
to
go
ahead
and
pull
this
out,
so
we
can
talk
about
it
for
version
13.
A
A
So
the
you
know
a
couple
weeks
ago,
as
we
were
entering
feature
freeze,
we
had
the
discussion
around
the
stability
and
test
progress
and
decided
that
we
weren't
going
to
be
able
to
meet
the
GA
criteria
for
12,
and
so
what
I
want
to
do
is
really
folk
focus
13
on
just
getting
that
stability.
In
closing
those
last
issues
that
we
need
in
order
to
in
order
to
get
stable
and
within
the
community,
and
so
I
I'd
like
to
propose,
is
basically
not
doing
any
of
the
specific
feature.
A
B
A
And
so
over
here,
at
Microsoft
and
I'm,
talking
to
my
manager,
a
few
other
people
and
I'm
trying
to
get
a
few
developers
they're
more
familiar
with
the
Linux
side
to
at
least
step
in
and
Store
start
letting
some
more
help
to
this,
so
that
we
can
better
understand
why
why
things
are
failing
here
and
I'll,
get
back
to
notes
in
minute
we
can
I
can
try
to
show
a
couple
of
the
failures,
but
anyway,
I
think
that's
kind
of
the
focus
that
we
need
right
now
and
just
looking
at
the
incoming
issues.
I'm
github.
A
C
D
A
Good
cool
anyway,
like
this
I,
think
this
is
a
great
example
of
the
kind
of
things
that
we
need
to
be
you're,
focusing
on
fixing
right
now,
and
so
you
know,
I
took
the
stuff
that
was
incomplete
in
12
and
moved
out
to
13
and
14
the
one
area
that
I
think
we
may
need
to
do.
Some
work
is
relating
to
container
D,
and
that
was
that's
the
next
topic
that
I
had
for
today.
D
A
Yeah,
that's
where
that's!
What
we're
trying
to
get
to
the
problem
right
now
is
that
we
don't
have
the
issues
reproducible
right
now
when
you
run
a
test,
pass
windows
will
crash
and
it's
not
happening
on
the
same
test
case
every
time,
and
so
this
I'd,
like
to
dock
from
from
Adelina
and
Claudia
who've,
been
working
on
porting
the
conformance
tests,
but
this
has
got
links
to
all
the
logs
from
the
nodes
in
a
test
pass
for
several
of
the
recent
test
runs
and
so
what
you're?
Seeing
is
that
over
time?
A
The
note
the
cubelet
goes
down?
One
note
at
a
time
until
the
tests
basically
stop
running,
because
the
way
all
the
conformance
tests
are
written
is
they're
not
going
to
run
on
any
nodes
that
are
down,
and
the
other
thing
that
you'll
sometimes
see
in
these
logs
is
that
pods
will
just
stop
scheduling
or
rather
they'll
be
scheduled
to
a
node,
but
not
start,
and
so
you
know
it's
like
what
we're
looking
at
now
is
symptoms
and
it's
not
something.
A
And
so
my
my
hope
is
that
between
Audrina
Claudio
pan-fry
myself
is
that
you
know
week
by
week
we
can
get
a
couple
bugs
filed
until
we
have
a
better
handle
on
what
the
root
cause
is,
and
so,
if
anyone
else
has
ideas
on
how
to
you
know
it
address
this,
you
know
I'd
love
to
have
more
help,
and
especially,
if
anyone's
got.
You
know
another
idea
of
an
approach
to
try
to
find
this
I
mean
I.
Suppose
we
could
start
writing
tests
from
scratch,
but
I'm
kind
of
hesitant
to
do
that.
D
A
E
A
A
A
C
A
A
A
E
A
E
A
E
E
E
E
A
E
A
A
Okay,
so
the
other
thing
I
wanted
to
cover
was
we've
got.
A
group
of
developers
have
been
working
on
getting
container
D
up
and
running
on
Windows
and
they're.
Now
at
a
point
where
they
have
both
container
D
working
for
being
able
to
to
pull
and
run
Windows
containers,
and
then
they
also
have
it
working
partially
with
with
cry
control
as
well,
and
so
my
expectation
is
that,
with
probably
by
early
October,
they
should
have
something
that
is
able
to
be
is
able
to
be
tested.
A
A
A
So
in
Windows,
Server,
20,
20
19
this
they're
using
and
updated
HTS
service,
and
so,
if
you
look
at
Microsoft,
slash,
HCS
shim
repo
you'll
see
that
they
actually
have
a
slightly
different
API
endpoint
there,
one
of
the
main
things
that
they
did
for
this
release
in
Windows
Server.
And
you
know
these
changes
actually
started
in
1803.
Was
they
separated
out
the
API,
so
they
could
better
support,
creating
a
sandbox
like
we
need
for
for
kubernetes,
and
so
the
API
that
windows
all
uses
underneath
is
much
more
similar
to
to
the
CRI.
A
A
A
So
some
of
my
concern
here
is
that
you
know
if
we
try
to.
If
we
try
to
run
and
support
to
run
times,
we
may
not
be
able
to
do
it
with
with
the
number
of
people
that
we
have
available,
that
that's
what
my
concern
comes
down
to
and
if
there's
more
developers
improving
the
stability
of
container
D,
then
I
think
that
we
would
have
a
better
chance
of
success
there.
A
And
so
once
you
know,
those
tests
are
up
and
running.
I'd
like
us
to
you
know,
look
at
the
data
and
say
you
know:
does
this
make
sense
or
do
we
or
do
we
go
down
a
path
where
we're
having
to
fix
a
lot
of
bugs
they're
specific
to
dr.
shim?
And
so
you
know
at
this
point
we
don't
have
any
data,
but
but
it's
a
question
that
I
that
I'd
like
us
to
be
thinking
about
and
and
probably
make
a
decision
on
sometime
in
October
once
we
have
test
results
in
hand.
D
C
D
E
D
A
C
C
C
A
G
A
C
A
C
I,
don't
know
what
has
costed
I,
don't
I
do
know
that
it
has
reliably
worked
on.
Current
Internet
is
110,
and
since
then,
we've
had
some
code
changes
to
our
startup
scripts
and
obviously
the
kubernetes
versions
have
changed
as
well.
I
think
there's
something
that
happened
in
recent
final
PRS
that
went
in
well.