►
From YouTube: Kubernetes SIG Windows 20200721
Description
Kubernetes SIG Windows 20200721
A
Hello,
everybody
and
welcome
to
another
sick
windows.
Meetup
it's
the
21st
of
July
today,
as
always,
is
a
recorded
meeting.
So
please
adhere
to
the
scene
CF
code
of
conduct.
Alright,
let's
get
started.
Let
me
share
my
screen
right
before
some
of
you
joined
I
was
thinking
James
for
a
lot
of
the
work.
That's
been
doing
kind
of
shepherding
and
trying
to
get
the
Lava.
There
are
PRS
and
efforts
in
same
thing
for
for
David
as
well.
A
Adelina
Claudia,
you
all,
have
been
putting
a
tremendous
amount
of
time
trying
to
get
all
these
things
in
I've
been
pushing
sick
release
were
going
back
and
forth
on
on
quite
a
variety
of
issues,
so
kind
of
wanted
today
to
kind
of
go
through.
What's
going
on
in
119,
what's
left
and
see
what
we
need
to
apply
pressure
and
what
may
be
potentially
a
lost
cause
and
then
from
there
we'll
we'll
see
where
we
need
to
go
quick
note.
A
Next,
Tuesday
I've
invited
the
entire
team
to
give
us
a
time
on
the
Windows,
CE
and
I
will
allot
them
anywhere
between
10
to
15
minutes
or
as
part
of
the
meeting.
And
after
that,
the
first
two
meanings
of
August
Mars
will
drive
would
be
probably
on
vacation
all
right.
Let's
take
a
look
at
their
ones
for
this
week,
David
the
first
one
Windows
test
failing
without
PR.
Ninety
three
zero,
six,
three
open
up
the
PR,
the
PR
one
in
so
so
that
that
that's
it
was
merged
as
part
of
Jordan.
A
B
Test
passes
or
green
now,
since
this
first
one
ten
are.
Basically,
this
was
causing
some
of
the
some
of
the
tests
to
fail
on
the
CI.
A
test
pipeline
for
kubernetes,
especially
on
Windows
yep
I,
think,
like
pods,
couldn't
even
start
up,
basically
yeah
serious
change,
but
now
it
looks
like
if
you
go
into
the
xpr
I
think
there
was
a
written
looks
like
the
should
be
green
now
as
well.
Now
that
this
has
gone
in.
C
A
D
A
A
Ok
cool
so
so
David
I'm,
assuming
your
PR,
the
DSR
PR,
should
make
it
in
now
like
no
fingers
crossed.
So
so
here's
what
you
should
do,
folks.
Anyone
that's
waiting
for
a
PR
that
needs
to
go
in
119.
As
soon
as
it's
merch
send
me
a
message.
We
wanna
verify
back
with
with
the
release
team,
make
sure
they
made
it
in.
D
A
D
D
E
D
D
F
D
D
A
D
B
G
B
G
G
B
A
A
A
Okay,
cool,
so
I
think
we
covered
all
of
your
dates,
so
one
winning
the
no
new
privileges
fix.
That's
the
one
that
we
talked
about
earlier.
He
went
in
as
part
of
Jordan
liggett's,
updated
er
because
he
he
reversed
our
nodes,
PR
on
the
GPU
device
manager,
work
and
fix
the
CI
test
and
added
they
no
new
privileges
fixed.
So
that's
great,
we
talked
about
them
the
volume
singing
PSR,
that's
the
one
that
we
just
talked
about
a
second
ago,
then
I
didn't
call.
You
are
looking
at
the
CI
failure
that
we
just
mentioned.
C
C
I
wanted
to
get
a
sense
of
what
we
need
to
do
to
get
to
the
point
that
we
have
a
PR
blocking
or
pre
submit,
or
it
so
I.
He
said,
I
put
it
in
there.
They
forget
some
feedback.
I
was
gonna,
respond
and
but
I've
other
people
want
to
give
some
some
feedback
in
there
as
well,
be
super
useful
to
start
to
move
in
that
direction
so
that
we
can
avoid
some
of
these
breaking
changes
that
have
happened.
C
A
A
You
so
much
I
I
saw
you
mentioned
that
in
one
of
the
tickets
that
I
remember
which
ticket
it
was
but
I
completely
agree
with
you
without
having
some
more
PR
test
on
Windows,
everybody
keeps
breaking
us
left
and
right
and
we
don't
catch
it
until
later
and
we
end
up
having
to
go
through
all
this
trouble
so
very
needed.
We
discuss
this
like
a
year
ago,
maybe-
and
it
just
never
happened,
but
now
we
actually
have
to
evidence
why
this
is
needed.
A
Alright
GPU
support
kind
of
I
kind
of
mentioned
this
briefly
earlier,
not
made
of
PR
Tomales
and
others
were
fully
supporting
it,
deep
reviewed
it.
It
was
reviewed
by
signaled,
it
went
in
and
it
ended
up
having
some
issues
with
the
path,
essentially
the
previous
PR.
In
this
case
here
he
wasn't
using
a
full
path
for
for
for
Windows.
He
was
basically
using
a
relative
path
and
Windows
didn't
like
that.
A
Off
and
he
and
he
basically
can't
see
what
he
changed
since
earlier-
okay,
so
he
changed
again
and
and
basically
he
was
using
C,
Drive,
leather
and
basically
I
even
taking
the
feedback
he
shouldn't
be
using
the
C
Drive
letter.
He
needs
to
be
using
the
that
it
is.
He
changed
it.
He
should
be
using
the
Wescott
CAD
system.
Drive,
that's
why
he
changed
cool,
so
there's
two
changes
that
he
made
the
first
one
is
he
actually
puts
a
full
path
studying
we
see
dry
because
Windows
didn't
like
it
otherwise.
A
So
now,
instead
of
hard-coding
see
he's
using
all
wasted,
cut
environment
system
drive,
we
have
other
issues
in
kubernetes
and
need
to
be
fixed
around.
You
know
hard
coding
of
path,
but
the
least
is
to
alleviate
it,
and
the
second
is
a
change
that
Jordan
asked
him
to.
Basically
only
do
this,
if
your
run
time
windows
deep,
if
you
can
give
this
formal
look,
if
you
haven't
I-
think
this
should
be
good
to
go
now.
A
A
In
our
case,
post
container
doesn't
execute
any
actions
right,
so
the
run
is
username,
wouldn't
really
impact
anything.
Would
it
like
if
you
run
the
post
container
specific
identity,
with
the
run
as
username?
What
what
impact
will
it
have
I
mean
you
would
either
post
container
and
Windows
is
called
almost
a
knob
right,
so
deepening
any
thoughts
on
that
I
think.
A
E
G
A
A
A
D
D
A
D
Yeah,
basically,
less
time
spent
pulling
images,
and
especially
out
of
sync
images.
For
example,
we
constantly
have
to
rebuild
diagnose
image
because
new
versions
are
built,
a
boost
response
forth
and
Microsoft
basically
published
his
new
images.
One
was
every
month,
if
I'm
not
mistaken,
so
they
get
out
of
sync,
but
you
don't
serve.
It
doesn't
even
matter
that
much
it's.
C
A
C
D
D
A
D
A
So
so
on
as
soon
as
119
chips,
we're
gonna
have
a
meeting
when
I
look
at
these
four
or
five
PRS
that
we
just
talked
about
right
now
and
we're
gonna
push
them
through
you,
I'm
gonna
ask
everybody
to
rebase
them,
we'll
get
approvals
from
us
in
signaled,
or
whoever
else
is
needed,
and
hopefully
you'll
get
them
in
like
early
on
in
120.
So
I'll
make
sure
that
we
drive
that
so.
G
A
Completely
freeze
the
branch
and
they
open
it
up
for
120
120
merges
then
we'll
do
it,
then?
Okay,
and
when
do
you
expect
that
roughly,
like
my
end
of
this
month
of
this
month
right,
you
know
this
cherry
pick
thing
is
gonna
go
for
a
while,
probably
early,
August,
okay,
but
you
know
every
release
team
adjust
this
a
little
bit.
A
A
D
A
A
D
A
small
note,
one
thing
that
my
assign
myself
two
weeks
ago,
there
was
a
test
video
regarding
the
add
my
slices,
that
failure
has
been
fixed.
Basically,
there
were
some
issues
with
the
nginx
image
on
because
we
switch
one.
Nano
server
and
nginx
binary
had
some
issues
on
a
server,
typically
missing
dll's
as
far
as
so
forth.
Apparently,
there's
not
a
single
working
or
good
version
of
nginx
on
the
whole
internet
on
windows
and
I
basically
had
to
rebuild
it
myself
and
publish
the
damage
myself
under
my
industry.
A
G
A
G
D
You
that's
been
quite
troublesome
for
me
as
for
head
to
search
everywhere
for
one
and
what
point
that
just
gave
up.
First
of
all,
you
have
to
have
x64
binaries
on
nano
server.
You
cannot
run
32-bit
applications
on
nano
server,
so
that
was
the
biggest
hard
one,
so
I
had
to
target
64-bit
or
hit
age
4,
specifically
I'll
put
it
in
the
meeting.
D
A
You
appreciate
all
right:
everybody
well
have
a
great
rest
of
your
day
or
evening,
depending
where
you
are.
Thank
you
for
all
the
hard
work.
Folks,
great
great
release
who
had
to
you
know
container
D,
endpoint
slices
DSR.
The
work
on
CSI,
going
beta,
like
amazing,
work,
this
release.
Thank
you.
Bye.