►
From YouTube: Kubernetes SIG-Windows 20230606
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
June
6th
2023
iteration
of
the
kubernetes
sick,
Windows
community
meeting.
As
always,
these
meetings
are
uploaded
and
reported
to
YouTube
so
be
sure
to
adhere
to
the
cncf
code
of
conduct
we're
a
little
bit
behind.
So,
let's
just
jump
into
things
in
terms
of
announcements,
I
think
still
only
announcement
is
that
128
enhancement,
freeze
is
coming
up,
I
believe
that's
yeah,
next
Thursday,
so
I
think
that's
the
next
major
milestone
for
that
does
anybody
else
have
any
announcements.
A
Thank
you,
okay.
Next,
we
can
go
on
to
new
contributors.
Everybody
on
the
call
has
been
here
before,
though,
but
if
anybody
wants
to
say,
hi
feel
free
to
do
so.
A
Okay,
before
we
jump
into
the
segment
of
Deadpool's
Administration
dims
pin
segment
of
slack
I
just
wanted
to
raise
some
awareness.
Let
me
get
like
this
like
it
looks
like
there's
a
couple
of
Windows
jobs
that
have
been
failing
like
fig
Windows
test
jobs
have
been
failing
for
a
long
time
about
half
of
those
are
GCE
jobs
and
about
half
of
them
are
like
Azure
disk
Azure
file
jobs
and
the
ask
is
to
either
reduce
their
frequency
or
disable
them
I'm.
Getting
a
link
to
the
red
and
slack
right
now.
A
Does
anybody
have
any
preferences,
I'm
kind
of
inclined
to
just,
except
for
the
segment?
I
was
kpng
job,
just
disable,
pretty
much
all
the
jobs,
because
I
think
people
aren't
looking
at
them
and
we
can
re-enable
them
if
needed.
A
Yeah,
so
these
are
the
jobs
that
are
failing.
I'll
put
this
in
blank
too
we've
got
GCE
124,
Master
container
D,
maybe
I'll
reach
out
to
the
Google
folks
and
see
if
any
of
them
can
help
with
that.
The.
C
I
mean
it
seems
like
yeah,
you
would,
you
would
delete
them
and
just
put
something
on
the
mailing
list.
Right,
yeah.
A
We're
in
slack
the
alpha
drops
family
dreams.
I
think.
Are
we
still
looking
at
that?
First,
looking
at
that
right,
that's
a
PR
job.
A
Yeah,
so
let
me
just
drop
this
there
and
I
think
yeah
for
most
of
them,
especially
the
ones
have
been
failing
for
like
a
year,
just
disabled
them
for
now,
and
then
we
can
re-enable
them.
If
he's
got
time
to
look
at
it,
that's
that's
pretty
much.
All
I've
got
for
the
test
stuff
Arvin.
Do
you
want
to
go
into
secret?
No
schedules?
It's
yeah.
D
I
was
hoping,
Matthias
I
know
he's
been
busy
these
days.
It's
really
his
agenda
item.
I,
don't
want
it.
I,
don't
want
us
to
talk
and
make
a
decision
when
he's
not
around
so
I'm,
not
sure
what
to
do.
Have
you
heard
from
Mateus
recently
Jay.
C
No
I
was
I
was
traveling,
I
was
in
I,
was
in
Palo
Alto
last
week
for
work
and
then
I'm
back
now
so
I
just
flew
in
this
morning
on
a
red
eye,
so
I'm
I'm,
I'm
I,
don't
know.
What's
going
on.
D
So
let's
do
this
I'll
suggest
to
him
that
he
adds
this
to
the
agenda
whenever
he
has
a
chance
to
come
for
the
meeting
and
we
can
discuss
it
at
that
point.
D
An
opinion,
but
I
don't
want
to
just
you
know,
sit
and
discuss
this.
When
he's
not.
There
contribute
so
I'll,
take
an
action
item
to
bring
him
on
slack
and
see
when
he
can
make
it
and
then
we
can
add
it.
C
B
Yeah
I
just
was
just
going
to
call
out
that
somebody
from
the
community
a
couple
weeks
ago
said
they
were
gonna
work
on
that
and
they
did
so
there's
a
PR
for
the
windows
exporter
that
fixes
the
networking
I
left
a
few
comments,
but
anybody
else
wants
to
take
a
look.
B
We
can
and
then
the
other
one
was
just
quick
update
on
the
Pod
and
container
stats,
Nancy
and
I
met
last
week
and
the
alpha
job
is
failing,
but
I
got
up
here
to
fix
that
into
Windows
testing
and
then
I
also
found
two
bugs
in
the
container
decode.
That
I
wrote
based
off
of
that.
So
I've
got
two
PRS
into
containerdy,
one
of
them's
already
been
back
ported,
so
1.7,
and
then
the
other
one
is
under
review.
So
we're
moving
along
there.
B
The
yes,
so
they
just
opened
up
the
cap
of
our
I,
think
I
saw
that
or
they
just
updated
the
cap
for
that,
and
so
that
is
the
plan.
I
think
so
here.
C
A
B
I,
don't
think
any
we
don't
know
yet
somebody's
looking
into
why
126
breaks
on
Azure,
but
okay.
A
Yes,
yeah
I've
ever
seen
the
same
issues,
just
sound
like
politics.
Only
like
phonics,
yeah.
C
C
B
Yeah,
so
what
like,
the
Linux
was
updated,
but
Windows
wasn't,
and
so
that
was
one
problem,
and
that
was
why
I
think,
maybe
on
the
Windows
side,
we
weren't,
seeing
anything
with
those
set
of
failed
tests
is
because
we
were
running
a
different
version
of
Calico
than
the
Linux
nodes
were,
but
then
the
Linux
nodes
on
top
of
that
were
flaking
with
like
pod
startups
and
other
things
like
that.
So
I
think
there's
like
multiple
layers
of
of
issues.
It.
A
C
A
C
A
C
I
guess:
there's
a
minor
update
on
the
Windows
proxy
stuff,
which
is
tangential.
I
I
need
to
find
demon
and
figure
out
what
he
wants
to
do
a
demo
of
the
new
of
the
new
stuff.
But
there
is
some
possibility
that
Sig
Network
might
eventually
come
up
with
a
way
to
plug
to
vendor
an
entry
proxy,
but
there's
no
kept
for
that
yet,
but
they're
trying
to
figure
out
whether
there's
a
way
to
they
can
do
it
with
staging
and
that's
gone
back
and
forth
multiple
times.
C
C
You
warned
me
about
this
at
one
point
and
you
were-
and
so
you
know
but
but
there's
still
no
answer
right
so
I
think
I
still
think
kpng's
the
only
game
in
town
for
doing
this
kind
of
thing,
but
but
someone
might
figure
out
a
way
to
do
some
entry,
vendoring
thing,
but
no
I,
don't
think
it's
going
to
be
anytime
soon.
A
C
Everyone
else
built
their
out
of
tree
proxies
before
kpng
was
sort
of
really
had
been
kind
of
usable
outside
of
it.
You
know
because,
like
we
didn't
make
it
so
you
could
vendor
Kate
Pinchy
until
kpng
until
about
maybe
a
year
ago.
Okay,
every
other
out
of
tree
implementation
didn't
have
a
choice,
but
they
had
to
copy
all
of
the
group
proxy
code.
So
there's
just
copy
paste
stuff
right
can.
C
C
You
know
you
just
copy,
but
for
folks
that
don't
know
about
by
that.
What
we
mean
here
is
literally
you
copy
paste
all
of
the
stuff
inside
of
package,
slash
proxy
into
another.
Go
repository
figure
out
a
way
to
get
all
the
client
go
dependencies
for
the
unsupported
vendoring
in
kubernetes
to
work
which
isn't
hard.
Jordan
Leggett
has
like
a
blog
post
or
something
about
how
to
do
it.
C
C
You
could
do
something
like
that
and
then
you
vendor,
you
know,
client,
go
and
then
you
just
say:
okay,
you
know
you
just
have
package
proxy
running
in
a
different
code
base.
Something
like
that.
It's
not
you
know
it's
not
that
awkward,
but
it's
certainly
a
lot
more
technical
debt
than
necessary.
So
so
it
would
be
our
last
resort.
B
D
A
D
Mark
before
we
go
there's
the
only
remember
during
the
the
backlog
refinement
meeting,
we
had
discussed
what
to
do
about
the
docs
yeah.
A
D
A
Yeah,
so
we
used
to
have
well
I
guess
we
still
have
on
the
calendar
a
docs
meeting
that
was
every
other
Thursday
and
the
alternating
weeks
of
the
or
the
backlog
refinement
meeting
and
we're
wondering
if
we
want
to
bring
that
back
up
for
now
that
time
actually
doesn't
work.
The
best
for
me
anymore,
I,
was
wondering
if
other
folks
are
interested
in
I
mean
I
could
probably
make
it
work
sometimes,
but
should
we
bring?
Should
we
just
try
bringing
that
back
up
again,
Urban.
A
The
issue
that's
open
and
we
looked
at
it
at
the
last
bag
of
confinement
meeting
and
there
was
a
lot
of
to
Do's
to
just
review
certain
pages
that
were
I,
think
we
weren't
sure
like
we
didn't
really
identify
anything.
That
was
bad
about
that,
like
that.
We
wanted
to
restructure
about
those
pages,
but
there
was
all,
but
we
just
wanted
to
make
sure
the
content
was
up
to
date,
because
it
tends
to
not
stay
up
to
date
over
time.
D
A
D
D
So
yeah
I'm
not
sure
how
to
move
forward
Mark
like
we
definitely
don't
need
to
have
that
meeting.
If
there's
a
conflict
or
I
should
say
we
shouldn't
have
a
meeting
in
the
slot
where
it
is
at
currently,
given
you
have
a
conflict,
one
thing
we
can
maybe
do
is
if
we
find
that
our
agenda
is
light
like
on
on
certain
days,
we
make
it
a
day
that
we
talk
about
Docs.
C
D
We
don't
at
least
I,
don't.
A
What's
what's
that
yeah?
Let's
add
it
to
the
agenda.
It
seems
like
unless
there's
a
segment
of
Dev
tools,
discussions,
the
rest
of
it
is
pretty
light.
Next
week
we
can
add,
we
can
bring
it
back
up.
I'll
get
a
link
to
the
issue,
it's
in
K
website
and
I'll
edit
for
the
next
week,
and
if,
if
folks
are
here
to
discuss
image
building
stuff,
we
can
bump
that
out.
C
D
D
A
D
B
Yes,
I
would
propose
that
we
could
also
bring
up
like
like
doing
a
little
bit
of
triaging.
If
we
have
time
in
this
meeting
as
well.
A
D
C
C
A
A
B
I
mean
I
think
it's
just
if
we
have,
if
you
know,
if
it's
a
light
agenda
meeting,
let's
do
some
triaging
and
I
think
it
just
gets
exposure
to
other
people.
Yeah.
D
That
sounds
good
James
I,
like
that
idea.