►
From YouTube: Kubernetes SIG Windows 20181016
Description
Kubernetes SIG Windows 20181016
B
A
C
C
You
know,
in
a
matter
of
the
next
week
or
two
before
that's
ready
again
and
then
the
other
thing
that
I've
been
doing
related
to
that
is
I've
basically
been
trying
to
collect
all
the
different
tasks
that
were
needed
in
order
to
move
to
Server
2019
and
a
nerdy
cut
that
a
project
board
listed
there,
then
we've
got
cubic
on
coming
up.
Anybody
have
any
other,
because
you
want
to
add
for
today.
C
E
E
Argument
not
os3
strong
and
it's
actually
used
for
a
couple
of
tests
as
well
like
if
it's
debian
or
if
it's
anything
else,
it's
gonna
skip
some
tests.
We
can
use
the
same
mechanism
for
Windows
as
well
and
a
couple
of
scenarios
in
which
some
tests
are
trying
to
to
spawn
some
containers,
which
are
incompatible
with
how
it
is
at
the
moment
like
spawning
with
the
SC
Linux
options
or
trying
to
run
with
you
idea
or
a
JD
on
Windows
or
transform
some
specific
Linux
containers,
images
on
windows
so
on
and
so
forth.
D
But
this
way
we
can
just
say
confirm,
run
conformance
no
performance
and
it
was
given
all
automatically
so
there's
no,
no
huge
skip
test
regex.
We
we
need
so
far
and
if
I'm
not
mistaken
with
this
patch
I
think
we
can
also
but
correct
me
if
I'm
wrong
value,
I'm
referring
to
same
thing,
we
can
also
have
conditions
inside
the
test.
F
G
G
E
D
C
D
B
E
C
B
C
D
E
Should
cover
almost
all
of
the
conformance
once
okay
I
haven't
taken
a
look
at
the
full
run,
because
there
will
be
a
lot
more
in
that
on
the
site,
but
this
conformity
should
be
almost
all
down.
I'll
double
check
to
see
if
any
other
new
tests
were
added,
which
cannot
for
Windows
should
be
most
of
it.
D
E
E
D
For
the
stability
issues
we
we
were
having
with
triangle
which
to
properly
apply
that
that
states,
because
darker
basically
doesn't
want
to
start
after
it
with
trying
to
see
how
we
can
let's
say
for
starting
or
figure
out
the
issue
for
that
one.
Basically,
after
a
reboot
doctor,
won't
start
and
there's
a
SS
engine
issue.
For
that
and
correct
me
if
I'm
wrong,
I
think
you
referenced
another
issue
into
that
issues.
So
probably.
D
A
C
A
C
The
logs
said
that
the
service
wasn't
ready
after
30
seconds,
and
we
talked
to
the
National
Knight
earlier
today
and
he's
thing
said
since
the
patch
is
still
installing
right
after
Windows
comes
up.
If
that,
if
the
Windows
networking
services
and
ready,
then
docker
may
hang
for
some
time
waiting
on
that.
A
A
A
A
A
Another
option
is:
maybe
our
services
like
for
the
cubelet
can
depend
on
doctor
who,
just
if
I
remember
correctly,
does
depend
and
then
our
service
can
have
a
delay
start
and
then
it
will
force
doctor
to
start
on
its
own
like
two
minutes
later,
for
example.
So
that's
an
option
you
can
do.
We
don't
have
to
notify
the
doctor
service.
It
just
works.
A
C
C
H
Sure
yeah,
so
we've
been
trying
to
make
some
progress
on
the
testing
and
jce
and
Peters
doing
the
the
majority
of
work.
But
I
created
a
cluster
manually
using
the
Peters
guide
and
I
ran
the
III
test
against
it.
So
I
thought
I
would
share
with
everyone
about
on
the
dock
and
see
like
the
set
of
tests
that
actually
passed
versus
failed,
so
I
didn't
skip
any
tests
and
I
ran
conformance
and
no
components
tests.
So
just
as
a
reference
point,
if
anyone
is
interested
in
the
King,
the
results
are
in
the
doc.
D
H
B
Then
I
look
at
the
network
test,
at
least
I
think
the
DNS
ones
we
are.
We
understand
the
issue
and
we
are
going
to
go
to
Signet
work
with
the
understanding
how
why
Linux
has
done
that
way.
But
there
is
a
patch
that
Adaline,
like
the
Adalind,
did
where
the
last
four
tests
related
to
intro
to
pod
communication.
Note
the
pod
communication.
They
were
requiring
the
host
network
in
the
test.
I
H
I
H
D
H
D
C
D
C
D
H
D
C
Okay,
excellent
yeah,
thanks
for
sharing
that
and
if
you
have
any
other
questions
on
that,
you
know
be
sure
to
to
ping
us
around
the
Sigma
additional
and
be
great
to
compare
the
results
there
mm-hmm
and
then
this
is
using
a
GC,
specific
plugin.
That
Peter
was
working
on
for
the
networking
right
now.
H
C
B
I
E
I
E
C
Through
the
work
that
I
was
doing
to
bring
up
Windows,
Server,
2000,
19
and
container
D
on
India's,
your
environment
and
I,
basically
put
all
that
into
one
project
board
I'm
using
to
get
work
signed
out
to
multiple
people,
and
so
the
stuff
related
to
you
know.
Acs
engine
is
basically
work
items
that
are
specific
to
how
we're
deploying
to
things
on
donnager,
but
all
the
other
compliance
performance
blockers
are
in
there
as
well.
So
I've
got
a
list
of
everything.
C
Yes,
if
anyone
else
would
like
to
you
know,
you
know
work
with
me
and
start
adding
more.
You
know
windows
feature
specific
tests
like
I'm,
not
looking
for
things
that
test
Windows
differently
from
Linux,
but
what
I
want
to
do
are
add
more
tests
that
are,
you
know,
targeted
to
be
run
on
Windows,
so
that
we
can
start
looking
for
some
of
the
potential
stability
problems
that
that
we've
been
that
we've
been
hitting.
C
You
know
that
James
has
been
adding
a
few
of
those
over
on
the
ACS
Engine
side
as
well,
but
I
think
we
should
probably
start
getting
some
of
those
into
the
kubernetes
repo
and
then
in
the
work
under
engineering
blockers
are
over
there.
That's,
basically
the
things
that
are
needed
for
us
to
get
this
little
test
pass
up
running
with
a
nerdy,
and
so
some
of
those
are
things
like
you
know.
Getting
the
container
D
builds
fixed
daily.
C
For
the
kubernetes
branch
as
well,
so
what
I
think
we're
going
to
do
is
just
like
how
Italy
has
been
collecting
all
of
the
test
fixes
in
that
branch
that
I
have
listed
there.
We're
probably
going
to
do
the
same
thing
for
met
ease
where
we
have
something:
that's
basically
taking
all
the
PRS
that
we're
waiting
on
to
merge,
put
them
into
the
same
branch
and
then
build
it.
So
we
can
at
least
measure
whether
each
successive
PR
is
continuing
to
fix
tests
right
and
not
cause
cause
other
problems.
C
C
So,
if
there's
anything
that
that
any
would
like
would
like
to
help
on
or
if
you
want
need
any
other
items
of
sign,
you
know
please,
please
just
know,
but
right
now.
My
biggest
concern
is
that
when
it
comes
to
stability
bugs
since
we
don't
have
any
test
cases
that
can
hit
these
you're
consistently
every
time,
it's
really
hard
for
us
to
know
whether
or
not
we've
actually
fixed
those
problems
and
then
in
like
YouTube
when
you're
testing
over
on
GCE.
C
C
C
Very
cool
men
in
Seattle,
I'm
gonna
do
a
quick
one
on
the
developer
experience
along
with
one
of
our
developer
advocates
Jessica
Dean,
but
that
one
we're
gonna
try
to
focus
on
the
higher
level
stuff
like
draft
and
how
so
it
was
got
any.
You
know,
suggestions
on
things
I'd
like
to
see
in
those
talks
forever.
G
B
G
For
that
one
then
recently,
and
as
part
of
that,
actually
we
also
thought
the
approvers
lists
updated
to
such
that
think
for
a
coup
proxy
for
the
window.
Specific
coup,
proxy
binary,
Ganesh,
Madonna
and
Peng
PHA
are
the
approvers
and
reviewers.
Now,
hopefully,
that
will
accelerate
like
any
future
fixes
that
we
need
to
approve
and
get
merged
by
the
right
people,
but
that's
good
to
see,
and
then
the
other
fix
that
also
went
in
is
port
mapping.