►
From YouTube: Kubernetes SIG-Windows 20230314
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
everybody
and
welcome
to
the
March
14th
2023
iteration
of
the
kubernetes
Sig
Windows
community
meeting.
As
always,
these
meetings
are
recorded
and
uploaded
to
YouTube
so
be
sure
to
adhere
to
the
cncf
code
of
conduct
for
anybody
new
here
that
pretty
much
just
boils
down
to
be
nice
to
everybody.
Let's
get
started
with
some
announcements.
First
announcement
is
code.
Freeze
for
the
127
release
is
today
at
5,
PM
Pacific.
A
So
that's
roughly
seven
and
a
half
hours
from
now
I
believe
one
of
the
big
things
that
we're
tracking
is
our
events
in
the
Vlog
query
piano.
We
can
talk
about
that
later
in
the
agenda
section.
The
other
big
announcement
is
that
can
the
energy
1.7
that
zero
released
yesterday?
This
is
a
big
release
for
Windows.
There's
a
lot
of
Windows
functionality
in
there.
A
There's
support
for
hyperview,
isolated
containers,
there's
support
for
the
better
host
process,
containers
value,
mounting
support,
there's
support
for
cri-based
stats,
which
is
an
enhancement
that's
coming
through
Sig
node
for
the
cubelets,
it's
probably
a
lot
of
other
stuff
in
there.
So
we
follow
it.
We've
been
testing,
Sig
windows
or
all
the
segment
of
such
passes
against
kind
of
the
main
builds
of
container
deep,
so
it
should
be
stable,
but
yeah
go
check
it
out.
Everybody,
oh
pod
termination,
grace
period,
yeah
the
Pod
termination
grace
period.
A
Support
for
all
Windows
Server
based
containers
is
in
there
too,
not
just
Nano
server.
So
there's
a
yeah,
a
lot
of
updates
in
there
yeah.
A
A
We
can
either
do
it
at
Microsoft
or
we'll
figure
it
out.
We'll
talk
on
slack,
but
I
think
we
definitely
want
to
get
something
out.
Okay,.
B
A
Yeah,
that's
a
that's
a
good
idea
and
we
did
discuss
yesterday
all
right
if
there's
no
other
announcements,
I
think
today,
we'll
Mobile
off,
like
always
we'll
give
some
space.
If
there's
any
new
contributors
want
to
either
introduce
themselves
or
you
know,
share
what
they're
working
on,
say,
hi
I
think
I've
seen
pretty
much
everybody
on
the.
B
A
Okay,
we
could
go
right
into
the
agenda
Arvin
did
you
want
to
start
with
some
updates
on
the
the
Vlog
query,
yeah
sure
yeah.
C
The
the
current
issue
that
I'm
seeing
is
Jordan
wands
more
people
to
review
the
pr
in
depth,
but
it's
hard
to
figure
out
how
that
is.
Quantified
I
got
Ryan
Phillips
from
node
I
got
Renault
to
review
the
pr
I
still
haven't
seen
anything
from
from
Jordan.
He
is
worried
about
an
escape
happening
because
of
the
way
the
Windows
command
for
get
event
is
getting
constructed.
C
I
have
basically,
even
though
I
don't
fully
agree
with
some
of
the
things
that
he
wants
removed
like
he.
He
does
not
want
dots
to
be
present.
He
does
not
want
spaces
to
be
present.
These
are
all
valid
names
of
like
I,
think
in
in
not
sure
in
Windows,
but
in
Linux
you
could
have
services
with
spaces
and
dots
in
them,
but
I
was
like
okay,
let's
be
conservative
and
I
change
the
reject
to
not
account
for
all
of
that.
C
So
as
far
as
I
know,
I've
taken
care
of
all
the
comments
that
he
wants.
I,
don't
know
what
to
do
now.
I
have
a
feeling.
This
is
again
not
going
to
make
this
release
and
I,
don't
know
what
we
can
do
to
satisfy.
Joy.
B
C
I
in
general,
I,
don't
know
how
how
we
could,
how
he's
going
to
get
convinced
that
this
has
been
reviewed.
Does
he
want
like
a
hundred
more
comments
from
someone
pointing
at
things,
even
though
there
are
no
more
things
to
find
I
just
don't
know.
A
Yeah
so
arvind
and
I
were
talking
a
little
bit
in
slack
and
I
think
that
I
I
I
reviewed
this
and
I
commented
on
the
issue,
and
my
stance
was
basically
like
this
to
me
really
like
it
implements
everything
that
was
discussed
like
it
implements
the
direction
that
we
decided
to
take
during
a
cigarchitecture
call,
and
there
may
still
be
some.
You
know
issue
like
there.
It
may
not
be
perfect,
but
this
it
looks
good
enough
for
an
alpha
release.
For
me,
it's
and
the
surface
area
is
even
smaller.
A
Now
that
it's
not
like
a
proper,
it's
a
just,
an
API
that
is
only
exposed
by
the
cubelet,
not
my
kubernetes
API,
so
I
feel
like
if
it
like,
it's
probably
like
we
should
put
it
in
and
even
if
we
have
to
keep
it
in
Alpha
for
a
while
iterate
there.
A
B
B
I
mean
if
there's
a
if
there's
a,
if
there's
a
reason
to
do
it,
I'll
I'll,
do
it
I'm,
always
looking
for
reasons
to
not
go
to
meetings,
but
if
you,
if
you
feel
like
it's
gonna,
be
helpful
for
us
to
be
at
this
meeting,
then
I'm
totally
coming
I'll
probably
come.
Let
me
see,
let
me
just
make
sure
I
don't
have
it
I.
B
All
right
folks,
Sig
note
after
this.
If
anybody
wants
to
come
help
us
try
to
get
no.
A
All
right,
I
think
that
that's
enough
for
that
I
think
we're
really
just
waiting
for
her
like
approvals
for
this
to
emerge.
Does
anybody
else
have
anything
they
want
to
discuss.
B
Let's
do
it
today,
I
think
you've
been
banging
your
head
at
this
stuff
for
a
while
and
I
think
it's
a
good
opportunity
for
everybody
to
see
where
we're.
A
At
all,
right,
I
stopped
sharing.
Let
me
know
if
you
need
help
sharing
the
screen.
I
believe
it
should
be
set
up
to
the
kitchen.
D
Yep
see
my
screen:
yeah,
okay,
so
I'll
just
start
with
what
problem
we
had
when
I
downloaded.
This
version
of
you
know
code,
so
we've
been
using
in
our
like
normal
vagrant
file,
just
to
bring
up
the
cluster,
which
would
have
which
have
Linux
one
box
Linux
and
another.
Is
the
windows
right
so
control
plane
is
the
Linux
one
right
so
when
I
bring
it
up,
I
had
to
like
use
this
virtualbox
for
that
and
I
and
my
Mac.
D
If
I'll
quickly
show
you
what
exactly
it
is
right,
so
it
is,
it
is
really
the
M1
Mac,
which
is
newer
version
of
Max
and
it
it
is
Arm
based
architecture
right.
So,
when
I
downloaded
this
this,
this
code
and
I
tried
to
bring
up
the
the
cluster.
It
was
failing
for
me
because,
yes,
the
boxes
were
all
x86
boxes
and
it
was
not
possible.
So
I
tried
digging
out
how
we
can
do
that.
D
So
we
I
I
came
up
with
this
solution,
which
is
q,
a
qemu
so
which
is,
which
is
nothing
but
another
kind
of
Provider
that
we
can
use,
and
so
we
tried
you
know
having
that
in
our
code
and
if
see
if
we
can
bring
up
the
nodes
and
everything
so
what
it
says.
Okay,
do
these
three
three
steps
right,
just
install
the
qmu
and
then
and
vagrant
have
this
plugin
that
you
can
do
that
and
just
do
a
simple
thing
right,
but
these
things
like
these
three
steps,
didn't
work
for
me.
D
So
what
issues
that
we
were
facing
was
that
internally,
these
commands,
like
the
vagrant,
bring
up
for
using
these
com,
the
qmu
commands,
which
are
which
were
not
supported
and
the
conversion
of
vehicle.
So
we
tried
you
know
so
so
we
were
like
exploring
the
qamu
commands,
as
well
as
the
vagrant
support
that
we
can
do,
but
which
was
not
there
right.
So
I
raised
this
bug
on
this.
D
The
owner
of
this
vagrant
qmu,
and
we
kind
of
you
know
shared
all
whatever
you
know
we
try
different
commands
and
then
you
know
changing
the
vagrant
files.
If
we
can
support
that,
but
like
she,
she
we
were
sharing
that
information
with
her.
So
ultimately,
I
I
had
this
like
this.
This
came
up
like
so
I
shared
this.
This
command
with
her,
which
which
actually
helped
me
bringing
up
the
notes
right
so
I
was
able
to
do
the
Linux
box
and
it
was.
D
D
So
so
this
is
like
we
were,
you
know,
learning
and
and
upgrading
and-
and
you
know
supporting
that
in
the
vehicle
and
what
what
exactly
qmu
fans
that
that
you
know
she
needed
for
for
all
the
you
know
upgrade
that
we
need
to
do
so.
Yeah
I
mean
that's,
that's
what
I.
D
Yeah
she
had
to
yeah
because
she
had
to
upgrade
this,
the
plug-in
that
we
I
was
using
zero
three
three
and
she
had
to
upgrade
that
to
support
the
the
boxes
that
we
have
right
and
yeah.
So
yeah
I
mean
I
I,
whatever
I
found
in
terms
of
the
commands
and
and
support
in
the
background
and
everything
I
have
it
now
in
this.
D
If
you
want
to
really,
you
know
quickly,
go
through
it,
it's
now,
not
the
you
know,
background
provider
is
not
the
virtual
box,
but
rather
it
is
now
qemu
and
you
know,
as
per
the
boxes,
that
that
we
digged
up
on
or
whatever
was
needed,
to
bring
them
up.
I
have
those
configuration
now
in
it
and
I
just
wanted
to
like,
like
quickly
show
I
I
mean
if
you
want
I,
can
destroy
and
do
that
again,
but
yeah.
This
is
right
now
the
status,
that's
both
the
nodes
are
up.
I.
D
B
I
think
I'm
going
to
test
it.
A
lot
of
other
people
will
too
so
for
folks
that
are
new
to
this.
Just
in
the
five
seconds,
as
you
know,
Sig
Windows
devtools
runs
off
virtualbox.
That
only
runs
on
x86.
We
looked
at
everything
terraform
all
these
different
things,
and
the
only
thing
was
this
qemu
idea.
Arvind
actually
originally
had
that
idea,
I
think
because
it
emulates
instead
of
it.
D
B
M2S
and
M1
Max
so
looks
like
now.
We
do
have
a
Windows
kublet
virtualization
solution
that
doesn't
cost
us
any
money
that
anybody
can
possibly
use,
which
will
be
using
qemu
to
to
build,
build
VMS
on
arm
or
whatever.
So
that's
the
whole
idea
so
huge.
This
we've
been
fighting
with
this
problem
for
like
almost
a
year
now,
so
thanks.
Thank
you
so
much
pramita
for
struggling
through
all
these
issues
and
everything
yeah.
D
Yeah,
because
on
the
internet,
if
you,
if
you'll
you
know
search
if
you
have
to
bring
it
up,
it
just
says:
okay,
these
three
three
commands
are
enough
for
you
to
bring
up,
but
it's
not
that
you
know
easy,
because
you
have
to
like
really
go
through
all
the
commands
it
is,
it
is
internally
using
and
then
the
whole
support
of
vagrant
is
also
not
there.
So
yeah
I
mean
that's
what
I
did.
B
D
Yeah,
so
this
is
the
control
plane
that
I
this
is
and
that's
the
windows
is.
B
C
Yeah
sure
this
is
great
news
for
me
that,
like
thanks
for
doing
this
work,
a
couple
of
follow-up
questions,
so
does
this
mean
we
could
just
use
Wagram
up
with
the
qmu
provider,
or
do
we
need
to
run
qmu
separately.
D
The
provider
I
think
that's
that's
what
I
was
I
was
telling
you
that
I
can
do
that.
Okay,
so
basically,
let
me
just
go
out
so
yeah.
Just
just
do
this.
Now
it
has
its
own
support
just
to
vagrant
up
and
then
hyphen.
C
Excellent
and
what
is
the,
what
is
the
windows
image
that
we
are
using?
Is
this
the
one
that
I
mean.
D
Sure
so
yeah
so
right
now,
so
basically
that
issues
that
we
were
facing
was
you
know,
doing
an
SSH
and,
and
you
know,
giving
IEP
to
those
nodes
right
so
that
now
these
all
things
are
fixed
right.
So
you
you
can,
you
know,
could
really
go
SS
engine
and
run
your
scripts
over
it.
So
now
I
need
your
support.
You
know
people
to
try
it
and
if,
if
something
in
failing
inside
that
VM
you
can
you
can
fix
that
right.
D
It's
just
a
matter
of
Googling
and
just
fixing
our
script,
that
that's
we've
been
doing
right,
but
but
earlier
it
earlier,
it
was
it
was.
It
was
not
that
the
VMS
were
not
coming
up
and
the
SSH
was
was
not
there
so
that
connectivity
is
there
now
and
you
just
you
know
we
can
go
into
and
yeah
we
can.
We
can
just
try
out,
try
out
whatever
scripts
that
we
have
in
terms
of
Calico
or
whatever
you
know
the
the
struct.
Basically,
your
cluster
creation
things
yeah.
We
can
try
that
now.
B
From
me,
I
said
yeah
so
and
so
pramita
is
gonna.
I'm
gonna
start
looking
into
some
of
the
test
related
stuff
with
pramita
some
of
the
e2e
windows
stuff.
Now,
because
I
feel,
like
she's,
been
banging
her
head
against
this
qemu
stuff.
So
long
I.
B
To
have
some
fun
and
write
for
code
now,
but
so
next
thing
is,
she
got
the
pr
and
we
just
we
need.
We
need
we're,
gonna
need
to
go
through
and
just
make
sure
it
works
end
to
end
now,
because
you
know
so
folks
want
to
make
PRS
or
whatever
try
it
out
see
what
comes
up.
What
doesn't
whether
Calico
Works,
whether
ant
Trail
works?
You
know
that's
kind
of
The,
Next
Step,
so
now
now
we
can
crowdsource.
B
This
whole
thing
right,
like
the
hard
part
of
like
digging
deep
into
the
providers,
is
done
so
now.
Let's
just
go
test
the
pr
and
I'll
do
it
to,
and
so
yeah
thanks
I
guess
this
is
your
your
your
Sig
Windows
internship
is
over.
As
of
today's.
B
All
right,
cool
and
they're,
not
here
but
Nuno
and
Ross,
and
a
few
other
people
along
the
way,
have
helped
to
give
us
advice
and
figure
this
out.
So.
A
A
B
Yeah
I
just
got
my
new
Macbook
too
it's
from
VMware,
because
I've
been
here
three
and
a
half
years,
and
they
sent
me
an
M2
so
or
an
M1,
so
I'm
looking
forward
to
see
Windows
Dev
tools
being
like
30
slower
for
no
obvious
reason,
but
at
least
working
on
my
new
laptop
okay
thanks
Darvin
for
this
idea.
By
the
way
also,
we
really
appreciate
it.