►
From YouTube: Kubernetes SIG Windows 20230725
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
recording
has
started
welcome
folks
to
the
July
25th
stigmundo's
Community
meeting.
The
meeting
is
recorded
and
uploaded
to
YouTube.
So
please
adhere
to
the
cncf
code
of
conduct,
which,
which
basically
translates
to
be
nice
and
kind
to
everyone
right.
Let's
kick
things
off
so
if
today,
the
main
announcement,
I
guess
is
the
128
test
freeze
is
today
I
the
only
thing
I
know
we
have.
We
have
some
of
quadu's
unit
tests,
I
think
that
are
still
potential
for
it
to
get
merged
today.
A
A
A
I
I
just
put
it
in
an
item
just
to
see
how
we
did
for
the
PRS
that
we
had
targeted
for
128
did
how
many
missed
the
you
know,
Mr
Freeze.
Do
we
need
to
track
it
for
the
next
release?
Those
are
the
kind
of
things
I
just
wanted
to
quickly
go
through.
We
do
have
the
PRS
listed
below
I
know
the
end-to-end
test
merge,
but
there's
a
issue
in
it
that
Mark
and
I
found.
B
A
So
that
merged,
what
about
BPA.
A
Okay,
so
that
is
something
we
should
track
for:
129.,
okay
and
let's
look
at
the
next
one.
A
C
A
Yeah
I'm
not
sure
I
can
I
can
fix
it
later.
So
the
only
other
thing
I
guess
is
the
unit
spr's
I
know
a
few
of
them
are
I.
Think
a
few
are
still
open,
so
I
guess
we
can
try
and
get
them
into
129.
A
All
right
right
so
moving
on,
we
can
look
at
the
next
one,
which
is
operational.
Readiness
was
that
UJ
that
put
that
in.
D
Yeah
I
added
it
for
me
just
looking
at
it,
though,
so
we're
running
some
of
the
Sig
Network
tests
and
for
the
operational
Readiness,
stuff
and
I'm,
not
sure
how
many
of
them
we
normally
run
for
Windows,
and
some
of
them
do
stuff
like
poke
around
like
starting,
they
start
containers
and
then
they
they
want
to
start
these
containers
on
like
a
host
Network
and
so
that
they
can
see
whether
a
node
can
probe
a
service
from
the
host
and
stuff
like
that,
and
so
those
tests
are
not
compatible
with
with
the
wastig
windows,
tests,
work
and
there's
kind
of
two
ways
of
sort
of
thinking
about
them.
D
One
would
be
to
say:
okay,
these
tests
do
not
run
for
Windows.
We
don't
care
about
this
functionality
for
Windows.
The
other
way
of
looking
at
them
is
to
say
now
that
we
have
host
process
containers.
D
You
know
we'll
we'll
do
the
host
Network
pod
functionality
through
those
and
I
haven't
thought
about
much
about,
but
it's
a
specific
container.
It's
it's
called
like
a
his
specific
test
and
what
it
does
is
it
like
creates
services
and,
and
then
it
creates
a
container
that
runs
as
a
host
Network
pod
and
like
tries
to
probe
them.
D
The
goal,
of
course,
is
to
make
it
so
that
we
have
an
explicit
definition
of
what
Sig
Network
tests
actually
work
on
Sig
windows
and
what
we,
what
don't
work
on
Sig
windows
and
and
then
once
you've
sort
of
know
that
you
can
sort
of
make
the
decision
of
this
doesn't
work
because
Windows
doesn't
support
it
versus
this
doesn't
work
because
the
e2es
haven't
been
written
in
a
way
that
work
with
Windows.
D
So
does
anybody
know
anything
about
host
processes
and
and
whether
or
not
host
process
containers
are
required
to
run
on
the
host
Network
in
the
containerdy
universe?
I
know
in
Docker
you
could
get
away
with
all
sorts
of,
but
like
in
container
D.
Do
you
need
a
host
process
container
to
run
on
host
Network
or
yes,.
D
Okay,
pramita,
that's
the
answer,
so
we
do
need
to
do
this
for
anything,
that's
a
host
Network
test.
We
want
to
get
it
working
we're
going
to
have
to
make
it
a
host
process.
Container
and
and
that'll
be
quite
the
adventure,
but
but
we
have
expertise
that
we
can
ask
James
and
Steph
for
help.
C
Yep
cool:
wasn't
there
a
plan
to
have
a
host
Network
for
regular
Bots
as
well?
At
one
point,
it
was
in
the
cap
to
potentially
look
at
it
in
the
future,
but
there's
no
I,
don't
think
there's
been
any
movement
on
it.
D
I
mean
I
think
that
we
know
what
to
do
now.
James,
we
may
ping
you
on
slack
for
some
pointers
on
how
to
how
to
how
to
what
the
minimal
thing
to
do
with
the
host
process
container
would
be
to
solve
the
problem
we
have,
but
I
think
I
think
we
can
probably
figure
it
out.
Yeah.
C
Absolutely
just
let
me
know
it
doesn't
mean
that
you'll
be
like
running
a
process
on
the
host
versus
like
in
a
pod,
so
you'll
have
full
access
to
the
host
I.
Don't
know
if
that'll
make
a
difference
for
any
of
those
tests,
but.
D
D
We're,
also
adding
some
annotations
to
the
to
the
tests
to
do
kubernetes,
dot,
IO,
slash
windows,
but
that's
largely
just
to
be
explicit
and
also
because
it'll
make
them
more
likely
to
pass
in.
In
certain
environments
like.
D
Eks,
so
those
are
kind
of
the
two
updates
we've
got,
but
thanks
again
pramita
for
digging
into
all
this
stuff
and
that's
that's
all
I
got
I,
don't
know.
If
was
there
anything
else
we
were
supposed
to
ask
him.
I,
don't
remember.
That's
all
I.
Remember.
D
A
All
right
sounds
good
thanks,
Jay
for
bringing
this
up
the
next
topic.
This
is
something
I
just
added
it's
about
the
overhauling
of
the
windows.
Documentation.
I
know
that
Tim
from
the
docs
team
pinged
us
a
few
times
and
I
think
he
might
have
gotten
a
little
impatient
and
he
just
mocked
us
as
life
cycle.
Stale
I
just
want
to
see
how
do
we
want
to
handle
this
I?
Think
the
windows
side
of
the
documentation
is
still
pretty
not
up
to
Mark,
right
and
I.
A
Think
we
I
think
Mark
and
I
think
a
little
bit
and
I
helped
out
a
little
bit.
James
helped
out
a
little
bit,
I'm
just
wondering
what
our
general
strategy
around
the
window,
specific
documentation
for
kubernetes
is
moving
forward
and
I
think
we
should
sort
of
reawaken
this
issue.
I
just
want
to
know
what
your,
what
everybody's
thoughts
are
on
that.
C
Yeah
I
mean
should
we,
we
were
making
quite
a
bit
of
progress
when
we
were
doing
the
regular
bi-weekly
like
docs
team,
like
I,
don't
know
like
I,
don't
know
what
we
call
it
but
like
we
were
just
getting
together
and
kind
of
keeping
each
other
accountable
and
just
moving
through
it.
So
maybe
we
should
start
that
up
again,
because
that
seemed
to
be
effective,
I,
don't
know
anybody.
A
I'm
fine
with
that,
like
I,
think
what
has
happened
is
that
slot
is
not
I.
Think
Mark
has
a
conflict
with
that
slot,
and
so
we've
been
talking
about
Reawakening
it
or
one
of
the
ideas
we
had
is
say
like
on
a
day
like
today.
Right
we
have,
the
agenda
is
pretty
light.
We
start
looking
at
the
docs
as
part
of
the
regular
meeting.
A
That
was
one
of
the
ideas
that
we
had
thrown
around
because
of
Mark
not
being
available
for
that
other
slot,
I
I'm,
open
to
anything,
I
think
I,
don't
have
a
conflict,
so
I
should
be
able
to
attend,
but
I'm
open
to
either
approach
James.
If
we
want.
D
A
So
I
think
I.
What
I'm
hearing
is
that
we
want
to
use
this
meeting
right.
Okay,
is
that
what
you
were
saying.
D
A
Yeah,
it's
not
it's,
not
my
project
or
James's
project
or
Mars.
It's
it's
our
project,
so
whatever
works
for
all
of
us
is
the
best
way
to
move
forward
is
what
I
would
say
so
James.
Are
you?
Okay
with
this?
Are
you
okay
trying
to
use
this
meeting
itself
to
do
the
docs
update.
A
For
me,
yeah
and
I
think
that's
what
Mark
was
also
mentioning
when
we
spoke
out
by
the
last.
So
what
I'll
go
ahead
and
do
is
I
will
cancel
that
doc
meeting
so
that
it's
off
the
the
Sig
Windows
calendar
and
then
I
will
ins
in
the
template
here.
I'll
just
add
an
item
for
overhauling
Windows
documentation
and
we
can
discuss
it
anytime.
A
A
And
maybe
you
know,
we
should
have
marker
mark
around
to
discuss
that.
D
It's
funny
you
mentioned
this
because
me
and
Damon
yesterday
made
a
Windows
networking,
dot,
read
the
docs.io
site
and
we're
like,
let's
just
put
everything
we
know
about
Windows
networking
on
this
thing
and
then
and
then
we
haven't
done
anything
on
it
yet,
but
I'm
like
and
then
feed
it
back
into
the
Stig
and
see
if
they
want
to
like
adopt
it.
Somehow.
A
Yeah
from
what
I
understand
the
the
docs
team
would
like
us
to
keep
everything:
that's
kubernetes
specific
in
the
doc
dot.
You
know
whatever.
Oh.
A
A
D
D
A
And
and
totally
fine
doing
that,
but
I
think
if
we
try
to
do
too
much
information
about
eternus
itself
on
the
kubernetes
side,
I
think
it
will
not
be
accepted,
which
is
what
I
took
away
from
our
previous
interactions
with
the
documentation
team.
They
want
all
of
us
to
live,
that's
somewhere
else,
yeah.
A
And-
and
that's
totally
fine
for
us
to
do
that
Jay,
you
know,
that's
a
good
reference
for
all
of
us
to
I
have
I
find
myself
digging
around
anytime.
I
have
to
do
anything
with
hns
Networks.
So
that's
a
good
reference
for
us
to
add.
A
Yeah
I've
been
working
with
with
with
Mike
on
Microsoft
side.
I
don't
know,
Michael
is
on
the
call.
A
Mike
Zappa
he's
on
the
call,
so
he
and
I
have
been
like
digging
pretty
deep
into
the
edge
in
this
land,
and
it
is
some
we
find
some
parts
of
it
to
be
to
be
murky.
So
any
reference
that's
out.
There
will
be
very
helpful.
A
All
right
so
I
will
make
add
the
documentation
overhauling
to
the
template,
and
we
can
start
talking
about
it
starting
next
week
anytime.
The
agenda
is
like.
B
Good
question
so
I
understand.
We
said
we
don't
want
to
add
too
much
H
documentation
in
the
kubernetes
website,
but
I
still
feel
like
there's
some
valuable
things
that
maybe
Jay
or
anyone
is
discovering
that
that
we
could
find
useful.
Is
there
anywhere
else
this?
This
information
could
live
that,
maybe
something
that
is
in
our
control
and
you
don't
have
to
wait
on
Microsoft
to
document
for
us,
because
personally.
D
Me
me
and
Damon
are
making
one
and
if
you
want
to
help
us
with
it,
it's
a
read
the
docs.io
site,
there's
literally
nothing
on
there
other
than
four
headers
right
now,
but
we
know
we
would
love
help
on
that.
That's
one
and
then
there's
like,
as
you
know,
there's
a
ton
of
blog
posts
and
stuff
that
have
stuff
scattered
around
everywhere.
C
C
A
D
B
Okay,
thanks
thanks,
Jay
I
would
definitely
contribute
in
like,
and
maybe
we
can
get
something
up
there
that
can
help
us
and
everyone.
Anyone
wants
to
see
thanks
for
that
initiative.