►
From YouTube: Kubernetes SIG Windows 20220705
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,
the
recording,
has
started
welcome
it's
july
5th
2022..
This
is
stick
windows
standard
meeting
every
tuesday.
A
A
So
yesterday
was
a
holiday
in
the
us,
and
so
I
think
there
was
kind
of
maybe
a
little
bit
of
a
light
agenda.
Jay
said
he's
going
to
talk
a
little
bit
about
dev
tools.
A
Here
I
don't
have
much
for
announcements,
we're
in
code
coding,
phase
of
the
125
cycle,
and
so,
if
anybody
has
any
prs
they're
working
on
or
anything,
they
need
reviews
make
sure
you
drop
it
into
sig
windows
slack
and
you
can
ping
us
or
make
sure
it's
tagged
to
sing
with
sig
windows
as
well,
and
we
will
review
it
and
triage
it
and
also
help
it
help
move
it
along.
A
Oh,
I
do
have
one
other
one
is.
Last
week
we
did
a
demo
of
the
perf
dash
and
the
it
is
now
live,
so
we
have
a
url
for
the
perfection.
They
just
find
it
here.
Oh
cool,
and
I
can
drop
it
into
the.
B
A
So
you
can
go
to
the
perf
dash
here
and
then
up
in
the
top
left
you
scroll
through
here,
and
you
should
be
able
to
select
soak
tests
and
then
over
here
we
have
all
the
different
information
we're
collecting.
So
you
can
see
cpu
usage
containers,
I'm
not
gonna,
go
into
super
detail
here,
but
I
just
wanted
to
call
out
that
we
are
starting
to
collect
it,
so
we'll
be
able
to
see
the
trends
over
time
as
far
as
like
what
services
are
being
used
the
most
during
during
this
test.
B
A
All
right,
let's
do
new
contributors,
there's
anybody
new
here
that
wants
to
say
hello.
Let
us
know
what
you're
up
to
and
why
you
joined
and.
C
Hey
this
is
russell
teague.
I
just
wanted
to
say
hi
the
manager
for
the
windows,
containers
team
at
red
hat,
so
just
pop
it
in
to
say
hi.
B
B
And
is
ravi
still
there.
I
don't
know
he's
not
on
the
windows
containers
team
anyway,.
A
D
D
Okay,
so
for
folks
who
want
to
spin
up
clusters,
so
I
think
mike
you
were
mentioning
you
were
doing
something
with
ansible
or
you
were
going
to
build
something
with
ansible
earlier
yeah
yeah.
So
you
know
we
we
have
this
thing
and
it
really
needs
to
be
ansibilized
or
puppetized
or
salted,
or
something
because
what
we
do
for
our
sig
windows,
dev
tools,
sort
of
we
do.
Oh,
we
got
a
pull
request
who's
this,
oh,
I
think
we
need
to
fix
these
antrio
manifests.
I
mean
did
that.
D
So
what
we
do
right
now
is
that
you
can
pull
this
repo
down
and
run,
make
all
and
it
uses
virtualbox
to
create
a
cluster,
and
we
don't
really
have
anybody
testing
it
heavily
on
linux
right
now
and
we,
I
don't
think
anybody's
used
like
libvert
to
do
all
this,
but
it
would
like
there's
a
few
things
that
you
know
there's
all
these
issues
here
that
we
have-
and
I
think
this
is
probably
one
of
the
key
ones-
the
missing
instructions
for
ubuntu
setup.
D
We
really
need
a
good
ubuntu
or
linux
user
experience
around
this,
and
we
don't
have
that
yet,
and
the
other
thing
we
need
to
do
is
like
because
it
supports
multiple
cni's,
so
it
supports
andrea
and
it
supports
calico
both
and
we
haven't,
like
migrated
it
over
to
like
the
way
we
do
it
is
we
have
these
scripts
that
we
put
in
here,
and
so
it
would
be
really
cool
if
somebody
who's
good
at
ansible
or
something
could
sort
of
just,
and
I
think
this
is
kind
of
a
fun
project,
because
you
don't
really
need
to
be
like,
like
you'll,
learn
this
entire
repo
in
the
process,
and
it's
just
a
matter
of
I
think
going
into
this
vagrant
file
and
replacing
this
stuff
with
like
a
vagrant,
ansible
plug-in
right,
and
I
think
we
could
like
pair
on
it
right
like.
D
I
could
explain
things
to
you
as
we
did
it,
but
like
basically
it's
just
a
matter
of
taking
these
things
and
sort
of
one
by
one
porting
them
over
to
like
ansible
instructions,
and
I
don't
think
there's
any
real,
strong
opinions
on
how
we
how
we
do
that
right.
D
So
that's
kind
of
so
so
sort
of
to
run
it
for
the
first
time
you
could
just
sort
of
clone
it
and
run
make
all
if
you
have
virtual
box
installed
and
it'll
work,
but
I'm
kind
of
open
to
like
what
should
we
do
next
with
this,
because
it's
kind
of
working,
I
still
use
it
for
my
sort
of
day-to-day
hacking
around
on
things,
but
you
know
I
kind
of
I'm
trying
to
figure
out
like
we
could.
D
D
We
could
just
keep
it
being
a
whole
big
web
of
shell
scripts
too,
like
I
don't
really
care
if
I
don't
have
any
problem
with
shell
scripts,
so
I
you
know
like,
but
I
see,
there's
a
thread
somebody
started
yesterday
about
they
had
a
tool
called
kubenet.
Well,
let
me
share
my
screen
again.
D
I
guess
I'll
I'll
keep
going
so
they
had
this
tool
called
kubenet
and
they
were
talking
about
kubenet
github,
and
so
this
is
some
other
tool
yeah
and
I
was
like
what's
this
so
then
I
saw
this
and
I
don't
know
what,
whether
I
don't
know
what
people
use
this
for
either
so
like
this
seems
to
be
an
option,
so
we
could
possibly
sort
of
join
forces
with
these
folks
or
the
coup
ansible
folks,
there's
all
these
different
ways.
We
could
go.
D
I
kind
of
like
what
ours
the
way
ours
works,
though,
because
it's
really
straightforward
and
it
has
all
the
scripts
right
inside
of
it
and
it
doesn't
do
100
different
things.
So
I
kind
of
like
the
road
we
went
down
here
and
but
I
just
didn't
want
to
like
you
know,
leave
out
other
options.
You
know
if
we
can
keep
the
same
functionality
of
supporting
multiple
cni's
and
installing
kubernetes
and
compiling
it
from
source.
I
think
it
will
continue
to
work
for
what
we
care
about.
D
We
probably
should
start
supporting
host
process
calico.
Also,
now
that
james
figured
all
that
stuff
out
but
yeah,
if
folks
want
to
pair
with
me
on
this
and
sort
of
help,
become
a
maintainer
on
it
or
help
sort
of
refactor
it
or
anything.
I'm
I'm
down.
D
I
couldn't
really
figure
out
what
was
going
on
with
the
kubernetes
stuff,
like
I
couldn't
figure
out
what
he
did
or
whether
he
was
planning
on
sort
of
integrating
that
with
other
stuff
we
were
doing
or
proposing
it
or
what
so.
A
Yeah
I
looked
through
his
pr
and
or
his
blog
and
it
looked
like
there's
a
series
of
pr's
in
the
cube
in
it
that
added
windows
support
essentially
using
some
of
the
similar
scripts
that
we
use
here,
and
it
looks
like
from
the
pr's
it
looked
like
cuban.
It
was
using
ansible
and
so
there's
a
bunch
of
ansible
in
there
that
wired
up
the
windows,
nodes
and
added
them
and
then
ran
similar
scripts
to
what
we
we
do
yeah
about
about.
Halfway
down.
A
There
is
like
five
or
six
prs
linked
in
the
at
the
bottom
yeah
at
the
bottom.
There.
D
Yeah
but
he
didn't
come
today,
so
I
just
wanted
to
pave
the
way
in
case
he
wanted
to
come
and
try
to
sell
us
on
using
it.
But
he's
not
here.
So
I'm
not
you
know,
I'm
not
like
I'm,
I'm
not
opinionated
on
whether
we
were
to
use
this
or
not,
but
it
sounds
like
sounds
like
he
was.
Maybe
just
sharing
it
with
us,
just
as
a
hey
like
as
an
fyi,
so
but
anyways
yeah.
E
Yeah,
it
would
be
nice,
I
don't,
I
know
nothing
about
kubernetes,
but
the
things
that
you
know
come
to
mind
is
being
able
to
quickly
change.
You
know
specific
versions
either.
You
know
your
linux
kernel
version,
your
windows,
os
version,
your
kube
version
and
various
other
versions
like
if
you
can
actually
set
that
really
easily.
That
would
be
a
nice
thing
just
for
you
know,
duplication
and
more
well.
D
That's
what
well
that's
what
we
give.
So
that's
what
you
get
with
sig
windows,
dev
tools,
that's
exactly
what
it's
built
for!
Is
that
so
you
go
in
here
and
you
run.
If
you
run
make
all
it
will
clone
kubernetes
from
source,
compile
it
compile
the
kubelet,
compile
coupe
proxy,
compile
the
kubelet
binaries
for
linux
and
for
for
windows,
and
then
it
will
use
those
exact
binaries
and
then
inside
of
the
directory
that
you're
in
you
can
cd
to
it'll
it'll,
literally
clone
kubernetes
locally,
and
so
you
could.
D
D
And,
and
so
that's
the
purpose
of
it
yeah,
and
so
the
other
thing
you
get
is
you
get
the
you
get
the
so
it
allows
you
to
switch
cni's
out
right,
so
it
allows
you
to
switch
out
either
calico
or
entry.
D
We
have
all
these
scripts
that
do
that,
and
so
the
next
step
that
I
was
saying
is
that,
like
it
would
be
nice
if
we
could
refactor
these
scripts
so
that
these
were
actual
ansible
roles,
as
opposed
to,
like
a
whole,
a
wall
of
bash
right.
So
in
other
words,
what
I'm
saying
is,
I
think,
all
the
features
that
folks
want
are
there,
but
I
think
we're
kind
of
at
the
point
where
it
would
be.
D
I
don't
think
there's
any
other
canned
installer
that
does
this,
because
nobody
running
anything
in
production
would
ever
do
something
so
crazy
as
compiling
kubernetes
on
the
fly
and
then
installing
it
locally
like
while
in
on
virtualbox
right.
This
is
only
specifically
somebody
who
wants
to
hack
around
in
a
development
environment
would
use
this
this
repo.
So
I
don't
think
we
can
easily
borrow
any
canned
tools.
I
think
we
get
to
build
it
all
from
scratch.
D
Yeah,
I
think
the
build.
I
think
the
thing
that's
the
longest
is
the
windows
node.
Like
that's
the
long
tail
you
can.
You
can
use
a
there's
a
way
to
pull
a
kubernetes
release.
I
forgot
what
it
is,
but
there's
a
way
you
can
like
pull
a
release
in
here
somewhere.
D
D
A
Awesome
thanks
for
sharing
mike,
were
you
trying
to
do
anything
specific
or
like
what?
What
was
your
use
case
here.
E
I
wanted
to
be
able
to
just
quickly
spin
up
a
cube
cluster
and
be
easily
set
like
a
specific
versions
and
from
one
file.
So,
if
I
want,
you
know,
had
a
user
that
was
running
an
on-prem
version
of
kubernetes
to
set
like
one
two,
two,
a
container
d
version,
a
specific
cni
version
and
various
other.
You
know
like
hot
fixes
and
more
just
to
be
able
to
reproduce
an
environment.
That
was
what
I
was
trying
to
do.
A
Okay,
yeah,
I
think
we're
almost
there
with
that.
I
know
like
I've
spun
that
up
to
do
something
similar
in
the
past,
I
had
to
kind
of
hack
the
makefile
to
not
rebuild
kubernetes,
but
there
was
a
flag
in
there
to
not
to
not
do
that.
So
probably
just
needs
a
little
love
and
could
maybe
potentially
do
what
you
need.
E
D
Yeah,
the
let
me
see
if
I
can
there's
if
we
go
in
here,
we
can
do
like
so.
A
meme
did
a
thing
where
he
actually,
he
actually
did
a
bunch
of
stuff
with
making
it.
So
you
could
use
image
builder
to
to
do
it
through
an
ova
route,
but
the
container
d
installate
installer
uses
that
uses
the
powershell
one.
But
what
we
did
in
here
is
we
forked
all
the
scripts,
so
you
could
literally
go
directly
to.
Where
is
it?
Where
do
we
get
the?
Oh?
D
D
They
can
just
sort
of
edit
the
scripts
and
we'll
locally
sort
of
use
the
local
scripts
in
that
way.
So,
but
it
looks
like
we
haven't
done
that
for
prepare
node,
so
we
still
seem
to
be
downloading
prepare
node
from
the
internet,
so
we
probably
should
have
you
know
copy
paste
that
into
our
little
into
our
little
sort
of
group
of
hacky
forked
scripts.
D
We
also
probably
could
do
some
kind
of
an
overrides
thing.
You
know
like
to
be
smarter
about
it,
so
that
you
know
we're
more
declarative
there,
the
so
this
is
where
you
actually
so
that
option
you
were
talking
about
mike
actually
actually
already
exists,
this
build
from
source.
So
you
could
just
turn
that
to
false
or
true
and
you'll
get
the
thing
you
just
wanted
that
you
mentioned.
D
So
and
then
here's
the
version,
so
I
think
these
are
the
two
options
that
you
mentioned
right
you
you
want
to
not
in
your
situation.
You
would
basically
do
this.
You
said
122,
so
you'd,
probably
just
put
122
here
and
it'll
just
pull
it
down.
I
guess
yep.
D
I'm
gonna
I'll
ping
dimitri
about
those
because
he's
got
the
latest
code
for
that
other
than
that.
I
don't
have
anything
else.