►
From YouTube: Kubernetes SIG Windows 20180130
Description
Kubernetes SIG Windows 20180130
A
Hello,
everyone
and
welcome
to
another
sick
windows
meeting
I.
Thank
you
all
for
attending
I.
Don't
have
a
lot
of
updates
today.
I'll
go
ahead
and
update
the
cornelian
distances,
I'm
aware
of
and
then
Patrick
and
others
can
also
give
their
updates.
So
first,
let
me
start
begin.
My
apologies
to
gently
I
took
me
a
couple
of
extra
days
to
go
through
a
couple
of
the
PRS
that
he's
emitted
like,
for
example,
the
VMware
fusion
bug,
with
with
the
get
extended
memory,
IX
called
I
was
that
was
failing
as
well
as
the
well.
A
That
was
a
good
physically
installed
system
memory,
failure
and
then
also
there
was
an
additional
PR
around
the
ability
to
add
hyper-v
containers
support.
So
I
proved
both
of
those
peers
earlier
today,
so
they're
good
to
go
I
believe
they
should
be
ready
to
merge
if
they
need
additional
retesting
or
rebasing,
then
you
know
obviously
monitor
that
closely
and
get
them
through.
So
you
know,
you
know
amazing
work
Pat
recently
in
the
team
to
get
this
out.
That's
you
know
pretty
good
progress
to
get
us
started
on
the
one-to-ten
train.
A
B
B
A
D
So
for
the
week,
as
we
begin
make
that
into
the
agenda,
because
a
few
more
topics
to
discuss
and
that
delayed
our
topic
saw
the
green
world
discuss
the
window
CRI
in
the
agenda
at
meeting
today,
and
we
are
trying
to
present
our
revised
detector
problem.
There's
only
the
CPU
and
memory
resources
and
the
first
step.
D
Besides
that,
I
think
compared
also
has
five
feature
requests
on
the
upstream,
so
that
we
can
officially
add
this
as
feature
before
the
feature
deadline
locks
down
besides
that
also
yeah,
as
micro
has
said,
the
high
PB
work
is
quite
related
to
the
CRI,
which
could
utilize
the
resource
control
in
a
CI.
Pom
file
has
the
Sameer
first
PR
of
that.
D
D
D
A
D
A
D
C
C
C
Okay,
I'll
double-check-
on
that,
okay,
so
stuff
I
want
to
check
or
a
quick
was
under
under
coab
one
down
nine
there
were,
there
were
for
release,
sorry
for
items
there
on
the
Trello
board
and
just
starting
for
the
top
one
of
them
was
was
windows.
Node
cannot
access
services
using
a
service
IP,
I'm
actually
trying
to
test
that
along
with
Jason
right
now,
because
I
had
a
demo
that
was
broken
by
that
and
so
I'm
trying
to
update
that.
But
that's
just
a
windows
only
change,
so
that
was
also
that
yeah.
C
That
was
the
DNS
query
one.
So
there
was
one
that
issue
that
we
had
marked
and
it
looks
like
Robert
just
updated
it,
but
before
one
point
nine
was
released.
We
had
a
problem
where
wasn't
getting
the
right
windows
version.
I'll
put
the
copy.
The
pull
request
in
that
channel
here,
but
I
think
this
is
one
that
we
may
need
to
get
a
reviewer.
C
B
C
C
Okay,
okay,
cool
all
right.
That
was
the
main
thing
I
wanted
to
check
on
on
just
on
those,
so
otherwise
I'm
still
trying
to
check
out
these
network.
This
network
issues
with
Jason
and
I'm,
hoping
that
they
will
be
able
to
share
more
about
that,
because
I
know
we've
got
to
get
a
patch
in
testing
I.
Just
you
know
we
can't.
We
can't
give
a
date
for
when
it's
out
and
tell
us
out,
but
at
least
we're
testing
that
one
internal
you
know
that's
been
a
problem
on
from
customers
on
149
and
which.
E
C
C
C
So
I
think
I've
got
yeah.
I've
got
that
on
the
or
at
least
I
thought
I
had
down
in
DNS
one,
but
anyway,
okay,
that
cell,
all
that
I
had
for
today
I'm
still
in
the
discussion
on
this
side
in
regards
to
bring
bringing
up
to
ETA
chest
or
we're
still
making
progress
there,
but
nothing
specific
I
can
share
yeah
I
guess
some
I
want
to
see
if
Darren
or
possibly
or
just
had
anything
that
they
wanted
to
share
about
upcoming
progress
or
not
it's
up
to
you.
F
C
F
C
G
A
Just
I
know
that
you
and
Robert
were
looking
into
going
through
all
our
instructions
and
duplicating
some
of
that
work
for
different
sea
and
ice.
You
know
anything
that
looks
that
it's
not
like
what
you
said
right,
some
knowledge
that
implied
to
just
flag
it
that
way
you
can
go
back
and
edit
that
documentation.
So,
like
turn,
you
can
send
me
a
direct
message
and
slag
and
tell
them
hey
over
here.
We're
using
these
four
or
five
acronyms
be
great
if
we
actually
expanded
on
those
and
I'll
take
care
of
that.
G
G
B
G
A
G
A
A
E
E
A
That's
something
that
at
least
in
the
past
Arlene
and
his
team
have
taken
on
and
and
I
helped
us
a
lot
in
kind
of
validating.
Some
of
the
networking
enhancements
are
happening,
Windows,
Alina,
I,
don't
know
if
that,
if
you
are
up
for,
if
you
guys
can
continue
following
that
process
with
the
new
networking
builds
that
Jason
mentioned.
A
A
B
I
wanted
to
ask
one
more
question
for
like
there's,
there's
a
good
number
of
issues
that
we
have
that
are
open
in
terms
of
sig
windows
for
kubernetes
and
I
was
curious
if
like,
if
we
had
any
sort
of
attitude
towards
like
closing
out
the
stale
issues
or
responding
to
them
as
like.
Is
there
any
advice
towards
that
because,
like
we
already
have
go
to
kind
of
like
noise,
and
so
I
wanted
to
see
about
clean
those
out
if
possible?
Is
that
like?
Would
you
have
any
advice
towards
doing
that?
A
A
A
C
We
have
one,
for
example,
it
says,
like
you,
know,
support
pada,
pada
networking
on
Windows
yeah.
We've
got
get
set
up
guidance
on
how
to
do
this,
so
it
looks
like
there's
a
slash,
close
command,
but
does
that
only
work
for
the
person
to
opens
the
issue,
or
is
that
something
where
anyone
that's
in
the
sig
that's
assigned?
You
can
close
it
I.