►
From YouTube: Kubernetes SIG Windows 20230613
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,
I
think
the
recording
has
started
welcome
to
the
June
13th
big
Windows
community
meeting.
The
meeting
is
recorded
and
uploaded
to
YouTube.
So
please
add
here
to
the
cncf
code
of
conduct
which,
if
folks
are
not
aware
generally
translates
to
be
kind
and
nice
to
everyone
all
right.
B
I
have
bad
enhancement,
I've
painted
some
people
from
State
storage
and
then
Jordan
didn't
finish
the
API
review
before
we
went
on
break
so
I
I'm,
not
too
hopeful
this
one's
going
to
get
in
for
128,
but
I'll
and
just
yesterday
somebody
from
the
prrr
team
took
a
look
and
I
need
to
respond
again.
I'll
do
that
after
students,
Community
meetings
so
we'll
see,
I
hope
that
that
gets
in.
A
A
All
right,
if
there
are
no
more
or
not
announcements,
we
can
see
if
there
are
any
new
contributors.
Participation
is
pretty
light
this
week.
A
So
has
anybody
new
and
would
like
to
introduce
themselves
please
go
ahead.
If
not,
we
can
move
up.
A
A
C
I,
just
the
only
reason
I
say,
is
because
I
want
the
other
day,
I
needed
to
look
something
up
at
Sig,
Network
and
I
I
needed
to
look
up
something
from
like
a
presentation
from
like
three
years
ago,
because
I
was
I,
wanted
to
show
somebody
a
demo.
We
did
on
the
network
policy
stuff
and
I
was
like
thank
God.
I
was
all
in
one
dock.
It's
the
only
place
where
all
the
information
is
all
so
I
mean
we
could.
C
B
B
One
is
this
is
owned.
I
think
this
is
still
in
Michael,
Michael's
personal
account,
so
I
mean
we
could
probably
start
a
new
Doc
and
carry
over
everything.
Oh,
that
would
be
great
yeah
and
then
try
and
reformat
it
too
yeah.
A
B
A
A
C
B
C
C
C
A
A
Yeah
I,
don't
worry
about
that
yeah
I.
Can
it's
a
copy
based
job
so
I'll
just
do
it
I'll
clean
up
some
of
the
the
text
and
what
I'll
do
moving
forward
is,
rather
than
just
having
a
giant
note
section
is
I'll
have
like
subsections
for
each
meeting
so
that
it's
easy
for
us
to
travel
as
if
we
want
to
go
hey
I
want
to
go.
Look
at
the
meeting
notes
from
this
date.
I
can
go
and
do
that
yeah.
C
A
C
A
C
David
can't
make
it,
but
he
got
node
ports
working
on
the
Windows
service
proxy
yesterday
on
the
new
one
that
we're
writing
and
he
he
want.
He
said
he
wants
to
come
next
week
and
and
demo
it
I
haven't,
looked
at
it
for
a.
A
C
C
There
we
haven't
done
the
service
type
load,
balancer
a
lot
of
the
function
at
this
functionality
for
node
ports.
Wasn't
there
at
all,
because
it
okay
I
only
did
the
cluster
IP
when
we
originally
copied
it
over
and
so
he's
adding
the
node
he's
having
to
add
a
lot
of
the
function
that
new
functionality
back
yeah
because
he
went
he
he
he
insisted
on
implementing
it
using
the
the
full
State
model.
C
He
since
he's
like
it's
going
to
be
way
better
and
so,
which
it
is
it's
a
lot
more
readable,
so
so
he's
implementing
some
of
the
new
new
functionality
from
scratch.
C
But
yeah
it
we
haven't
encountered
any
eks
specific
bugs
this
time.
So
who
knows,
though,
when
we
tested
on
AKs?
What
we'll
see.
B
A
C
Wondering
what
we
should
do
about
the
windows
I
think.
Should
we
I
I,
don't
know
whether
he's
still
around.
B
A
Yeah
I
I
pinged
him,
but
I
didn't
hear
back
so
we'll
give
it
some
more
time
we'll
pick
him
again,
but
yeah
you're.
Definitely
right
Jay,
we
yeah
at
least
what's
there
in
mastered
works,
so
we're
not
in
a
spot
where,
what's
that,
remaster
does
not
work?
A
It's
just
a
you
know.
Moving
forward,
we
keep
not
being
able
to
make
a
make
a
call
on
on
things.
C
I
mean
yeah,
I,
mean
I.
Think
Windows
native
solution
is
where
we
need
to
head.
If
you
know
so,
you
know
for
now.
We
should
just
assume-
and
today's
thing
is
an
experiment,
and
if
somebody
wants
to
take
over
that
experiment,
I
I
still
don't
have
a
Windows
laptop.
So
I
can't
take
any
of
that
work
over
so
I'm
stuck
all
I've
got
is
M1
and
I've
got
an
M1
and
another
M1
like.
A
A
C
B
C
C
A
We
always
so,
let's,
if
you,
if
you
take
a
step
back
and
think
about
the
history
right,
we
always
had
something
that
worked
on
Fedora
or
Ubuntu,
which
is
using
virtualbox
I.
Think
all
of
this
came
about
because
we
wanted
an
effort
to
move
away
from
virtualbox
and
then
we
started
introducing
requirements
like
oh
I
would
like
to
see
this
work
on
an
M1
or
an
M2
Mac,
which.
A
On
arm
and
I
think
we
spent
a
lot
of
Cycles
trying
to
get
that
working,
which
is
what
I
don't
want
to
revisit
in
some
sense
right,
I
in
in
some
sense.
What
I
would
like
to
see
is
we
have
sign
Windows
Dev
to
work
on
AMD
64
based
systems
and
if
we
can
get
it
working
on
Fedora
and
windows,
I
think
that
is
good
enough,
but.
C
A
C
B
A
Yeah
definitely
more
people
should
try
it
on
Fedora,
but
I'm
with
Mark
I.
Don't
see
why
this
should
not
work
on
Ubuntu
either.
It's
you
know
we
should.
What
we
need
to
check.
Jay
is
the
issue
that
you
ran
into.
Is
that
a
one-off
because
you
ran
a
particular
distribution
of
Ubuntu
or
that's
an
issue
that'll
go
away.
If
you
use
like
an
LTS
version
of
Ubuntu,
that's
out
there.
C
A
A
C
I
think
we
should
we
should.
We
should
say
what
works
based
on
what
we
know
works
right.
So
if
you've
got
it
working
on
Pandora,
then
that's
the
latest
thing
that's
been
tested
right
like
and
if
we
can
get
it
working
again
on
Ubuntu,
then
we
should
totally
say
that
okay,
this
should
work
somewhere.
Is
a
it's
really
confused
a
lot
of
people
right,
even
because,
like
I
thought
it
worked
on
Ubuntu
and
now
it
doesn't
now
I'm
wondering,
should
I
upgrade
Ubuntu
like
you
know,
you.
A
Know,
yeah
I
just
think
we
you
know
to
do
these
sort
of
things.
We
just
need
to
be
a
little
systematic,
I
think
what
happened
with
the
whole
Sig
Windows
devtools
effort
is.
We
went
off
in
a
bunch
of
different
directions
like
every
time
a
new
Direction
came.
We
said,
oh
that
looks
exciting.
Let's
do
that
and
none
of
that
panned
out
like
I,
think
we
had.
You
know
we
did
that
redshift
thing
for
a
while.
A
A
A
C
B
C
A
I
think
so
the
action
item
is
I
will
go
off
open
up.
Vr
call
out
that
it's
been
tested
on
fedora.
C
C
C
Yeah
and
I
think
it's
a
lesson
for
us
as
a
Stig.
The
Mage
file
is
a
great
point
you
bring
up
like
we.
We
shouldn't
have
coupled
that
to
this
like
we,
we
made
the
bar
so
high
that
we
there
was
a
basic
thing
that
would
have
enabled
Windows
developers
to
actually
use
the
dueling,
and
we
we
made
the
bar
so
high
that
we
lost
we.
We
drew
it
out
so
long
like
you
know
what
I
mean
like
we
shouldn't
do
that
right
like
well.
A
C
A
C
A
That's
a
huge
problem
Jay
like
because
you
are
so
so,
for
example,
right
if
I
try
to
introduce
another
image
that
doesn't
have
the
steps
that
were
done
as
part
of
image
Builder.
It's
this
like
vagrant
up,
will
not
work
because
way:
grind
up
assumes
that
some
artifacts
are
already
present
on
the
image.
A
C
A
Say,
for
example,
we
want
to
move
from
2019
to
2022,
or
we
want
to
introduce
an
image
which
has
like
a
particular
patch
bush.
Then
you
need
to
change
the
image
right.
So
at
that
point
we
need
to
be
careful
that
we
do
all
the
steps
that
are
done
as
part
of
creating
that
image
during
image,
Builder
steps
and
in
general
this
is
bad
software
practice,
where
you
are
not
clear
about
where
you're
doing
where
you
are
introducing.
C
A
B
A
A
Reference
it
yeah,
and
that
is
also
this
confusion
where,
if
you
installed
Calico,
the
Calico
installation
ends
up
re-doing
the
the
cubelet
service
to
point
to
its
own
Powershell
script.
To
start
running
the
cubelet,
which
is
different
from
the
service
configuration
that
you
had
when
you
were
initially
creating
this.
B
C
C
The
thing
to
me,
that's,
the
biggest
of
all
the
things
you
mentioned
is
how
do
we
get
upgraded
to
2022,
because
I
think
that's
the
thing
that,
like
you've,
mentioned
a
lot
of
problems
and
they're
they're
they're
all
great
problems.
The
thing
that
might
actually
selfishly
affect
something
that
I
specifically
would
want
to
do
or
test
would
be
I
want
to
test
Windows
22,
because
that's
what
my
company,
ships
and
I
want
to
test
that
if
I
change
this
line
of
code
in
the
kubelet,
it's
still
I
can
still
launch
containers
on
Windows,
22.
C
and
I.
Don't
really
care
how
anything
happens,
other
than
that
I
have
Windows,
2022
and
I
have
a
specific
couplet
that
I
have
right,
and
if
we
can't
do
that,
then
we
do
have
a
problem
that
is
to
me
blocking
every
single
use
case
you
could
ever
have
for.
First
for
for
because
everybody's
got
to
be
doing
stuff
on
2022
now,
right.
B
A
A
Yeah,
so
let's
you
know
I'll
at
least
do
the
the
low
hanging
fruit
like
calling
out
where
it's
tested
and
yeah.
This
is
going
to
be
a
long-standing
problem
is
what
I'm
I'm
saying
with
no
easy
solution
inside,
because.
A
Let's
roll
I
think
we're
getting
the
fact
that
we're
not
supposed
to
be
using
virtualbox.
That's
how
all
of
this
started
that
it
started
with
us
trying
to
move
off
a
virtualbox,
and
then
we
just
went
off
in
all
kind
of
different
directions.
A
All
right
folks,
let's
bring
the
meeting
code
close
and
we'll
keep
this
conversation
going
all.