►
From YouTube: Kubernetes SIG Windows 20220503
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).
B
A
A
All
right
I'll
wait,
one
more
minute
to
9
33
and
for
those
on
the
call
who
weren't
here
earlier,
we're
having
some
issues
getting
into
the
zoom
account.
So
that
means
that
I
won't
be
able
to
start
the
recording
before
the
meeting
so
I'll,
just
edit
it
when
we
get
access.
But
it
also
means
a
delay
to
the
recording
to
upload.
A
All
right,
I'm
just
gonna,
start
now
so
hello,
everybody
and
welcome
to
the
may
3rd
2022
iteration
of
the
kubernetes
windows
community
meeting.
As
always,
these
meetings
are
recorded
and
uploaded
to
youtube
so
be
sure
to
adhere
to
the
cncf
code
of
conduct.
Let's
get
started
with
announcements.
First.
Announcement
of
the
only
announcement
that
I
have
is
that
the
124
release
is
still
expected
to
happen
today.
It
looks
like
the
eta
for
that
release
is
5
p.m.
A
Pst,
today,
they're
the
sig
release
team
is,
I
think
they
gave
a
bunch
of
go
signals
for
the
release
and
they're
just
making
everything
happen
now
so
look
out
for
an
announcement
to
the
kubernetes
dev,
alias
for
when
all
those
artifacts
are
available.
A
A
Okay,
let's
move
in
to
the
agenda
first
agenda
item:
I
was
briefly
discussing
this.
There
are
some
issues
with
the
the
zoom
account
we're
having
issues
getting
into
the
zoom
account.
So
the
meeting
is
set
up
to
auto
record
to
the
cloud,
so
we
have
that,
but
it
may
be.
A
There
may
be
a
little
slight
delay
between
getting
between
the
meetings
happening
and
getting
the
meetings,
recordings
and
uploading
them
to
youtube
so
I'll
update
once
we
get
that
resolved.
C
Yeah,
so
we're
redoing,
a
bunch
of
the
docs,
as
you
may
know,
for
the
124
release.
One
of
the
docs
that
I
was
working
on
was
the
cube
adm
docs
and
the.
If
anybody
that's
not
familiar
with
the
cube
am
docs.
They
have
a
bunch
of
information
about
how
to
like
install
flannel,
how
to
configure
flannel
and
all
of
those
types
of
things,
as
well
as
running
cube.
Adm.
The
the
linux
docs
used
to
have
that
information
in
them
and
they've
moved
away
from
it.
C
C
What
kind
of
folder
structure
you
should
have
on
the
windows
node
and
that
type
of
thing,
and
that's
going
to
be
going
away
in
124,
and
we
have
a
little
bit
of
that
in
one
of
the
other
docks.
But
we
were
wondering
if
how
much
that's
used
and
also
like
do
we
need
to
have
this
type
of
information
somewhere
and
where
do
we?
Where
do
we
store
that?
C
Because
it
can
be
very
specific
according
to
what
runtime
you're
using
as
well
as
what
cni
you're
using,
but
we
was
looking
for
kind
of
just
a
little
bit
of
feedback
on
you
know
if,
if
we
need
this
information
in
the
kubernetes
docs
and
if
where
it
should
live,.
A
I
I
my
gut
feeling
says
that
these
are
being
used
today,
just
based
on
some
issues
and
feedback
and
pull
requests
that
we
occasionally
see
into
the
sig
windows
tools
repository
where
these
happen.
I'm
not
sure,
if
that's
the
extent
of
that
of
like
of
this
yeah,
if
that's
the
extent
of
that
usage
or
if
people,
if
there's
a
lot
more
people
who
find
the
information
on
the
kubernetes
website
that
don't
have
that,
don't
get
to
the
segwindos
tools
repository
or
not,
though,.
D
They
want
to
put
things
on
d
drives
right,
so
it's
not
the
host
os
and
a
lot
of
things
don't
work
by
default.
That
way,
so
I
mean
guidance
around
where
to
place
that
and
how
to
place
it
and
like
how
to
move
things
around
like,
I
think,
would
be
valuable.
D
C
Yeah,
I
I
think
the
not
being
prescriptive,
but
giving
some
guidance
is
kind
of
the
right
direction
to
go.
I'm
interested.
Do
you
run
your
services,
so
there's
a
couple
different
ways
to
install
kubelet
and
install
qq
proxy.
Are
you
using
nssm?
Are
you
using
something
else?
Are
you
just
using
straight
windows
services?
C
I
think
that
that
comes
down
to
some
of
some
of
the
details
as
well
as
how
do
you
configure
these
things
so
just
interested
in
what
you're,
using
out
there.
D
I
don't
like
nssm,
but
there
there
is
not
an
alternative
to
turn
things
into
windows
services
easily.
It
irritates
me
that
not
everybody
has
a
dash
dash,
install
service
or
whatever
flag
to
like
make
a
windows
service
from
the
go
app
like.
I
feel
like
that,
should
be
baked
in
more
places
for
rke2
the
rk2
service
installs,
using
the
go
framework
with
a
flag
as
a
windows
service
using
go,
and
then
we
supervise
cubelet
and
container
d
and
all
those
things.
D
So
all
those
things
get
booted
up
by
rke2
and
it
supervises
that
those
processes
stay
running.
So
we
avoid
a
lot
of
having
to
use
nssm
and
stuff,
but
we
we
worked
around
that,
but
we
still
create
services
using
go
and
I
don't
like
I
understand
the
powershell
script
to
then
generate
the
windows
service
is
what
calico
uses
which
is
within
ssm.
But
I
don't
know
I
don't
think
they're
a
good
solution,
but
it
is
confusing
because
they're
everybody's
all
over
the
board.
You
know
yeah.
A
Yeah
and
unfortunately
like
I,
don't
think
we
can,
because
of
these
same
third-party
content
guidelines,
I
don't
think
we
can.
I
don't
think
it
changes.
Docs
that
say
here's
one
option
to
configure
the
windows
bits
to
run
the
services
on
the
kubernetes
website
is
to
use
nssm.
I
don't
think
that
that
would
be
approved
for
on
the
main
kubernetes
website
for
the
same
reasons,
so
yeah,
it's
kind
of
tricky.
A
A
Well,
it's
yeah!
I
don't
think
that
it's
anything
against
nssm
is
that
in
general,
they're
against,
like
there's
some
policies
against,
I.
E
Mean
I
think,
if
we're
gonna
have
any
issues
maintaining
our
docks,
we
should
sim
link,
kubernetes,
docs,
dot,
io
and
say:
look
if
you
want
help
with
windows,
here's
the
place,
it's
maintained
and
either
have
our
own
doc
site,
or
do
it
on
tools
or
whatever
or
dev
tools.
For
that
matter,
any
repo,
I
don't
care
what
repository
it
is,
but
we
should
have
a
home
that
we
can
just
push
to
that.
We
don't
there's
not
enough
of
us
to
spend
time
jumping
over
cncf
hoops,
I
mean
for
linux.
E
E
F
C
A
I
you
were
kind
of
breaking
up
there,
but
I
think
I
got
the
gist
of
what
you
were
saying.
I'm
just
saying
that
versioning.
A
Version
and
other
things
aren't,
and
it's
a
lot
of
effort
to
maintain
versions.
Even
in
these
other
repositories,
I
think
specifics,
like
flags
for
components
that
would
be
more
subject
to
versioning
would
still
get
documented
in
the
on
the
main
website
and
put
tips
or
guides
on
how
to
set
things
up
with,
like
an
ssm
or
with
a
native
service
or
potentially
even
a
guide
on
how
to
implement
that
go.
Lying
service
base
stuff
that
jamie
was
talking
about.
A
E
D
E
D
E
James
had
a
good
me
and
james
had
this
book
that
got
rejected,
like
maybe
james
I
mean,
maybe
we
should
just
this
is
we
should
just
open
source
that
damn
thing
right
and
put
that
on
there
too
right
like
like
they
did
with
the
cappy
stuff
right?
They
have
a
cluster
api
book
and
people
can
read
it,
and
the
cappy
group
maintains
it.
D
C
So
I
think
what
I'm
hearing
is
that
this
is
valuable.
We
can
put
some
basic,
maybe
a
basic
page,
that
just
talks
about
like
this
is
how
you
install
cubelet
as
a
service
using
the
flags
and
then
from
there.
C
E
E
D
You
know
because
yeah
well,
I
mean
I
mean
microsoft
has
a
very
specific
way
of
writing
docs
and
you,
you
spend
all
your
time,
reading,
powershell,
docs
and
reading
windows
docs
to
figure
out
something
that
if
the
kubernetes
docs
were
in
a
very
similar
like
format
and
style,
this
is
just
my
personal
opinion.
I
think
that
would
ease
people
finding
the
information
that
they
need.
It
might
confuse
yeah.
A
Yeah
and
the
docs,
the
kubernetes
website
has
their
own
style
and
yes,
it's.
D
C
Cool
also.
A
F
C
Any
volunteers
that
are
very
passionate
about
this
topic
always
looking
for
extra
help
beyond
that,
I
think
we
can
move
on
to
the
next
topic.
A
I
can
maybe
help
out
with
this.
I
will
say
too
that
the
the
big
doc
updates
that
we
wanted
to
do
should
be
landing,
hopefully
landing
pretty
soon.
So
we
can
just
maybe
use
that
as
an
opportunity
to
see
if
there's
any
feedback
and
then
figure
out
what
to
add
to
this
other
split
out.
Docs.
E
I'm
gonna
see
I'm
gonna
poke
david.
He
might
be
able
to
own
this
whole
thing.
I
mean
because
he's
been
getting
involved
in
the
docs
thing.
E
So
would
you
suggest
mark
that
this
should
be
like
a?
What
do
you?
What
do
you
all
think
like
this
would
be
a
sort
of
an
announcement
that
we're
moving
the
docs
here,
update
the
add
the
new
docs
and
then
create
a
pointer
in
the
old
docs
that
points
to
the
new
docs,
so
that
people
going
to
kubernetes.I
io
can
see
and
then.
A
A
Yeah,
I
think
we
should,
I
think,
if
we're
serious
about
doing
this,
I
think
we
should
maybe
have
an
issue
in
sig
windows
tools
proposing,
like
we
put
some
specific
docs
in
here
with
like
a
discussion
about
what
the
outline
is
and
maybe
some
other
higher
level
details.
A
E
I
I
think
I
think
I
know
somebody
that
can
own
this
whole
problem,
so
for
you
and
then
maybe
we
just
can
sync
up
with
them
for
like
30
minutes
sometime,
you
know
and
just
make
the
plan
and
then
they'll
just
own
it
from
beginning
to
end,
because
they're
really
trying
to
dig
into
the
docs
stuff
and
they're
on
the
release
team.
Here
at
vmware
and
they're
new
to
kubernetes
and
they're
he's
you
know,
and
he
even
uses
windows
so.
A
E
E
Yeah
like
if
you,
if
you
want
to
mentor
him
or
whatever
that's
great
like
you
know
that
that's
probably
necessary,
because
you
can
at
least
get
us
started:
okay,
cool,
I'm
gonna
assume.
Nobody
else
wants
to
do
this
so
I'll.
A
A
E
E
I
think
yeah,
I
think
you
need
to
create
the
issue
with
some
boundaries
in
it:
okay
and
it's
and
I'm
happy
to
do
whatever
and
help
do
whatever,
and
then
I
think
the
thing
that
david
could
really
do
is
once
those
boundaries
are
set.
He
can
work
with
me
or
a
meme
or
whoever
else
to
figure
out
where's
the.
How
do
I
do
flannel?
What's
nssm?
How
do
I
set
up
devtools?
G
Yeah
so
I
think
they
are
kind
of
interrelated,
because
for
my
what
I
understand
you
see,
windows
tools
has
a
folder
of
host
process
and
this
is
an
example
of
the
cns.
Just
went
there
somehow,
but
that
was
not
the
goal
of
the
final
goal.
So
I
think,
after
talking
with
james,
like
it's
better
for
each
cni
and
handle
its
own
setup
on
windows
and
and
that's
my
question
like
we
have.
G
To
do
that,
like
is
the
code
simple
enough
to
start
doing
these
things?
Should
we
move
to
your
own
repository.
A
A
I
think
that
in
a
perfect
world,
each
project
that
like
has
that
hosts
deployment
files
for
linux,
would
also
host
deployment
files
for
for
windows
in
whatever
capacity
they're
they're
comfortable
with
whether
it's
like
multi-art
images
or
a
separate
guide
or
whatever,
where,
but
I
don't
in
reality
like,
and
I
don't
know
if
people
have
been
here
in
it
like.
I
think
the
sig
windows
tools
is
kind
of
a
mess
right
now
and
has
been
especially
and
the
requirements
for
how
to
get
all
of
this
working
on
container
d
added
some
complexity.
A
So
I
think
the
reason
why
they
got
all
stood
up
there
was
it
already
existed,
because
we
had
some
of
those
the
deployment
files
for
the
really
hacky
cube
adm
with
docker
shim
deployments,
and
because,
especially
when
host
process
containers
were
in
alpha,
we
needed
a
place
to
exercise.
All
of
these
to
you
know,
build
and
exercise
all
of
these
and
get
feedback
from
this
too,
so
that
those
are
my
opinions
like.
A
I
think
that,
while
host
process
containers
are
still
in
beta,
if,
if
it
makes
sense,
we
can
add
more
examples
to
the
host
process
folder,
but
we
should
be
clear,
saying
like
these
are
temporary
and
we
do.
We
don't
want
to
add
a
whole
bunch
and
also
try
and
see
if
for
new
projects
like
the
entree
deployments,
if
that
project
is
okay,
just
hosting
them,
I
would
prefer.
A
I
think
I
would
prefer
that,
and
we
do
want
to
also
try
and
move
the
like
the
cube
proxy
images
out
of
or
get
rid
of
those
and
just
have
the
cube
proxy
images
that
the
kubernetes
project
is
maintaining
just
support
windows,
and
I
I.
E
Really
liked
the
a
meme
did
that
experiments
directory
in
sig
windows
devtools
for
image
builder-
I
I
thought
that
was
cool
and
we
have
so
much
andrea
stuff.
In
there
I
mean
right,
like
maybe
having
making
that
the
poem
for
host
process.
C
At
least
for
the
calico,
I
initially
tried
to
push
that
upstream,
but
it
was
not.
It
was
kind
of
challenging
because
of
the
way
host
process
is
implemented
and
mark
did
that
demo
next
week,
and
so
now
that
once
once
that
lands,
I
think
calico's
gonna,
take
that
those
changes,
and
then
we
can
remove
it
from
this
this
tool.
C
So
I
think
the
I
would
like
to
see
an
effort
to
go
to
directly
to
the
andrea
project
and
see
that
if,
if
there
say
no
way
we're
not
going
to
take
this
right
now
because
of
x
y
z,
then
we
can
probably
take
it
into
sig
windows
tools.
But
I
would
like
to
see
that
effort
happen
before
we
take
it
into
sequential,
since
that
makes
sense.
A
A
Yeah
james,
can
you
clarify?
Is
it
mainly
the
lack
of
being
able
to
use
in
cluster
config,
yeah?
Okay,
so
hopefully
once
that's
solved,
then
the
deployments
for
these
are
going
to
be
a
lot
simpler
and
then
it
may
be
a
lot
easier
to
get
these
support.
For
each
of
these
added
upstream
is
that.
C
Yes,
yeah,
that's
the
the
idea
and
then
there's
there's
one
other
tool
in
there
that
hooks
up
container
d
and
etw
logging
that
law
it
stands.
You
can
use
it
to
log
any
etw
to
to
standard
out
which
is
helpful
for
all
sorts
of
situations,
and
I
think
that
one
that
that's
kind
of
like
there's
nowhere
for
that
to
live,
and
that
seems
like
a
really
useful
place
to
live
in
sick
windows
tools,
because
it's
a
tool
that
somebody
could
potentially
use
that
doesn't
necessarily
have
a
place
to
live.
C
E
G
E
A
All
right,
one
one
other
wrinkle,
that
I'll
throw
into
this
mix
is
so
long
time
ago.
All
of
the
images
that
were
built,
the
container
images
that
were
built
built
in
sig
windows
tools,
were
published
to
a
segwindos
tools.
Docker
hub
account,
as
everybody
knows,
they're
working
on
moving
away
from
docker,
docker
hub-based
container
registries,
when
we
initially
did
the
setup
to
produce
some
of
these
images
and
push
them.
A
We
went
to
the
github
container
registry
under
the
kubernetes
org,
and
so
there's
a
couple
of
red
repositories
there
that
were
made
public
since
then
the
github
management
team
and
the
contribex
people
have
locked
it
down,
so
we
can't
make
any
more
container
repositories
public.
I've
asked
for
that
to
like
I've,
asked
for
more
details
on
that
and
to
make
some
new
images
public
in
that
repository,
and
I
didn't
really
hear
anything
back.
I
need
to
go
poke
some
people
with
that
too.
So,
host
hosting
the
container
images
is
another
open
question.
A
E
Gonna
go
back
to.
I
think
that
the
best
place
for
the
andrea
host
process
stuff
is
in
the
experiments
directory
of
sig
windows
devtools,
because
that
is
a
place
where
you
can
go
and
you
can
test
andrea
by
clicking
one
button
and
we
can
write
up
exactly
how
to
run
it
with
a
host
process
configuration
and
we
can
point
people
to
the
readme,
and
I,
unless
this
is
going
to
live
in
the
official,
andrea
repo,
I
don't
see
the
point
of
putting
it
anywhere
else.
G
E
A
Maybe
we
could
see
how
the
discussion
about
the
issue
that
I'm
going
to
create
cigarettes
tools
goes
to.
I
need
to
drop
for
the
signaled
meeting
too
so.