►
From YouTube: Kubernetes SIG-Windows 20230509
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
Code
of
conduct
we're
a
little
late,
so
let's
get
started.
First,
then
only
announcement
is
that
the
128
enhancements
freeze
is
a
couple
weeks
away.
That's
June,
15th
I
think
we
discussed
a
bunch
of
enhancements
last
week,
so
don't
need
to
discuss
more
unless
anybody
has
some
updates.
Next,
we'll
give
some
space.
If
there's
any
new
contributors
who
want
to
say
hi
introduce
themselves,
ask
some
questions
share
what
they
want
to
get
out
of
this.
A
C
Yes,
okay,
so
last
week
I
just
mentioned
it.
We
got
a
few
reviews
and
had
a
little
discussion
and
I
think
we're
gonna
add
the
memory
to
the
Windows
Fields
only,
and
so
that
means
it
will
be
available
via
the
stat
summary.
If
you
turn
on
the
cry-only
metrics
feature
and
we'll
push
to
get
that
into
beta,
so
that
it's
on
by
default,
if
you
do
need
this
field
prior
to
that
time,
it
is
exposed
Through,
the
Windows
exporter
and
you
could
use
a
cada,
scaler
and
kind
of
Auto
scale
against
that.
C
A
I
do
notice
like
two
here,
and
this
was
I,
think
the
plan,
but
we
should
highlight
that
that
eventually
we
hope
to
have
the
built-in
scalers,
HPA
and
BPA,
and
everything
and
Metric
server
expose
this.
Do
we
have
like
an
issue
that
we
can
track
multiple
like
this
PR
plus
the
like
any
future
ones,
especially
around
metric
server
too
James?
No
I,
don't
think
we
do.
Okay,
well,
maybe
I'll,
try
and
make
that
today,
because
I
think
this,
since
this
is
going
to
span
multiple
potentially
releases,
we
should
maybe
have
an
issue
for
this.
C
C
D
I
figured
I'd
catch
up
with
foreign.
D
Where
things
were
at
over
the
last
couple
of
weeks,
I
know
there's
some
PRS
on
the
Sig
Windows
Dev
tools,
Windows
native
solution,
but
that's
just
some
ongoing
implementation
details
that
we're
working
through
so
that
doesn't
need
to
be
an
official
part
of
the
meeting.
If
folks
have
other
stuff
to
talk
about.
E
How
about
how
about
the
the
windows
Box
Thing,
if
this
is
a
part
of
the
larger
picture
in
I,
was
watching
the
the
CI
trash
a
few
minutes
ago
and
I
noticed
that
it's
end-to-end
tests
running
against
windows
and
is
the
wind,
the
official
Windows
box
used
there
for
those
tests
or
I
mean?
What's
the.
A
Those
tests
are
not
using
sync
Windows
devtools
right
now.
Those
tests
are
using
cluster
API
provided
for
Azure
they're,
the
the
cluster
profile
kind
of
all
that
code
to
provision
the
Clusters
in
Azure
they're
still
running
as
private
jobs,
but
they're
yeah,
just
Cloud
clusters,
yeah.
D
We
can
we
can
break
anything,
we
want,
we
don't
even
have
versions
like
yeah
I'm
gonna
have
to.
If
we've
got
something
better,
we
can
do
it.
The
question
is:
my
question
is
you're
concerned
about
image
Builder
and
the
kubernetes
version
is
the
only
thing
I'm
worried
about
because
I'm
like
well.
The
whole
idea
of
Sig
Windows
Dev
tools
is
that
we
install
kubernetes.
So
what
did
you
run
into
that
made
you
worried
about
that,
or
were
you
just
being
polite.
E
No
no
I
I've
been
writing
the
the
box
that
was
built
with
the
image
Builder
right
and
I
noticed
simply
that
kubernetes
on
Windows
box
is
old
and
it
doesn't
get
updated
or
installed.
During
the
vagrant
box,
sorry,
vagrant
machine,
provisioning
and.
D
E
We
are
copying,
we
are
copying
some
stuff,
but
but
I
mean
the
the
versions
are
reported,
diff,
really
I'm
I'm
new
to
this
whole
ecosystem
and
it
really
I'm
I'm,
not
I'm,
not
I'm,
not
sure
myself.
You
know
I
think.
E
D
B
Know
how
are
you
gonna
make
me
fat
again?
Sorry
I
missed
that
I.
D
B
A
B
So
there
are
two
things
right:
Matt,
oh
Jay,
sorry,
James,
I,
just
finished
this
and
I'll
and
I'll.
Let
you
go
it's.
This
is
what
we
have
discussed
in
the
past
is
what
do
we
want?
Stick
with
those
Dev
tools
to
do?
Do
we
want
to
start
with
the
blank
windows
image?
Sorry
book,
I
really
have
bad
allergies.
That's
why
I'm
coughing
all
the
time
if
you
are
going
to
start
with
a
blank
windows
image,
and
then
we
do
everything
right,
we
install
continuity.
B
D
C
Yeah
so
I
think
the
problem
with
doing
it
all
is
it
just
took
so
long,
so
the
the
reason
they
ended
up
using
the
Sig
Windows
Dev,
like
the
image
Builder
image,
was
because
it
took
the
build
time.
Like
start
get
clone
run,
make
was
like
an
hour
and
a
half,
and
then
they
with
the
baked
image.
You
cut
that
down,
because
you
don't
have
to
do
the
reboots.
You
don't
have
to
do
all
those
installs,
and
so
it
was
just
to
get
like
all
the
features
that
you
need
installed
and
configured.
C
C
D
B
C
It's
a
matter
of
like
hey.
We
have
this
thing
that
does
kind
of
for
all
the
stuff
we
need,
and
so
I
think
that's
where
I
mean
had
initially
just
grabbed
it
to
to
start
it.
There
yeah.
D
B
E
The
thing
is,
the
thing
is
the
Packer
and
ansible
is,
is
a
is
a
new
animal
to
me?
I,
don't
have
an
experience
so
I,
you
know
whatever
I
I
I
understand
I
need
to
learn
stuff
to
move
forward,
but
you
know
I
would
I
would
appreciate
if
someone
tells
me
go
learn
this
I.
D
E
E
I
I've
just
received
lots
of
answers
to
my
questions
so
from
from
James
from
aravind
from
UJ.
I
received
lots
of
answers
already
so
I
I
kind
of
get
a
picture.
What
is
the
purpose
of
the
Sig
Windows
devtools?
You
know
what
how
it
should
work
and
things
like
that.
Yeah,
in
my
opinion,
should
work
fast.
Building
the
whole
image
takes
me
around
1
hour,
50
minutes.
So
if
I
want
to
run
actually
kubernetes
the
two
node
cluster
I
want
to
run
it
fast.
So
I
need
some
base
image.
E
The
base
image
doesn't
have
to
have
all
the
components
they
can
be
copied
during
the
machine
provisioning,
but
the
base,
like
you,
know
the
the
system.
The
firewall
is
off,
the
win,
RM
is
configured
and
things
like
that
should
be
in
place
in
the
base
image.
But
then
just
copying
you
know
the
the
binaries
and
and
some
yamls
and
and
that
yeah.
D
E
D
Cool
yeah
that
sounds
good
then,
and
there's
yeah,
there's
things
we
can
do
in
the
future
to
make
it
better.
But
it's
like
yeah,
you
know
so,
do
you?
Are
you
gonna
upload,
a
new
image
to
vagrant
Cloud?
Do
you
just
want
to
do
that
and
start
using
that
instead
or
do
you.
E
You
me
yeah
yeah
yeah.
Yes,
that's
that's
my
goal.
Hopefully
like
this
week,
I'll
get
it
done.
Yeah
cool.
E
We
need
the
Windows
Server
2022
as
well,
so
yeah
I
will
experiment
with
the
packer.
Just
you
know
like
a
single
tool
that
builds
the
base
image
and
then
we
don't
need
the
image
Builder,
but
the
you.
E
A
If
you
want
I,
think
I
have
some
examples
of
workflows
that
do
something
similar
to
what
image
Builder
does,
but
just
use
Packer
and
Powershell,
and
not
ansible,
that
might
be
I'll
I'll.
Get
that
to
you,
yeah
Slack,
yeah,
yeah,.
B
B
C
B
B
A
B
B
Or
four
years,
yeah
I,
don't
think
we
can
claim
that
we
were
the
first.
In
fact,
our
golden
image
has
nothing
kubernetes
related
in
it's
a
clean
image,
with
all
the
prerequisites
needed
for
running
kubernetes,
and
then
our
operator
does
all
the
setup
and
installation
it's
mainly
because
we
need
to
support
multiple
clouds,
not
just
one
Cloud.
So
we
can't
go
with
you
know
a
proper
golden
image
with
everything
pre-installed.
D
D
D
But
yeah
okay.
D
So
I
don't
really
have
anything
else.
E
I,
don't
have
anything,
I
mean
I
I'll
press
on
with
the
Packer
and
trying
to
eliminate
that
ansible
from
the
picture
and
if
I
have
any
questions,
I'll
just
reach
to
Mark
and
Arabian
and
let's
see.
E
D
E
Not
I
mean
I
would
be
happy
to
use
image
Builder,
but
the
answerable
is
a
bit
because
ansible
when
I
run
things
on
the
Windows
host,
then
I
need
to
run
from
WSL
just
to
make
ansible
you
know
running
and
but
the
virtualbox
is
on
the
Windows
host,
not
on
WSL,
so
I
had
to
apply
some
hard-coded
IP
addresses
to
let
the
Packer
running
and
ansible
running
on
WSL
connect
to
virtualbox
on
my
host
and
I.
E
Don't
I
don't
have
any
idea
how
to
how
to
sub
what
kind
of
patch
to
submit
to
image
Builder
to
make
it
kind
of
generic
in
a
usable
outside
my
own
system,
local
system.
So
this
is
like
I
applied
very
specific
patches
with
you
know:
IP
addresses
hardwired
and
things.
So
if
the
basketball
can.
E
D
E
D
E
2022
and
like
you
know,
I'm
thinking
long
term
a
bit
here,
perhaps
not
unnecessarily,.
B
But
yeah
no
I
think
he
has
a
good
point
Jay,
because
we
ran
into
the
same
thing.
We
found
that
if
our
golden
image
creation
steps
are
not
well
documented
and
re-producible,
it
becomes
a
problem.
Everybody
is
trying
to
say
solve
the
same
problems
they
ran
into
over
and
over
again.
So
that's
why?
If
you
look
at
our
repo
you'll
find
the
golden
image
steps
are
very
detailed
and
very
organized
so
that
anybody
can
go.
B
Yeah
it'll
actually
be
very
useful
for
us,
because
the
first
time
we
run
into
like
oh
man,
we
need
to
rebuild
this
image
is
when
we'll
run
into
trouble.
If
we
do
not
know
how
to
do
this
easily,
because
that's
the
trouble
I
ran
into
and
I
was
like.
Oh,
let
me
try
and
rebuild
this
image
and
I
just
couldn't
get
it
to
work.
D
A
D
Okay,
great
yeah,
totally
I
mean
anything
that
makes
things
better
is
great.
I
just
didn't
want
you
to
feel
like
pressure
to
solve
this
and
the
other
huge
problem
that
you're
solving,
because
so
the
other
huge
problem
that
you're
solving
is
like
such
a
huge
problem
that
I'm
just
amazed
that
you
can
solve
both
of
them
at
the
same
time
at
the
same
time,
but
that's
awesome.
Yeah.
E
Yeah
I
would
rather
solve
like
one
important
problem
before
I
move
to
Second
important
problem
that
that
is
based
on
the
previous
solution.
You
know,
you're
gonna
get.