►
From YouTube: Kubernetes SIG Windows 20190528
Description
Kubernetes SIG Windows 20190528
A
So
you
know
we
gave
like
a
cig
status,
update
that
was
Michael
and
I.
If
you've
bent
these
meetings,
it
shouldn't
be
anything
new
from
the
air
was
more
bringing
up
other
people
in
the
community
up
up
up
to
date
with
what
we're
doing
and
had
almost
a
full
hour
of
Q&A.
It
was
pretty
good
and
then
John
and
I
forgot.
The
other
presenters
name
also
had
a
session
talking
about
the
CSI
storage
proposal
that
we're
still
need
to
review,
but
those
are
both
posted.
A
A
So
I
had
a
few
ideas:
I
recorded
those
in
the
in
the
list,
and
so
if
anyone's
got
feedback
on
that
I'd
love
to
hear
hear
later,
but
one
of
the
specific
things
I
wanted
to
try
to
do
sooner
was
we
also
have
some
contributors
in
in
China,
and
this
time
does
not
overlap
with
with
their
time
zone
and
so
towards
the
end
of
the
14
release.
We
had
a
weekly
I,
get
wait.
A
weekly
engineering
stand-up
meeting
that
was
happening
on
I
think
it
was
Thursday
afternoon.
C
A
A
Okay,
so
moving
forward
code
freeze
is
currently
this
Thursday
and
I
see.
There's
a
couple
specific
PRS
that
are
listed
on
here.
The
first
one
is
related
to
some
logging
improvements
and
Dinesh
and
Kalia
and
did
either
if
you
have
a
chance
to
look
at
that
and
I
know
that
a
few
weeks
ago,
there's
that
deny
should
mention
that
that
he
might
be
able
to
have
someone
on
his
team.
Do
that,
but
I
don't
know
if
it
was
ever
confirmed.
A
A
B
A
E
E
E
It's
like
slash
package
util
in
it
system,
so
it
uses
there's
some
review
comments
from
Luba
Mayer
on
that,
but
I
need
to
address
and
I'll
do
that
tomorrow,
but
that
vendors
in
a
golang
library
for
Windows
service
manager,
so
I
think
we
already
have
a
parents
dependency,
but
we
need
the
child
ones
so
that
one
gets
updated
in
there.
So
that
needs
to
be
approved
as
well.
So.
A
E
A
E
I'm
have
a
PR
out.
That's
total
like
work
in
progress
right
now,
but
that's
gonna
handle
the
cute
proxy
retry
when
the
H&S
network
or
if
the
HS
network
goes
away.
So
mother
made
some
review
comments.
I
didn't
have
a
time
to
polish
it
so
I'm
back
in
office
tomorrow.
So
I'll
look
at
that,
but
there's
no
dependency
change
there,
so
it'll
be
reviewed
pretty
quickly.
I
just
need
to
finish
it
I.
E
A
A
E
A
A
C
A
C
A
C
A
A
D
F
A
Okay,
but
yeah
I
haven't
seen
this
dis
failure
and
the
azure
runs
so
far,
but
I
guess
call
you
if
you
happen
to
see
this
one
be
sure
to
a
lot
lot
to
Nash
know
too.
So
that
way
we
can
look
at
look
at
those
ones
held
up
or
basically
get
a
cluster
held
on
Azure
for
investigation.
If
we
had
it
there
and.
D
C
D
That
issue
was
definitely
fixed
bloody.
This
one
is
sliced
typically
saying
it's
like
it
felt
like
a
heap
corruption,
where
we
have
a
namespace
entry
at
the
beginning
of
a
function
and
then
at
the
later
of
the
function
it
was
having
null
value.
So
that's
that's
where
I
stopped
it,
so
we
were
trying
to
do
you
do
lot
of
local
runs
to
reproduce
you
I
thought
Nathan
is
going
to
give
a
private
with
some
additional
logging
to
find
out
if
what's
happening.