►
From YouTube: Kubernetes SIG-Windows 20230221
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
All
right
welcome
everyone
to
Sig
windows:
it's
February,
21st
2023..
This
is
a
cncf
meeting,
and
so
we
follow
the
cncf
code
of
conduct.
Anybody
has
any
questions
or
concerns.
Please
reach
out
to
ours,
us
or
any
of
the
leads
and
otherwise
welcome
hope.
Everybody
had
a
good
weekend
and
I
think
we'll
get
started
here.
A
So
for
announcements
code
freeze
is
March
14th,
so
coming
up
a
couple
weeks
now,
and
so,
if
you
have
any
PRS
get
them
out,
there
get
them
reviewed
Hangouts
on
any
of
them,
and
let
us
know
if
you
need
help
with
anything.
B
By
node
log
viewer,
of
course,
at
some
point,
we'll
need
another
review.
Okay,.
A
B
A
And
then
we'll
welcome
any
new
contributors
if
anybody's
out
there.
That
wants
to
say
hi
and
let
us
know
what
you're
up
to
and
why
you're
interested
in
Sigma
news.
A
Okay,
doesn't
look
like
anybody
wants
to
say
hi,
so
move
on
the
agenda,
and
so
Mark
I
think
you
have
the
first
one
here:
periodic
tests.
C
Yeah
so.
A
C
Who
are
here
were
working
on
kpng
for
Windows
and
ported
a
lot
of
it.
We've
moved
a
lot
of
the
code
for
the
Windows
server
or
the
windows
win
kernel
proxy
or
from
the
kpng
remote
to
the
windows
service
proxy
repository,
and
we
finally
got
a
test.
Periodic
test
pass
stood
up,
that's
running
KPMG.
This
test
is
using
cluster
API
provider
for
Azure
running
this,
but
it
is
running
the
latest
image
out
of
that
Repository.
D
C
D
Yeah
as
I
recall,
there's
six
or
seven
total
tests
in
Linux,
I'm,
sorry
in
I,
think
there's
six
or
I
never
counted
for
the
Sig
Windows
tax
for
the
Linux
tests.
If
you
disable
kubeproxy,
there's
six
conformance
tests
that
fail
and
I
don't
know
if
that
number
is
different
for
Windows
but
like
in
the
worst
case
scenario,
I
wouldn't
expect
more
than
like
10
or
15
tests
to
fail.
C
D
D
D
Thanks
so
much
okay,
cool
great.
A
D
Yeah
and
it's
a
lot
of
go
codes,
so
if
folks
actually
wanted
to
write,
go
code
and
stuff
and
not
spend
a
bunch
of
time,
just
installing
Windows
and
like
like
here's,
a
chance
to
get
in
there
and
write
some
code,
because
now
that
we've
got
this
job,
folks
can
write
some
go
code.
Compile
things
make
a
PR.
C
I
think
there's
an
opportunity
for
writing
some
unit
or
integration
tests
that
don't
require
cluster
as
well
with
whatever
you
call
it
like
the
file
to
store
Jay
yeah.
D
C
D
D
D
The
windows
that
you
buy
from
the
store
not
Windows
server,
is
there
a
way
that
I
can
then
run
the
hns
apis
and
stuff
on
that
machine
so
that
we
can
give
a
developer
story
to
folks
and
say:
look
yeah
like
any
Windows
machine
you
can,
then
we
can
use
that
yeah
I
see
you
not
just
you
can
interrupt
me.
James
I'm,
I'm,
rambling.
You.
C
A
Hardest
thing
would
be
just
getting
container
d
installed
and
running
the
right
version
of
the
windows
image.
If.
D
B
We're
noticing
that
with
folks
who
are
new
to
Windows,
when
you
ask
them
to
bring
up
a
Windows
workload,
they
find
it
really
difficult
and
I've
pointed
them
all
the
docs
that
we
have
at
the
Microsoft
docs
and
all
that
and
they're
like
it's
still
not
obvious
like
if
you,
if
they
they're
the
the
issue,
they're
saying,
is
they
go
to
like
Docker
Hub
and
look
at
a
Windows
image
by
looking
at
a
Windows
image,
there
they're
not
sure
what
to
do
from
that
step.
So
I
sometimes
feel
like.
B
D
A
Windows
yeah,
it's
not
really
clear
to
me
like
what
do
I
do
if
I
want
to
make
a
sample
application,
what
do
I
do?
I
get
Dot,
net3
and
then
I
get
some
version
of
Docker
and
then
I
hope
that
the
thing
that
I
build
will
work
on
the
Windows
Server
22
instance
that
I
have
and
if
it
doesn't
I,
go,
look
up
a
table
or
something
and
there's
that
weird
table
somewhere
on
the
internet.
That
has
all
the
base,
images
and
versions
right.
B
B
They're,
familiar
with
containers,
they're
familiar
with
Linux
containers,
but
they're
not
familiar
with
Windows
and
I'm
I'm,
hesitant
to
go
and
tell
them
go
and
learn
all
this
stuff
about
Windows
before
you
can,
you
know
start
running
a
container
because
that's
one
way
of
telling
people
okay,
you
know
this
is
too
complicated.
Don't
do
it
that
sort
of
thing
right,
so
I'm
trying
to
get
them
into
like
an
easy
path
that
they
could
do
this.
C
D
C
D
E
Running
so
I
kind
of
have
one
of
those,
it's
not
anything
official,
but
it
was
when
I
was
working
on
rk2
and
like
we'd
have
QA
people
be
like
hi
I
have
a
Windows
laptop?
How
do
I
test?
E
It's
not
anything
official,
though
so
I'd
be
happy
to
find
those
notes
and
throw
them
in
a
document
somewhere.
So
we
can
Rev
on
it.
D
D
Smith
I
mean
the
the
use
case
that
I
know
of
is
I,
have
a.net
3
app
and
I
want
to
run
it
in
a
pod.
What
do
I
do
now
right
and
then
there's
that
and
then
there's
something
like
I
have
some
Windows
app
that
talks
to
a
PCI
device
and
I
want
to
run
that
in
a
pod.
What
do
I
do
now?
Those
are
the
two
that
I
know
of
that
are
like
and
then
there's
three
I
have
a
Windows
app
that
does
dot
net
that's.net3.
D
That
needs
to
be
fully
integrated
with
active
directory
and
I
want
to
run
that
in
a
pod
right.
It's
like
there's
these,
like
there's
like
seven
or
eight
of
these
things
that
are,
you
know
what
I
mean
like
yeah
and
it's
like
I
think
that
Ross
is
like
to
me.
That's
how
that's
how
you
tell
the
story
right.
It's
like
it's
something
like
here's
who
I
am
here's.
What
I
want
to
do?
D
What's
one
way
to
do
that,
right
and
and
then
and
then,
if
we
do
that,
then
we
can
just
add
stories
to
it,
and
people
will
know
what
to
look
at,
because
most
people
are
pretty
smart.
Like
one
thing
once
they
kind
of
are
into
one
funnel
they're
able
to
dig
around
and
figure
out
the
details
right,
but
the
problem
is
sometimes
people
don't
know
what
funnel
to
start
from
right.
C
D
E
I
had
actually
kind
of
started
writing
something
very
similar
but
separate
as
part
of
a
cap.
So
yeah
I
can
merge
those
two
together.
D
While
we're
looking
for
new
contributors,
operational
Readiness
work
has
frozen
because
we
lost
the
person
that
was
working
on
it
me
and
amima
flat
out
and.
C
D
I'm
trying
to
onboard
new
people
I'm
spending
all
my
time
doing.
That
and
folks
are
folks
are
coming
online,
but
we
need
somebody
wants
to
write
some
go
code.
We
have
the
operational
Readiness
stuff
and
we
haven't
finished
it.
So
that's
another
one
and
it's
easier
than
the
Kube
proxy
stuff.
So
it's
you.
D
Don't
know
if
it
did
versions
around
it
did
we
I
mean
it's
probably
Alpha.
If
anything,
what
is
that
so?
Okay?
So
it's
it's
the
it's
our
version
of
kubernetes
conformance
right,
so
the
back
story
there
was
over
here.
You
know
when
we
over
at
ton
Zoo
when
we
decided
to
release
Windows
support
for
kubernetes.
D
There
was
always
this
circular
question
of
like
well.
How
do
we
know
whether
our
thing
is
as
good
as
what
Azure
does
or
is
as
good
at
what
red
hat
does
or
whatever
right
so
we're
thinking
about
this
and
we're
like
well
the
reason
this
is
such
a
complicated
thing
that
and
to
ask
is
that
there
is
no
actual
conformance
suite
for
Windows
that
we
can
run
so
I
think
it
was
a
deep.
What
was
the
name
of
the
Evelina
or
whatever
she
started
a
an
issue.
D
C
D
So
and
Mike,
you
know
what
the
conformance
tests
are
right,
like
the
cncf,
conformance
spec
right
like
there's,
two
they're
250
tests.
If
you
run
them,
then
you're
then
you're
a
kubernetes
provider.
Officially,
if
you
don't,
if
you,
if
your
distribution
fails
on
them,
then
you're
not
right
and
that's
the
general
rule,
except
for
for
Edge
devices
where
sometimes
you
may
have
like
one
node
and
that's
running
a
kubernetes
cluster
and
that
fails
conformance
because
there's
one
test
that
requires
you
to
have
two
nodes.
But
that's
another
thing.
D
So
so
there's
this,
but
in
general
conformance
and
the
reason
I
say
that
is
because
conformance
was
built
for
Linux.
It
was
kind
of
defined
in
2016
or
whatever
for
Linux.
So
so
we
came
out
with
the
operational
Readiness
spec
and
what
that
says
is
people
running
Windows
clusters.
They
are
they're
different.
They
need
some
way
of
knowing
what
their
cluster
supports
and
what
it
doesn't
support
and
whether
or
not
it
conforms
to
some
basic
set
of
standards
for
that
right.
D
So
if
I'm
running
Windows
cluster
I
want
to
run
my
operational
Readiness
specification,
it'll
say:
yes,
you
support
storage.
Yes,
you
support
GPU
workloads.
Yes,
you
support
active
directory.
Yes,
you
support
persistent
volume
claims.
Yes,
yes,
yes
and
I
can
just
see
those
bullets
in
like
one
page
right.
So
that's
what
it
does.
It's
plug
in
a
meme
Works
real
hard
on
it.
This
other.
This
girl,
chinchi
her
and
a
meme.
D
Both
worked
really
hard
on
it
and
they
got
a
lot
of
stuff
done,
and
the
initial
prototype
was
like
a
like
a
tiny
gold
program
that
that
I
wrote
originally
and
and
then
they
went
off
and
fleshed
it
out
and
made
it
a
Sony,
but
we
plug
in
and
then
since
she's,
not
working
on
kubernetes
anymore,
so
she's
she's
doing
something
else
now,
and
so
we
don't
have
anybody
working
on
it
right
now.
D
So
it's
a
bunch
of
go
code
and
it
basically
runs
the
e2e
tests
and
publishes
a
yaml
file
that
really
makes
it
super
easy
for
an
end
user
to
know
what
their
clusters
do
and
don't
support,
and
it
mostly
works.
We
just
don't
have
anybody
owning
the
completion
of
it?
There's
no
technical
problems
to
solve.
There's!
No!
D
D
He's
interested
yeah
I
have
a
link
to
that.
I'll
put
it
in.
D
C
D
Yeah
definitely
yeah
as
far
as
Windows
Dev
tools
goes,
the
so
bringing
this
whole
thing
up
of.
How
do
we
get
new
contributors
right
to
me?
The
dev
tools
is
I,
hope
that
we'll
be
able
to
get
people
to
easily
contribute
that
way,
but
so
pramita
tried
using
Fusion
this
weekend
and
it
turns
out
that
VMware
Fusion
on
a
Mac
does
not
support
emulation.
D
So,
but
the
maintainer
of
vagrant
qemu
responded
about
five
days
ago,
with
the
potential
work
test
of
whether
or
not
we
could
start
using
qamu
again.
So
we're
going
to
try
to
use
qamu
we're
going
to
basically
I
think
the
guidance
is
going
to
wind
up
looking
something
like
this
and
we'll
put
this
into
a
document.
D
If
you
want
to
contribute
to
Windows,
there's
four
there's
three
there's,
there's
kind
of
like
it
looks
like
three
stories
you
can
use,
VMware,
Fusion
or
VMware
Workstation
and
they'll
work
the
same
way
and
they'll
use
vagrant
or
if
you're
on
a
Mac,
OS
X
machine,
then
you
either
have
a
cloud
account
or
you
use
qemu
manually,
and
that's
because
there's
no
arm
support
on
Windows
and
that
I
mean
that's
a
pretty
complicated
developer
story,
but
I
don't
think
that
we
can
do
anything
simpler
than
that
because
of
the
fact
that
there's
because
of
the
fact
that
these
M2
and
M1
chips
just
now,
but
what
we're
hearing
from
everybody
is
VMware
Workstation
on
Windows
works.
C
C
C
D
If
that,
if
well
do,
if
that
works,
then
we
may
have
a
way
to
start
talking
about
qemu
again,
I
have
a
feeling
that
if
that
manual
invocation
works,
then
we
can
sort
of
say
sort
of
you
know
sort
of
looking
the
other
way
we
can
kind
of
say
you
know
like
well,
it
looks
like
qemu
could
work
for
this,
but
it's.
D
You
know
nobody's
really
doing
it
like
maybe
it
seems
like
for
us.
The
big
thing
is
getting
Windows
developers
engaged
and
because
anybody
can
get
their
hands
on
a
Windows
laptop
or
an
Ubuntu
laptop
if
you're
realistic.
So
if
we
can
just
have
a
a
unified
story
for
AMD
64
laptops-
and
you
know-
I
mean
that
solves
some
reasonable
chunk
of
the
problem.
Right.
E
So
I
have
a
I,
actually
have
a
Mac,
Studio
and
then
I
also
have
the
last
two
years
of
the
windows
arm:
64,
Dev,
kids,
so
I.
This
is
actually
a
problem
near
and
dear
to
my
heart,
so
I.
If
anyone
wants
to
kind
of
pair
on
that
on,
you
know
figuring
out
how
to
do
arm64
support,
I
would
love
to
do
that.
E
D
E
D
On
work
days,
all
right,
9,
A.M,
yeah
cool
Let's,
do
let's
pair
now
we
can
stop
the
recording
and-
and
we
can
pair
on
this
thing
and
try
to
figure
out
what
to
do
and
what
we
need
is
an
approach,
so
I'll
open
up
a
Google,
doc
or
something,
and
we
can
sort
of
set
up
the
two
or
three
things
we're
going
to
do
and
see
where
you're
going
to
help
us.
A
Cool,
so
just
to
wrap
up
the
the
main
meeting.
Does
anybody
else
have
anything
else?
Otherwise,
we'll
see
everybody
next
week.