►
From YouTube: Kubernetes SIG-Windows 20221011
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
Hello,
everybody
and
welcome
to
the
October
11
2022
iteration
of
the
kubernetes
seguendos
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
start
with
some
announcements
of
first
announcement
is
where
past
enhancement
freeze,
that
was
last
Thursday,
so
the
next
major
milestone
for
the
126
released
is
code
freeze
and
that
is
Tuesday.
A
November
8th
I
believe
that
time
is
PBT
the
exact
times
or
deadlines
for
each
time
zone
are
on
the
release
schedule,
but
we're
still
always
up
on
that.
Not
to
worry
about
that
does.
A
Feel
free
to
add
it
to
the
announcements
or
speak
up.
If
you
want
not,
we
can
check
to
see
if
there's
any
new
contributors
who
would
like
to
introduce
themselves
here.
As
always,
we
usually
give
a
little
bit
of
space
if
there's
anybody
who's
new
to
the
project
who
wants
to
say
hi
or
you
know,
share
what
they
would
like
to
get
out
of
the
community
meetings.
A
Okay,
I,
don't
see
anybody.
Volunteering
with
that
I
didn't
see
a
whole
lot
in
the
agenda
today,
since
we
just
entered
the
I
guess
exited
the
enhancement.
Freeze,
I
did
take
a
few
minutes
to
list
out
some
of
the
work
that
people
are
prioritizing
for
this
release.
We
can
go
over
that
if
there's
no
other
agenda
items
that
people
want
to
discuss,
see
if
we
can
find
more
owners
or
kind
of
collaborate
more
with
that.
A
So
if
anybody
has
anything
else,
they'd
like
to
discuss
feel
free
to
do
so
or
just
interrupt
me.
I
will.
Oh
I
will
also
say
that
the
fix
for
the
cube
proxy
regressions
that
we
discussed
in
depth
last
week
have
been
merged
into
the
124
and
125.
release
branches,
so
I
think
the
patio
thesis
for
those
are
coming
out
soon.
A
So
we
will
once
those
patch
releases
are
coming
out.
I'll
work
with
David
to
probably
send
up
notes
to
the
Sig
Windows
mailing
list
and
we'll
highlight
it
in
this:
the
slack
again
that
people
definitely
want
to
pick
up
those
changes.
That's
the
issue,
we're
fixing
this
issue
here.
A
Okay,
so
for
the
enhancements
that
are
being
worked
on
in
126
and
I,
didn't
include
the
operational
Readiness
enhancement
folks,
because
that's
tracked
out
of
tree,
but
the
ones
that
are
we're
hopefully
making
progress
on
for
126
is
the
node
service
log
viewer
by
going
to
Alpha,
RPG
or
anything
you'd
like
to
comment
on
that.
A
Yeah,
so
I
am
now
going
to
start
reaching
out
to
Tim
Hawkin
on
slack
now
that
I've
I
wanted
to
give
him
a
because
he
had
sent
out
a
a
tweet
saying
he's
really
busy
with
the
cap.
So
I
don't
want
to
Ping
him
while
he's
reviewing
caps
to
review
code
now
that,
like
five
days,
are
passed,
I'm,
gonna
ping
him
on
slack
and
not
on
the
VR
and
ask
both
him
and
Jordan
and
Fabian
I
I'll.
A
Add
you
to
that
that
group
so
that
we
can
just
talk
about
stuff
there,
and
hopefully,
Tim
will
have
some
time
to
review.
Okay,
let
me
know
if
you
like
me
to
Ping
them
too
Pastor,
then:
okay,
yeah
yeah
we've
got
the
the
tests
and
everything
there
too.
So
hopefully,
that's
gonna
be
more
easier
or
like
easier
to
let
that
merge.
Yeah,
that's
true!
A
Okay!
Next
one
is
for
the
host
process
containers.
We
should
be
targeting
stable
for
this
release.
We've
talked
about
that
before
host
Network
support
for
Windows.
That's
something
that
hopefully
we
can
go
to
Alpha
with
the
changes
in
kubernetes
are
pretty
minimal,
but
there's
more
changes
that
are
needed
in
containerdy
or
the
container
runtimes.
For
that
too,
that's
all
kind
of
described
in
the
cup
and
I
think
for
this
one.
A
A
Thank
you
last
one
that
I
have
here
is
the
cri-based
stats,
the
Amendments
for
Windows
the
window,
support
for
this
merged
kind
of
late
before
or
before
enhancement,
freeze
and
I.
Believe
James
has
an
open,
PR
in
container
D
and
in
the
cubelet
to
wire
that
up
on
both
ways,
so
that
I
think
is
probably
just
needs
some
reviews
at
this
point
and
then
that
should
be
good
to
go.
A
Yeah
I
need
to
refresh
those
where
we
put
reviews
on
them.
What's
on
my
list
to
do
later
in
the
week,
yeah
I,
don't
think.
That's
urgent,
but
you
get
to
do
early,
does
any
body
else?
Is
there
any
other
caps
that
are
probably
not
tracked
by
Sig
windows
but
are
have
Windows
related
work
that
people
would
like
to
either
discuss
or
track
here
how's
the
kpng
kept
going
today.
B
B
It-
and
it's
just
mostly
just
you
know,
not
really,
there's
not
it's
mostly
formalized
now
to
the
point
that,
like
it,
will
be
proposed
to
sing
windows
and,
like
I
mean
for
the
most
part,
I
feel
like
v0
mission
accomplished,
like
we've
demonstrated
that
we
can
redo
the
coup
proxy
and
it
works
on
all
platforms.
Using
this
model
and
I
think
one
of
two
things
will
happen.
It
will
be
the
Catalyst
for
them
to
say,
okay,
here's
what
the
new
coup
proxy
should
be
go
build
that
like
or
it'll,
actually
be
like
yeah.
B
Let's
do
this.
This
is
good.
Just
you
know
what
I
mean
it'll
be
one
of
those
two
things
I
think
so
in
in
most
ways,
I
feel
like
what
we
wanted
to
do
has
has
sort
of
been
done
now,
which
is
sort
of
demonstrate
that
you
could
redo
all
this
in
a
completely
new
way.
B
Hopefully,
hopefully,
people
will
be
sort
of
okay
with
it.
You
know.
A
B
A
B
Updated
yeah
and
so
like
from
there
I
think
my
yeah.
My
I
would
like
it
to
be
at
that
point
to
be
driven
by
and
by
a
group
of
people
who,
like
a
new
group
of
people,
so
that
it's
not
like
you
know
so
I
don't
become
some
benevolent
dictator
or
something
like
that.
You
know
like
I,
don't
want
to
be
in
that
situation
and
so
I'm
hoping
that
once
it's
proved
it'll
be
driven
by
other
people.
B
A
B
Way,
we're
proposing
it
in
the
cap
is
that
every
back
end
will
be
a
separate
repository
and
that
will
be
Federated
together.
The
way
we
do
with
staging
now
and
something
like
that,
and
then
that
there
will
be
like
a
kpng
core
proxy
for
the
for
the
server
brain
thing
and
that
that
and
then
like,
and
so
we
will,
we
can
still
give
people
a
single
binary
and
that
single
binary
will
be
something
that
federates
the
code
from
all
those
repositories
and
compiles.
That
looks
and
feels
and
runs
the
same
as
regular.
B
Coupe
proxy
goes,
but
it's
just
a
decomposition
of
those
other
things
or
I'm.
Sorry,
an
aggregation
of
those
other
things
awesome
and.
B
B
And
then,
and
then,
if,
if
in
that
future,
the
way
it
would
work
is
seek
windows,
we
could
just
own
our
own
Coupe,
proxy
and
well,
there's
all
another
future,
which
is
that
if
we
at
Sig
Windows
decide
that
it's
really
what
we
want
to
do,
we
could
literally
just
we
could
make
Coop
proxy.
We
could
get
on
a
call
with
David
or
something
and
say
like
hey:
do
we
want
to
just
have
our
own
service
proxy
and
the
one
that
seemed
tree?
B
You
know
like
if
other
folks
want
to
maintain
it,
they
can,
but
the
best
thing
for
Windows
would
be
to
have
our
own
proxy
that
we
maintain
right
because
I
mean
that's
something
we
could
talk
about
because
I
don't
see
the
point
like
if
we
can
do
a
better
job,
maintaining
our
own
proxy
and
that's
what
everybody
else
is
doing
now,
maintaining
their
own
proxies
and
there's
not
a
plugable
way
to
do
it
in
core.
We
could
just
have
our
own
proxy,
like
no.
What's,
there's
no
law
that
prevents
us
from
doing
that
right.
B
A
All
right,
some
of
the
other
work
that
I
know,
is
kind
of
ongoing
and
and
long-lived,
and
this
is
definitely
not
an
exhaustive
place.
It's
just
what
came
across
like
half
that
in
mind.
A
The
the
unit
tests
running
for
Windows
there's
a
lot
of
open
PRS
that
are
all
tracked
on
our
project
board
that
Claudio's
done
most
of
those
I
think
we
do
want
to
try
and
get
those
merged.
So
if
anybody
has,
you
know
bandwidth
to
test
them
out,
review
them.
A
Yep
they're,
all
tracked
right
here
under
they'll,
have
unit
tests
in
there
give
some
reviews
that
would
be
appreciated.
I
think
most
of
these
are
touching
multiple
parts
of
the
code
base
and
have
some
initial
reviews
that
are
just
either
waiting
for
the
rest
of
the
everybody
who
needs
to
approve
have
them
be
merged.
C
C
We
do
random
I,
think
we
I
think
we
still
do
and
yeah
and
you
can
see
it
in
test
grid
as
well.
This
should
be
pills.
B
C
A
C
A
C
A
C
A
The
other
PRS
were
I,
think
kind
of
help
to
link
them
the
Windows
File
system,
permission
PRS.
Those
have
been
open
for
probably
what
18
months
now
at
least
one
of
them
is
it'd,
be
good
to
get
through
and
get
that
merged.
C
C
But
yeah,
basically,
with
this,
we
we
will
start
to
set
file
permissions
for
any
volumes
which
are
being
said
basically
for
volumes.
You
can
also
have
item
mode
set
or
stuff
like
that
which
we
were
ignoring
before,
because
we
didn't
support
this
on
Windows
and
that's
going
to
be
supported
from
now.
C
The
political
Source
words
some
unit
tests,
which
verifies
that,
indeed,
the
file
permissions
work
as
intended
on
Windows.
So
you
know
extra
guarantees.
B
C
A
C
A
That's
really
all
I
had
on
the
agenda
today.
Does
anybody
have
anything
else
they'd
like
to
discuss?
If
not,
we
could
end
a
little
bit
early.
C
One
minor
thing
I
forgot
to
mention
regarding
the
file
permissions
work,
there's
another
pull
request
which
I
have,
which
will
also
enable
E3
tests
which
verify
those
file
permissions
being
set
properly.
There
are
some
Linux
only
tagged
tests
which
were
tagged
with
links
only
simply
because
we
were
not
supporting
file
permissions
right,
but
if
we
do
merge
this
one
I
do
have
another
request
which
we
should
be
able
to
run
afterwards,
which
is
this
one
LinkedIn
chat
we
should.
C
We
should
be
named
something
like
like
enables
file
permissions
related
tests
on
Windows
I.
Think
that's
the
one.
C
Yeah
there
shouldn't
be
a
problem.
There
was
a
small
issue
in
the
agnostic
image
which
was
not
reading
the
file
permissions
properly
now,
basically,
how
those
volumes
work,
they're,
basically
siblings,
how
they're
made
and
diagnosed
binary
was
actually
reading
the
Sim
links
file
permissions,
not
the
targets
file
permissions,
which
was
returning
false.
C
Results
because
of
that,
but
now
an
update
was
sent
to
diagnost
image.
It
was
published
a
long
time
ago,
so
everything
should
run
properly.
I
think
we
can
even
run
the
windows
E3
job
on
this
one
I
think
it
already
ran
already
on
this
pull
request.
That'd.
A
C
C
C
Yeah
I
think
it
was
B.
I
ran
the
around
the
windows
job
on
the
original
purpose,
which
had
all
of
the
commits
there,
because
we
still
need
that
that
political
submerged
first.
So
this
will
pass.
So
you
won't
pass
without
that
that
one
yeah,
but
we
did
run
it
before.